Linux version of Logos Bible Software
Comments
-
Care to share why it fails?
0 -
The wiki on the installer site does contain info on how to manually install including where to find links. Unless it was archived with the ferion script but that is still searchable on github.
The reason it fails here: https://bugs.winehq.org/show_bug.cgi?id=57674
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
One advantage @Taylor and the Linux team have provided is to allow Logos to run on older computers.
I run daily on a 2006 Dell XPS M1330 SSD long since ready for the land fill.
A native Linux version may never be seen and over the years the Wine version has had problems.
The current project Oudedetia has come very far and may have problems in the future.
It seems many more people are involved and problems are solved in a timely manner.
It is not for everybody, may God bless the people for their work.
0 -
I've been using Logos on Linux for about 5 years. I'm very grateful to those who have poured hours into making this possible! I'm quite contentedly using v. 25. Would I gain significantly by updating to v. 38 (or 39…)? Is there a way to retain settings, layouts, etc.? Advice appreciated!
0 -
Your settings and layouts will stay… its low risk to try it. Rename your current wineprefix dir from eg. LogosBible10 to LogosBible10-backup. Use the script to install the latest version. If you like it delete the old one. If you don't have the disk space you can backup the old one onto an external drive. I do this a lot because I test the installer against new wine versions etc.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Here's a direct link to 38.1.0.0002.msi
https://downloads.logoscdn.com/LBS10/Installer/38.1.0.0002/Logos-x64.msi
It would be helpful to maintain a list of old known working installers outside of the githib script.
1 -
Thanks John. I tried using the script to install the latest version. Everything seemed to go fine—no errors or stalls—until I tried to run Logos. I get a new (to me) splash screen, and then a sign in window. I enter my credentials and… nothing…
I went back through the thread here to look for a solution, but didn't find anything. I have a new LogosBible10 folder (I renamed my old one as you suggested). The splash screen says v38 was installed. I have new shortcuts in my main menu. Anything else to try?
0 -
A new version of the script will be published in the next couple of days which will resolve those install issues sorry. Those not using the script, I can't offer to support due to time constraints. The script and the telegram / matrix channel is where we can support you. To use crossover, you will need to copy how we do it. There is a pr on github where you can see the solution the script uses - I hope that helps! You're looking to use the mst file with the msi file to enable the msi to progress.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
1 -
Thanks for the reply, John. I can easily wait a few days for a new version of the script—the version I'm using is working fine, and I've waited this long to even consider updating. ;-) I fully understand 'time constraints,' and will certainly respect yours. Thanks for continuing to work on this project!
0 -
I'm pleased to announce I have a fix for the menu bug as well. For me, this was probably the hardest computer thing I've ever done. It required a small patch for wine itself so will need to go through a code review and testing process before it makes it into any public binaries. At this stage it is perhaps proof of concept but anyway… its coming soon!
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Is this the old need to multi click the menu choice bug? Awesome!!! Congratulations
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
And I've had a message from Bradley saying they will likely release an update to v39 which installs on Linux without the mst soon - another of many examples showing Faithlife are great at responding to customer feedback and do care enough about Linux users to offer us help!
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Yes that's the one! https://bugs.winehq.org/show_bug.cgi?id=52380
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
1 -
That was annoying, that will be nice to not have to use the work around that brought it's own frustration!
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
I've been having some issues with this program, so I'm very happy to find such recent discussion on here!
I see some talk about a forthcoming new installer script, and perhaps that will solve my problem, but I'm unsure.I had had Logos working perfectly on Ubuntu using Ou Dedetai, but I then had to install another program using Appimagelauncher, which had previously been uninstalled by Ou Dedetai. After finishing that, I tried opening Logos again to reach the prompt to uninstall Appimagelauncher again, but instead my screen went grey, telling me that an error occurred and that I needed to log out. This would happen consistently each time I tried, so I searched for all Logos-related files and deleted them, as well as all Appimagelauncher related files, and attempted a full reinstall. This also failed, though. I could get to the login screen, and then select what resources I wanted to download, but after that I got both a small box saying that the installation had failed, and the window with a progress bar for resource download. That progress bar made it to 60% on two different tries, but each time I ran into a fatal error.
If anyone understands what might be going on here, I'd appreciate advice! Or if this new install script could solve this, I wouldn't mind waiting.
Thank you for all the work that's gone into this!
0 -
v39 issues resolved with the newly released v4.0.0-beta.6 . This release includes:
- Recovery in case an install is upgraded to v39+ within the Logos app from before thanks to Nathan Shaaban
- New wine version 10 (which also happened to fix the bug where logos would crash while downloading resources for the first time) thanks to T. H. Wright for keeping an eye on wine-10. This also might resolve the menu bug for some users.
- v39 clean msi install thanks to John Goodman m0rvj
- Increased code robustness thanks to Nathan Shaaban with feedback from T. H. Wright and n8marti
All in all a team effort through and through. Thank you for your patience now on to read our wonderful God's word!
cc: @Paul Unger
1 -
Thanks for this! Unfortunately, it doesn't seem to be working.
But maybe I didn't start off on the right foot? How do I proceed given that I have an existing install using oudedetai? Is it just a matter of deleting the install folder "LogosBible10" that it installed previously? That's what I did, but it doesn't seem to have been enough.
Details: I used the GUI option. 'Install' went seamlessly. When I click 'Run Logos' in the Ou Dedetai control panel, I get the Logos splash screen (v. 38.1), and then a Faithlife login screen. I enter my credentials and, nothing… There is an instance of Logos.exe in my 'System Monitor' (this didn't appear with the previous version of Ou Dedetai), but it shows 0% CPU use and 'N/A' for memory, disk read, disk write, etc. No change after at least 10 minutes. In fact, it's so 'inert' I can't even 'End / Kill Process' it.
If you could point me to where I could find an install log, I'd happily submit it.
0 -
The continual improvements are encouraging!
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
I tested Logos v39.1 perhaps try using that. Regardless the log is under ~/.local/state/Faithlife-Community/oudedetai.log ~/.local/state/Faithlife-Community/wine.log ~/LogosBible10/data/wine64_bottle/drive_c/users/*/AppData/Faithlife/Logos/Logs/LogosLog.txt
To be clear: when is it stopping? Right after you put in your credentials or one screen later? Hitting continue after selecting how much of your library to download? If it's the latter can you check which wine version is in ~/LogosBible10/data/bin/wine- ? It should be 10.0-rc5. If not I'd like to see your log (to help other users), and you should be able remove ~/LogosBible10 and ~/.config/Faithlife-Community/oudedetai.json and ~/.cache/Faithlife-Community/network.json then try again. We understand gathering these files could be easier, created a github issue for further improvement in the future
0 -
Hi Folks, Just want to let you know that I appreciate all the work you are doing. My main workstation is running OpenSuse Tumbleweed. I did try to install Logos a while ago but didn't succeed. Most likely I'll try again soon. Thanks again, All the best
0 -
I'm currently downloading and indexing! I removed oudedetai.json and network.json from the folders you mentioned in addition to /LogosBible10, and tried again. Unlike my earlier attempt (when I just removed /LogosBible10), this time it downloaded things, set renderings, configured fonts, etc., which all took a while. I don't recall these things happening when I tried this morning—it all went very quickly. So I think I'm over the hurdle! Thank you.
Re. To be clear: It was stopping right after I put in my credentials—there was no other Logos screen that appeared after that. I have oudedetai and wine logs from the failed attempt, along with a LogosError.log I found:
Program Version: 38.1 (38.1.0.0002)
Windows Version: 10.0.19043.0
.NET Framework Version: 8.0.10
Time: 2025-01-23 07:35:12 -08:00 (2025-01-23T15:35:12Z)
Installed memory: 15,395 MB
Install path: C:\users\*\AppData\Local\Logos\System\Logos.dll
Free install space: 130,409 MB
Temp path: C:\users\*\AppData\Local\TempFree temp space: 130,409 MBProgram Version: 38.1 (38.1.0.0002)
Time: 2025-01-23 07:35:12 -08:00 (2025-01-23T15:35:12Z)
SQLite Error 2058: os_win.c:49869: (33) winUnlockReadLock(C:\users\*\AppData\Local\Logos\Users\UserManager.db.create) - Lock violation.0 -
Debian 12 Bookworm with CrossOver allowed Logos to self update from 38.1. Splash screen showed 39.1 About logos showed 38.1. Downloaded LogosSetup.exe from logos.com and installed it into the same CrossOver bottle. I was given a repair or remove option. Clicked repair. Logos splash screen shows 39.1, About logos shows 39.1. Everything seems ok. Will do some testing on a few things I know weren't working properly in 38.1 and see how it goes.
Thank you for working with devs to keep Logos working in WINE/CrossOver.
0 -
Here's an issue I get only with Linux. Every major update, whether its a Logos update within Logos or I download the installer and update that way, deletes the vast majority of my library and then redownloads the entire library. Has anyone had anything similar?
0 -
Many of us kept a backup of the 'Data' 'Documents' and 'Users' folders located in the Logos folders for this reason. I haven't been involved for a little over a year - so some of the current Linux team could give you the best insight.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Hopefully you can get Logos running - Tumbleweed was my most stable install when I was involved.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
This issue seemed to have been resolved for quite a long time. Is this happening to you still?
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Yes that is why I posted about it. How was it resolved?
0 -
I just installed 39.1 over my 38.1 in my CrossOver instance on Linux Mint. So far it seems to be working fine; the only issue I'm noticing (even with 38.1) is when I initially open the app and click on the layouts to re-open my saved layout, it opens everything fine, but clicking on the layouts button again starts to flicker by instantly opening and closing, and I can't open other saved layouts until I completely close and re-open the app. The same is present when trying to open Tools. Initially it works then starts to instantly open and close.
I have a backup instance of Logos on a custom (completely debloated) Win 11 VM that's strictly used for that in case I want stability for deeper work.
0 -
We had many updates with no data loss so presumed it fixed. I thought it was due to an update in wine. Can you tell me which wine version you were using and which version of Logos you updated from and to?
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Ultimately if you can make it work for mac you can make it work on Linux. Just target Linux Mint, currently the most popular distro.
0