Linux version of Logos Bible Software
Comments
-
Paul Unger said:
As for my install, I have Logos up and running again (had to download 3.9 GB of my 20 GB of resources...), but indexing is still throwing errors. I'll see if any of the workarounds work.
I have been confused by indexing errors..... sometimes it seems that people report there are errors, but still in the end indexing completes. You can check "System Monitor" to see if any process related to indexing is still running (if so, maybe it will complete even though it gave errors?). Sorry I haven't re-installed a clean Logos setup in a while to better understand the indexing issues.
Regarding the AppImage instructions, sorry you got confused using those. For reference, I put a link to the AppImage github home in the main Ubuntu / Wasta-Linux Logos Installation Guide so people can find reference to this alternative / more "cutting edge" process more easily.
Daniel has pretty detailed instructions in the README.md, but I think you are right it isn't completely clear what you download from the "Releases" page. You want to download the "standard" .sh file (sorry I haven't kept up on what the difference is with the "fast" .sh alternative file). Then proceed with step 0.1 (chmod +x on the downloaded .sh file). I am sure he would like help in re-wording anything that is confusing for users, so please create issues at that github site for things that need more clarification.
0 -
You're way ahead of me in terms of what you're trying, Purist, but I wonder if "ntlm_auth" is part of Windows's "NT LAN Manager" (see https://en.wikipedia.org/wiki/NT_LAN_Manager, and https://docs.microsoft.com/en-us/windows-server/security/kerberos/ntlm-overview)? Just a shot in the dark, but if it helps you along, maybe it's worth it (as it may help me eventually, too!).Purist said:My indexing stopped working on Ubuntu 18.04.
...
I tried to install via Daniel's script, and got an error saying "Your system does not have the command: ntlm_auth. Please install ntlm_auth package" I haven't been able to find this package in spite of my search online.
I don't have a preference between Daniel's script and wasta-linux, but I do want to get indexing going again. What would you all recommend?
Thanks.
0 -
Some things I've noticed about Indexing behaviour when it fails:
1. Usually when Logos is "doing" something--updating, syncing, indexing--there's a blue number in the upper right of the menu bar. When indexing, there's also a progress indicator (x%). When I start Logos, my CPU ramps up, the fan starts whirring, and the process "LogosIndexer.ex" starts (NB that's not a typo), but there's no blue number in the Logos menu bar, and no indication of progress--none of the usual indicators, in other words, that Logos is "doing" something.
2. I'm curious about the process name "LogosIndexer.ex". The command line (found with a right click > Properties) is: C:\users\username\Local Settings\Application Data\Logos\System\LogosIndexer.exe, so maybe it's just the name that isn't .exe. But the other Logos processes have the full .exe in their names: LogosCEF.exe and Logos.exe. Like I said, I'm curious...
I don't know if that's helpful for troubleshooting, but there you have it. I have also saved a log from the crash report, if that would be useful to anyone.
0 -
Paul, using the wasta-logos-setup install, you can manually start the indexer this way:
WINEPREFIX=$HOME/.wine-logos/ /opt/wasta-wine/bin/wine $HOME/.wine-logos/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/System/LogosIndexer.exe
At this point I am not certain my indexing is complete.... it does seem to end in an error with some "deadbeef" output which is never good :-( I know that Indexing is completing much quicker using the newer wine versions from the AppImage method. It will take some testing and review if it is reliable enough to move wasta-logos-setup users to or not.... I fear it isn't quite ready. But if we can't get indexing to work at all currently that isn't good!
0 -
Purist said:
I tried to install via Daniel's script, and got an error saying "Your system does not have the command: ntlm_auth. Please install ntlm_auth package" I haven't been able to find this package in spite of my search online.
When I recently installed Logos using Daniel's script, I ran into this. IIRC, I solved the issue by installing the winbind package. There also were a couple of others I had to hunt down and install.
0 -
I'm sorry. Since July 2020 everything started to fall apart. The installer script stopped working, the old portable version didn't worked anymore, and I was never able to update LogosBible again (on every update after this, i'm removing and installing it again). The wine-5.x version was using a lot of CPU, and it was very hard to use here (slow machine). And with wine-5.17, even the WINE AppImage using 32-bit dependencies have stopped working as well.
We made progress too, but like I told John Goodman on telegram, each 32-bit proper build and test takes about 1 hour (if we go fast), and each regression test needs somewhere around 10-15 builds. So something like 1 hour x 12 = 12 hours. And if we need to test the 64-bit version, the proper compilation and testing takes around 2 hours (because the 64bit version needs the 32bit version working at the same time). So something like 2 hour x 12 = 24 hours (again, if we go fast with the test). So it take some time to do even simple things like one regression test. The WINE project kinda implements one entire operating system, which is quite large.
Well, we can only do what God allows us to do. And at the moment I don't feel confident about making recommendations. Maybe just one: try to wait a little longer with the versions that are still working, and use the new ones just for testing, so you will always have a working version.
I separated the Changelog from the release page (making it cleaner), and put the description of the files in it. I also made a short video of 00:02:38 with the installation done with fast_install_AppImageWine_and_Logos.sh, and put the link in the step "00- Download and execute:", right at the beginning. I was unable to post it on youtube (upload stops at 1%), so I hope everyone can download and run it locally.
And may God bless us.
0 -
Hi Daniel,
This is immensely helpful, and I appreciate all the work you have put in. The video works. I did not know I needed to install those two packages, and now the installer is up and running.
One more question for the "wasta" experts: Assuming Daniel's script installs, how do we remove the wasta-wine version of Logos from the applications? I know how to run "wine uninstaller" but obviously the application isn't listed there.
Grateful for the help.
0 -
That's a very helpful update, Daniel! It's always good to know that one is not alone. And that the issues one is facing are being faced by others with a chance of sorting them out (I don't have a chance...). ;-) I have a working version (Logos 8.13 on Wine 4.18); I just can't get indexing to complete. That doesn't seem to be affecting anything I'm doing in Logos right now, so I'm not going to get too upset about it. In fact, it sounds like I should be quite thankful about that, and I am.
I'll have a look at the video you posted. It sounds like the "cleaner" website will make more sense to me now. Thanks!
Let me just say that I appreciate the effort and time the developers have put into getting this project as far along as it is--more than I can say. Honestly, God has blessed us through your and the other developers' efforts! I'll say a prayer for His continued blessing, and that He'll show you guys the way forward. ;-)
0 -
I followed the AppImage video Daniel created and my new Logos install is now (drum roll please...) indexing! I also changed the icon to match the "stock" Logos icon that installs with the wasta-wine version.
A huge thank you to everyone who continues to make this possible.
0 -
I am on a chromebook and have Logos working in the linux environment (thanks to this awesome group). It has been up and running for a few weeks now. All of a sudden my clipboard doesn't seem to be working between Logos (Linux env) and my ChromeOS. Any idea what to try?
0 -
I did some more testing to narrow it down. The clipboard works in all my other Linux apps except Logos. It used to work so I am not sure what might have happen. When I say works, I mean I can Ctrl+C or Right click and hit Copy and go in my ChromeOS environment, say Google Docs, and do a paste.
0 -
I used Daniel's script to install Logos on my chromebook in the standard Debian Buster container. Everything was working, but now the program will launch and just before getting to the desktop, the error box stating Logos.exe has encountered a serious problem and needs to close box appears. Clicking both Show Details and Close exits the program.
0 -
Rob Perry said:
I did some more testing to narrow it down. The clipboard works in all my other Linux apps except Logos. It used to work so I am not sure what might have happen. When I say works, I mean I can Ctrl+C or Right click and hit Copy and go in my ChromeOS environment, say Google Docs, and do a paste.
WINE doesn't have all the clipboard functionality implemented yet, so depending on how your system is using it, the clipboard may not work.
A possible workaround would be to run the register:
* For the 32bit version:
$ ./Logos.sh wine regedit* For the 64bit version:
$ ./Logos.sh wine64 regeditand use the key:
[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"UsePrimarySelection"="1"In the future we will try to implement this functionality in the WINE code, but first we will have to make LogosBible be able to use the latest version of WINE as default.
Bill Anderson said:I used Daniel's script to install Logos on my chromebook in the standard Debian Buster container. Everything was working, but now the program will launch and just before getting to the desktop, the error box stating Logos.exe has encountered a serious problem and needs to close box appears. Clicking both Show Details and Close exits the program.
Could you tell us which installation script was used and which installation option was chosen?
You can try to run it from the terminal:
$ cd "${HOME}/LogosBible_Linux_P"
$ ./Logos.sh
then when you receive the error and close LogosBible, copy everything you can from the terminal and post it at "pastebin.com" (and post the link here).0 -
I am not sure if I did this right. I added a registry key with a value. Below is a picture. I retried my scenario and a copy and paste doesn't seem to take still. Let me know if I failed to set the key right. Thank You!
0 -
Rob Perry said:
I am not sure if I did this right. I added a registry key with a value. Below is a picture. I retried my scenario and a copy and paste doesn't seem to take still. Let me know if I failed to set the key right. Thank You!
...
Half correct. The "X11 Driver" is a Key (shown as a folder) and is right, but the "UsePrimarySelection" is a "String Value" with the name "UsePrimarySelection" and value of "1" (shown as if it were a file).
0 -
Daniel Ribeiro da Silva said:Bill Anderson said:
I used Daniel's script to install Logos on my chromebook in the standard Debian Buster container. Everything was working, but now the program will launch and just before getting to the desktop, the error box stating Logos.exe has encountered a serious problem and needs to close box appears. Clicking both Show Details and Close exits the program.
Could you tell us which installation script was used and which installation option was chosen?
I used the fast install script and selected option 1. Terminal output is attached. Sorry, I have not used pastebin.4643.Output.txt
0 -
Bill Anderson said:
...
I used the fast install script and selected option 1. Terminal output is attached. Sorry, I have not used pastebin.4643.Output.txt
Don't worry, pastebin was just my usual suggestion (because the Gentoo Linux forum doesn't allow attaching files).
Your log indicates that the dotnet is failing when trying to obtain the "Display" resource. And since everything was working before, this resource was probably blocked for security reasons.
You can try to run a simple window with the LogosBible WINE to test, like:
$ cd "${HOME}/LogosBible_Linux_P"
$ ./Logos.sh wine notepadand the old and simple Windows notepad should appear.
0 -
Daniel Ribeiro da Silva said:Bill Anderson said:
...
I used the fast install script and selected option 1. Terminal output is attached. Sorry, I have not used pastebin.4643.Output.txt
Don't worry, pastebin was just my usual suggestion (because the Gentoo Linux forum doesn't allow attaching files).
Your log indicates that the dotnet is failing when trying to obtain the "Display" resource. And since everything was working before, this resource was probably blocked for security reasons.
You can try to run a simple window with the LogosBible WINE to test, like:
$ cd "${HOME}/LogosBible_Linux_P"
$ ./Logos.sh wine notepadand the old and simple Windows notepad should appear.
The old Windows Notepad does appear. The issue persists when I try to run Logos.
0 -
Bill Anderson said:
...
The old Windows Notepad does appear. The issue persists when I try to run Logos.
Interesting. I can think of some possibilities:
1- The installation of dotnet was corrupted by issues in the file system.
2- The last update wasn't completed successfully and left LogosBIble in an inconsistent state.
3- Your setup has become complex enough that the dotnet inside the WINE can no longer access the Display. Being a possible WINE's bug.I would try to do another installation (reinstall) of LogosBible and check if the same issue happens again.
0 -
Daniel, thank you so much for your help, and patience, for what is probably a basic question. I think I have the key right now. The clipboard works within Logos but it still doesn't work between other linux apps and my chromebook environment like it once did.
0 -
Rob Perry said:
Daniel, thank you so much for your help, and patience, for what is probably a basic question. I think I have the key right now. The clipboard works within Logos but it still doesn't work between other linux apps and my chromebook environment like it once did.
...
Yes, that's correct. And as far as I know, at the moment this is the best that WINE can do (for now).
All that remains is to know how your graphical interface is handling this. For example there are known bugs, and work being done at this point of time, like this: https://gitlab.gnome.org/GNOME/mutter/-/issues/13380 -
I just updated my chromeOS to Version 86.0.4240.112 (Official Build) (64-bit) and things are working again. I can Ctrl+C / V in and out of Linux and my ChromeOS environment.
0 -
Does anyone know where to download the LOGOS 9 MSI or how to find out? There is no version number for 9 in the Wiki yet. Greetings Dominik
0 -
Logos 9 update applied automatically to my Logos 8 AppImage (Daniel's edition) on Ubuntu 18.04. It redownloaded all resources as well. Now my Logos is broken again - crashes on start.
When I click "More Details" on the crash report the dialogue box disappears without showing any error reports. Any tips on how to get it running again?
Also, what do we think of setting up a way to incentivize our volunteer developers, i.e. put a reward out there for folks like Daniel (and others) to upgrade the AppImage to Logos 9? Would that be legit and/or helpful?0 -
I have tried to install LOGOS 9.0.0.0168 with the "LogosLinuxInstaller" script. The installation worked fine. Logos can also be started, but it looks like this now. Everything is black. When I hover the mouse over some of them, that part appears and the rest is black. I use "WINE64bit 5.19" with "Fedora 33". Greetings Dominik
0 -
Is it possible it is in dark mode? First time logos opened after the update, it was black in windows as well. I think they were showing dark mode. In settings, it can be changed back. Only a guess...
0 -
The problems are the same in dark mode as in light mode with Wine64bit 5.19.
In the meantime I have tested it with the Appimage 64Bit 5.11. So LOGOS quits after a short time and doesn't find the cover images from the resources. But the error with the black areas is not there.
In the console I keep seeing the following error message:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.8
0 -
Dominik,
Did you do a fresh install with the latest installer in your Downloads folder? Mine updated from within the app, so if yours was a fresh install I will try that route and report back.
0 -
Yes it is a fresh installation with a copy of the folders "Data", "Documents" and "Users" from my Logos 9 Installation on Windows. I used the "ferion11/LogosLinuxInstaller" and changed in line 8 "LBS8" to "LBS9" and "8.17.0.0011" to "9.0.0.0168".
0 -
Are you signed in with an account which has a L9 license?
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0
