Linux version of Logos Bible Software

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.

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!).

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!

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.

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. ;-)

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?  

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.

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!

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

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 notepad

and the old and simple Windows notepad should appear.

The old Windows Notepad does appear. The issue persists when I try to run Logos.

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.  

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.

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?

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...

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.

Are you signed in with an account which has a L9 license?

Logos 9  installs using install_AppImageWine_and_Logos.sh script.

 When Logos 9  starts it does not run long. Attached is the backtrace from Wine.

Thanks for all the work the Linux team is doing.

(Lubuntu 20.04)

1447.Wine-20201027-backtrace.txt

6330.TerminalOutputLogosWine.txt

John Goodman said:

The terminal output is usually much more helpful than the backtrace. If you can attach the terminal output that could help. Thanks.

John:

         Please find attached the terminal output which occurs shortly after Logos 9 starts up. (Lubuntu 20.04.01 LTS).

         Thanks again for all the work you Daniel, Rik and others are doing with Linux and Logos.

That's exactly what I'm seeing, Rob.

Al Graham said:

Logos 9  installs using install_AppImageWine_and_Logos.sh script.

 When Logos 9  starts it does not run long. Attached is the backtrace from Wine.

Thanks for all the work the Linux team is doing.

(Lubuntu 20.04)

1447.Wine-20201027-backtrace.txt

You are being quite adventurous here. Using your native, old, wine-5.0 (vanilla), without any patches (nor the staging set), and still trying to do the installation using install_AppImageWine_and_Logos.sh.
If the goal isn't the adventure, and you just want it to work, then install using the script fast_install_AppImageWine_and_Logos.sh and select the option with the AppImage.

Rob Perry said:

Indexing is running after a large update and it doesn't seem to finish.  I've tried several times to rebuild via ./Logos.sh removeAllIndex followed by 'indexing'   It is running but I see the attached error message.  I see it if I start Logos.sh and it kicks off indexing or if I run indexing directly.  Is this a normal error message?  Anything else I should try?

This message is quite normal. And in fact at the end of the index, it seems that the LogosBible index stopped for good (in my case it was 51%). You can see this through the CPU usage by the index process. But after closing and reopening, the index was ready and working. At least that's what happened here. But we don't have much guarantee due to the recent changes.

Al Graham said:

Daniel:

          Thanks for your help.

          Attached is the terminal output when I use fast_install_AppImageWine_and_Logos.sh.

...

You are getting the error message:

err:seh:segv_handler_early Got unexpected trap 6 during process initialization

This kind of error normally happens when using liveUSB and WINE cannot write to the USB, or when using liveISO in RAM and you don't have enough RAM to write all the data. But that doesn't seem to be the case here.

I saw from your previous log that you are using Ubuntu, but I don't know which version. Perhaps some incompatibility with glibc (one Ubuntu update maybe can solve it).
A good try would be to install wine-staging-5.11 from winehq.org:
wiki.winehq.org/Ubuntu

using something like (you can change the "bionic" to your version):
sudo apt-get install winehq-staging=5.11~bionic wine-staging=5.11~bionic wine-staging-amd64=5.11~bionic wine-staging-i386=5.11~bionic

then try using the option with native WINE on fast_install_AppImageWine_and_Logos.sh

This will ensure better compatibility with glibc.

I would like to make one AppImage with all dependencies for 64 bits (including glibc), as I had done for 32 bits, but there are some technical impossibilities, like the double glibc combo for WINE WoW64 (and now a new bug too), that has been holding me back for quite a while. For only then, we could have more guarantee that all the installations would behave in the same way. Without me having to say that it works very well on the test server using Ubuntu bionic (and on my local machine using Gentoo Linux), as you can see here: github.com/ferion11/LogosLinuxInstallTests/releases/download/v2.20/videoa.mp4
But for now, we will have to live with the peculiarities of each Linux distribution and its different versions too.

Purist said:

I'm getting the following error during a fresh install on Ubuntu 20.10. I have installed on this OS before without errors, but I see that the fast_install script was updated 2 days ago.

"./fast_install_AppImageWine_and_Logos.sh"

Returns:
./fast_install_AppImageWine_and_Logos.sh: line 6: syntax error near unexpected token `newline'
./fast_install_AppImageWine_and_Logos.sh: line 6: `<!DOCTYPE html>'

Any suggestions are much appreciated.

You downloaded the wrong file.
We can easily be fooled with the "blob" version (made to be used only by the web browser) instead of the "raw" version (the real file) in the URL. They are generally similar in size and have the same name too, but the blob format is html, and the raw, in this case it would be a bash script.
The raw link for the v2.20 is:
https://github.com/ferion11/LogosLinuxInstaller/releases/download/v2.20/fast_install_AppImageWine_and_Logos.sh

For me the script (v2.20 fast AppImage) works very well on Ubuntu 20.10. I only changed the LOGOS version number in the script to 9.0.0.0181 before I ran it.

Thanks a lot for the good work. [Y]

Rik Shaw said:

for those taking the conservative route waiting for 64-bit wine to be more stable, it seems like a good option to update to this "last of the 32-bit installers

I appreciate this, Rik. I am currently on Logos 9 64-bit AppImage, with no indexing or search features working. I'd love to revert, but I wonder how we can keep Logos 8 from updating to Logos 9 from within the app itself. Is there a "Do Not Update" setting somewhere?

Also, do you know if those of us with version 9 licenses and features activated can go back to v.8?

That's funny. I just ran it without "sudo" and it started the installer. It proceeds until I say yes to corefonts, then hangs:

------------------------------------------------------
Running /opt/wasta-wine/bin/wineserver -w. This will hang until all wine processes in prefix=/home/purist/.wine-logos terminate
------------------------------------------------------

Rik Shaw said:

It may be that we need to roll back to the "safe" wine 4.18 for Ubuntu 18.04 users. Using 4.18 means it will take longer to install, but it may be "stable". I'll report back after further testing.

I have rolled back wasta-wine to version 4.18 for Ubuntu 18.04 'bionic' users. If you already installed wasta-wine version 5.20 then please remove it, and then install wasta-logos-setup again which should bring in wasta-wine version 4.18.

Negatives of version 4.18 of wine include a much longer .NET 4.8 install (with it sometimes "hanging" meaning you may need to force close it and re-run wasta-logos-setup again to hopefully get it installed). It could take around 40 minutes (or more!) to complete the .NET 4.8 installation (compared to about 6-7 minutes for wine 5.20 in Ubuntu 20.04). Additionally, running Logos with wine 4.18 will result in an initial crash the first time you start Logos. Just restart Logos and it should work the second time.

So in summary, Ubuntu 20.04 / 20.10 with wasta-wine 5.20 (staging) is preferred, but for the 18.04 users at least Logos should remain functional using the older 4.18 wasta-wine version.