Linux version of Logos Bible Software
Comments
-
(Please ignore this test post)
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
Added my three votes. Currently sitting at #27.
0 -
Well, I updated to Wine 5.0 RC3 as soon as it dropped. I'm running all 64 bit on Kubuntu 19.10 and the only oddity that I have noticed other than the known bugs that are logged was an occasional failed opening of Logos.
It does not crash, at least with a pop-up crash notification and clicking the shortcut a second time opens immediately and runs excellently. The first attempt to open brings up the Logos splash and then a brief graphical look of opening then nothing. But again the second attempt to open is flawless.
On the positive side - it seems to have no problem exiting and fully closing the program. When I close it, the program syncs and closes and when I go to system monitor it is fully closed.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Running the latest Wine 64, Logos 64 on Kubuntu 19.10:
I have Logos and the indexer set to run on the appropriate versions in winecfg.
After clearing out the corrupted index files, as I posted previously, I have been able to have consistent success with indexing completing. This includes twice indexing sequences over the past two days when adding resources to the library. Both times the indexer fired up, I was able to watch the percentage increase and the indexer ultimately closed itself out. The files structure in the index folder matched up with successful Windows installs.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Hi, Frank.
I'm interested in this, because I'm getting problems. I'm using Debian Bullseye with wine-staging at 5-rc3, 64 bit.
When I try to install in win7, it automatically goes to indexing and crashes.
When I tried to reset the directories as per your instructions of Christmas Day, it complained that I needed to update Logos to the latest version. Which seemed just to put me back into an infinite loop.I've uploaded terminal output and backtrace from my indexing crash at https://bugs.winehq.org/show_bug.cgi?id=47668
I'm also interested by the fact that some functionality hasn't worked for me under 64 bit, but does under 32 bit. Namely the help cards.Any comments would be gratefully appreciated.
Nick
0 -
Hey Nick,
I'm not sure on your help card issue. As for the indexer issue, in winecfg I have Logos.exe set to Windows 10 and LogosIndexer.exe set to Windows XP. You have to make sure that winecfg is run in the logos folder, for example 'winecfg /.wine/<name of logos folder>'
If you are still getting loop crashing, as you called it, you may want to back up your data directory and download the latest logos installer. run the installer and then move the resources back to the new data directory.
You can then run the Scan command in logos directing it to scan the new data directory.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Nick said:
I'm interested in this, because I'm getting problems. I'm using Debian Bullseye with wine-staging at 5-rc3, 64 bit.
When I try to install in win7, it automatically goes to indexing and crashes.I think that is supposed to work in rc3, is that the crash you reported on bugzilla at winehq?
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
John, Yes it is!
0 -
Voted on WineHQ AppDB as well, 75 votes and 22nd place [:)]
0 -
Have to say.... Having run Logos on Linux now for a while, it is working quite nicely.
Still running full 64 Bit across the board, with no indexing issues and very consistent performance. (Kubuntu 19.10, Logos 8.10 RC2, Wine 5.0 RC5 all 64)
I've been trying different tweaks to try to find what is causing the printing issue... So far, nothing has worked. But the removing corrupt indexes, allowing the indexer to complete in 64 Bit is good
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Just completed the upgrade to Kubuntu 20.04 - everything is running the same in regard to Logos. No issues found with the OS upgrade thus far. Seems the one drawback may be not having access to upgrading Wine, until they add a Focal repository
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Hi Daniel, thank you for your work on this. I followed the steps and everything looks like it installed correctly, but when I try to launch Logos I get target not found: /home/u/Desktop/Logos.sh.
I do see the Logos.sh in Desktop. Is there a different way I should launch this that I'm missing?
Running Manjaro Gnome
Husband, Dad, Expat to Northern Europe. I serve people, share hope, & write about simple theology for a messy life at genewhitehead.com.
0 -
Gene,
From a command prompt in a terminal, run ./Logos.sh
That's what I have to do in Ubuntu because the launch icon doesn't work.
0 -
Hi Gene,
I don't know if you've checked these things.
Your user name must be "u" so check permissions.Open terminal, and list the Desktop folder.ls /home/u/Desktop/Is Logos.sh there?If it is, check permissions using terminal.ls -l /home/u/Desktop/Logos.shYou should get back something similar to this. Ignore the numbers as I made those up:-rwxrwxrwx 2 u u 652 Jan 12 2020 Logos.shJust look at the -rwxrwxrwx and the ownership names "u u" as the file name, the rest I just made up.The parts that important are that there are x's in the first part and that your user name owns the file.Become root and chmod if you don't see rwxrwxrwx and chown if you don't own the file. Either condition will cause that error.Regards,David0 -
Gene W. said:
Hi Daniel, thank you for your work on this. I followed the steps and everything looks like it installed correctly, but when I try to launch Logos I get target not found: /home/u/Desktop/Logos.sh.
I do see the Logos.sh in Desktop. Is there a different way I should launch this that I'm missing?
Running Manjaro Gnome
You can use the same that the script at the end of installation run:
$HOME/Desktop/Logos.sh
But you should be able to run it from your Desktop with a double click (or using right click and on the "Run" option). If you have some bug/suggestion/comment... you can post a issue HERE too.
0 -
It seems that there is a new wine-stable: wine 5.0-stable, which works only with FAudio. I didnt have the time to check it out...
0 -
Ollie Pindakaas said:
It seems that there is a new wine-stable: wine 5.0-stable, which works only with FAudio. I didnt have the time to check it out...
I will wait for the release of "wine staging x86 v5.0" from playonlinux. They were able to compile only the "wine upstream x86 v5.0" version, but the "wine staging x86 v5.0" got an error. And I feel that the wine developers don't consider this v5.0 stable, but that they want to forget about supporting previous versions (because it hasn't had many tests yet).
0 -
John Goodman said:
I want us to be in the top 25, ideally ahead of the watchtower library app;)
*Done* [8-|]
Many greetings
Marc0 -
Ollie Pindakaas said:
It seems that there is a new wine-stable: wine 5.0-stable, which works only with FAudio. I didnt have the time to check it out...
Maybe are these three videos on YouTube helpful:
- Wine 5.0 on Ubuntu 19.10 > [View:
https://www.youtube.com/watch?v=uE-73Hjfy7s:550:0]- Wine 5.0 on ubuntu 18.04 > [View:
https://www.youtube.com/watch?v=sj08gKkHDpY:550:0]- Wine 5.0 on Mint 19.3 > [View:
https://www.youtube.com/watch?v=T6epKRoHpRw:550:0]0 -
Marc Zoellner said:John Goodman said:
I want us to be in the top 25, ideally ahead of the watchtower library app;)
*Done*
Many greetings
MarcAwesome! This is not just very helpful but also great witness! Well done folks.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
I'm having issues with indexing, as in, it churns away for a couple of hours and then throws an error. I found this post, which looks promising. Unfortunately, I don't understand how to do this step:
Frank Sauer said:After this, I double-checked that Logos.exe was set to Win10 and Logosindexer.exe was set to WinXP in winecfg and launched Logos.
Could someone break that down for a new linux user? Much appreciated,
Paul
[later...] I found a little snippet on the Logos 8 WineHQ page:
If indexing fails:
Set windows version for indexing
WINEPREFIX=$HOME/.wine-logos/winetricks winxpThis returned the error: "winxp: command not found"...
Frank Sauer said:Hopefully this is some good news....
I am running:
Kubuntu 19.10
Wine Staging 5.0 RC2 64 Bit
Logos 64 Bit
The indexer as has been noted was almost instantly crashing and changing the winecfg to Win XP as default nor as Win XP just for LogosIndexer.exe changed nothing - consistent crashes.
I decided to dig into the file system of Logos to see if I noticed any of the funky file issues we had way back in the beginning of the Beta testing days, when the indexer was first being introduced and quite volatile in behavior.
The Bible Index and Library index folders looked fine - the Personal Book index folder has a mess in it - a sign that there was possibly some corrupt files in there.
So I decided to clean out those directories after making sure that Logos.exe and Logoeindexer.exe were not running.
After this, I double-checked that Logos.exe was set to Win10 and Logosindexer.exe was set to WinXP in winecfg and launched Logos.
The indexer immediately started, the laptop went into full overdrive as the indexer is known to do and some time later - no crashes and a completed index running Logos 64 bit under Wine 64 bit. (this is Wine Staging 5.0 RC2 64 Bit)
The three folders should have 9 files in them - any more or any less and something is incomplete or corrupt.
The folders are located in:
/home/username/wineprefixfolder/drive_c/users/username/Local Settings/Application Data/Logos/Data/randomLogosnamedfolder
Replace the italicized portions of the path with you personal setup to get to the correct folder.
In the folder the three folders you want to check are:
BibleIndex
LibraryIndex
PersonalBookIndex
Each should have 9 files and the size all depends on the number of resources you have in your library (it can be many Gigs) - again any more or any less than 9 and that could be the issue. **(The 9 files is based upon my experience with successful installs and from my fully indexed Windows and Linux installs - Logos developers may know otherwise - purely a user experience observance)
To try out what worked for me you can delete the contents of each of those three folders or mock delete them by creating a folder in each and moving each folder's contents to the new folder.
0 -
Paul Unger said:
I'm having issues with indexing, as in, it churns away for a couple of hours and then throws an error. I found this post, which looks promising. Unfortunately, I don't understand how to do this step:
...
Download and use this script: https://github.com/ferion11/LogosLinuxInstaller/releases/download/v1.3/LogosIndexing.sh
Any issue with this, you can post here: https://github.com/ferion11/LogosLinuxInstaller/issues
0 -
Hi Daniel,
Thanks for offering to help. I don't know if you saw all of my post, but I'm a new Linux user, so: a) I don't know what you mean when you say to "use this script"--how?; and b) I wouldn't mind learning what's going on in your script. Maybe b) is asking too much...; but be that as it may, I definitely need help with a)!
Thanks,
Paul
Daniel Ribeiro da Silva said:Download and use this script: https://github.com/ferion11/LogosLinuxInstaller/releases/download/v1.3/LogosIndexing.sh
Any issue with this, you can post here: https://github.com/ferion11/LogosLinuxInstaller/issues
0 -
Download the script that is here.It's easiest to use wget. If wget isn't installed, install it.Open a terminal in your graphic user interface (GUI) then open a terminal, like mate-terminal or other terminal.Type this:cd DownloadsYou will have LogosIndexing.sh in the Downloads folder.Become root. Use su to do that and give the root password.suYour terminal turns from a $ prompt to a # prompt showing you are root.Now you have to chmod the script to make it executable.In terminal type:chmod +x LogosIndexing.shNow LogosIndexing.sh can be executed.In the same terminal, exit from root and you will be regular user.The prompt will change to $.Type this:./LogosIndexing.shWhen there some file that you want to run and it's not in a regular place that programs are kept (called the "path") you need to put ./ in front of the name of the file. If the file that you need to run is not in the directory that your prompt is, you need the full path.You can find out where your terminal is open by typing "pwd" which is short for print working directory.If you have any errors, you will be able to read them in your terminal.Just let the script work and work - it takes a long time.Best wishes,David
0 -
Paul Unger said:
Hi Daniel,
Thanks for offering to help. I don't know if you saw all of my post, but I'm a new Linux user, so: a) I don't know what you mean when you say to "use this script"--how?; and b) I wouldn't mind learning what's going on in your script. Maybe b) is asking too much...; but be that as it may, I definitely need help with a)!
Thanks,
Paul
Sorry. I always try to be concise here, as most of my comments are moderated by the forum (and take a while to appear).
My scripts don't need "root", so you just need "download" and "execute" ("run"). The "download" part should be just click on the link and the browser (like google-chrome) should download it. The "execute" part can be made by 2 steps:
1- Make it executable (because linux, for security reasons, don't use defaults executables, you have to explicitly said what you want to be one executable). And
1a- Right click on your .sh file and select "Properties".
1b- Click Permissions tab. And Select Allow executing file as a program.
2- Execute it by double-click (or single click, depending on your "File Management Preferences" preferences, because you can change this Behavior on linux).
Something like this: https://www.youtube.com/watch?v=RvKIN_z5QXQ
0 -
Thanks for the instructions--I appreciate that. Here's how it went: When I ran your script, I got the message, "The /home/username/.wine32 don't exists on your filesystem. Do you want to do Logosindex in another installation?" [No] [Yes]
I clicked [Yes]; selected my Wine Logos installation from the list that appeared; it downloaded something and churned away for about three seconds and then returned this message: "rndll32.exe This application could not be started. Do you want to view information about this issue?" [Yes] [No]
When I selected [Yes] a Windows Troubleshooting page opened in my browser, but the terminal then continued running some "winetricks" operations. After about 30 seconds of various winetricks windows popping up, it said Logos was indexing, and about 20 seconds later I was told it was finished and I was free to open Logos. That seemed incredibly quick, but I went to start Logos, and was told (via a Wine window) that the configuration had changed, and then the same "rundll32.exe This application could not be started. Do you want to view information about this issue?" [Yes] [No] error... When I clicked [Yes] another Windows Troubleshooting page opened in my browser, but Logos went ahead and started and my processor went to work. Opening System Monitor shows that Lgosindexer.ex is using 23% of my CPU (as it was earlier), but there isn't any indication in Logos that indexing is happening (i.e., the notification beside the Sync arrows).
In short, I'm afraid the script didn't work--this is exactly what was happening earlier. And I'm also afraid that my configuration in knackered... :-( Thoughts?
0 -
Paul Unger said:
...
In short, I'm afraid the script didn't work--this is exactly what was happening earlier. And I'm also afraid that my configuration in knackered... :-( Thoughts?
The Frank Sauer have reported one bug of LogosBible 64bits on linux about this issue: https://community.logos.com/forums/p/121/1081685.aspx#1081685
You could try the same solution. Or just install LogosBible 32bits too.
I know that LogosBible itself have better support on windows 64bits. But the wine 64bits (that run LogosBible on linux) is very new and have a lot of bugs. If you want avoid bugs, you should try the 32bits version.
0 -
Well, that's where I started, Daniel. :-P Asking how to perform an instruction from Frank Sauer's post:
Frank Sauer said:After this, I double-checked that Logos.exe was set to Win10 and Logosindexer.exe was set to WinXP in winecfg and launched Logos.
Which is when you suggested your script. ;-) Do you know how to do what Frank suggested? Thanks for any instructions, if you do!
Paul
Daniel Ribeiro da Silva said:The Frank Sauer have reported one bug of LogosBible 64bits on linux about this issue: https://community.logos.com/forums/p/121/1081685.aspx#1081685
You could try the same solution. Or just install LogosBible 32bits too.
0 -
Paul Unger said:
Which is when you suggested your script. ;-) Do you know how to do what Frank suggested? Thanks for any instructions, if you do!
Paul
No. Each Linux distribution has its own compilations for many versions of WINE, and the problem is even worse if we talk about the 64-bit version. I prefer stability. And the 32-bit version works better.
Because of this, my installer uses the 32bits version (inside one AppImage) with all dependencies, in order to ensure that the operation will be the same in all linux distributions. Outside of this, each case is unique.
0 -
Good news: The wine 5.1 is out and have fixed the Logos 8 bug (about the ReOpenFile implementation). Then you don't need the wine staging for this anymore (and the implementation of normal wine should be better than the wine staging).
The vote is already producing results (I'm impressed).
0
