Linux version of Logos Bible Software
Comments
-
That figure seems incredible to me... I wonder what the actual user base Logos is? And what is the user base of the forum? Is it being found by people who are searching for the tux mascot?
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
John Goodman said:
Is it being found by people who are searching for the tux mascot?
I think there's something to that guess; this thread is the #3 result in Google for "linux logos":
0 -
David Wanat said:
I wonder how many users that breaks down to With multiple visits.
I suppose many are wondering. I follow the thread because I would love to see Logos on Linux. My son is using Logos on Windows and got it working on Linux, but there are still issues to be worked out.
0 -
Aren't there any plans from FaithLife to compile Logos to a .deb package?
0 -
No. Nor should there probably be at this point, because (sadly) there are not enough Linux users to make it worth their while. Also, while things are getting a LOT better regarding running Logos on Linux using WINE there are still issues to be worked out. Those matters are being worked on right now, and the future looks good. Were Logos to officially support Linux, the way for them to do that would be with the Appimage method which is currently the officially recommended way to install Logos on Linux.
The only thing which would probably make Logos reconsider supporting Linux is if they wanted to enable users to run Logos on Chromebooks. I suspect that there are many more Chromebook users than general Linux desktop users. The process being worked on now would work for Chromebooks. That's an option for Faithlife folks to consider.
0 -
Logos is built on the .NET platform, which Microsoft contributed to open source a few years ago. The developers of .NET are making remarkable progress towards a completely interoperable platform. Version 5.0 of .NET (the release candidate version is already available) installs natively on Linux. I suspect that within a couple of years, there simply won't be anything for the Logos developers to do for Linux support. Linux will, once again, Just Work.
0 -
I am trying to install Logos on my PixelBook in the Linux environment. It looks like you got it working. Would you mind pointing me to the instructions?
Thank you!
Rob
0 -
Rob, welcome to the forums.
Are you running the standard Debian container on your Pixelbook?
0 -
Yes, but willing to do anything to try and get logos on there ;-)
0 -
I'm actually in the process right now of using Daniel's appimage installation on my Pixelbook Go.
https://github.com/ferion11/LogosLinuxInstaller
I had to install some dependencies -- zenity, x11-apps and a couple of others before the installer would run. I'm indexing now.
0 -
Thank you so much. I am heading to spend some time trying to get this on. Can't wait!
0 -
Everything went as documented. When I start Logos I get the attached picture. It is the control panel. I see Logos is installed. It might be that an environment variable is not set. If you have any ideas, shoot them my way. Thanks so much everyone!
Rob
0 -
Rob Perry said:
Everything went as documented. When I start Logos I get the attached picture. It is the control panel. I see Logos is installed. It might be that an environment variable is not set. If you have any ideas, shoot them my way. Thanks so much everyone!
...
You can remove the LogosBible_Linux_P folder in your $HOME, then:
Please try again using the fast_install_AppImageWine_and_Logos.sh script, as there are still some bugs in both wine and winetricks that in some cases make this kind of bug appear.
0 -
That did it! Everything is installed and I can move about. Indexing starts and causes a windows 'system error must close' I believe I saw others mention this so I will go and research how people got through it.
0 -
Rob Perry said:
That did it! Everything is installed and I can move about. Indexing starts and causes a windows 'system error must close' I believe I saw others mention this so I will go and research how people got through it.
You can try the index without running the LogosBible with:
And if you want to use the Frank Sauer workaround:$ ./Logos.sh indexing$ ./Logos.sh removeAllIndex
If you want one link to your LogosBible dir inside the wineBottle to make manual changes (like backup before update):$ ./Logos.sh indexing
If you want one shortcut LogosBible.desktop in your ${HOME}/.local/share/applications (many linux distribution use it to add it on the apps menu):
$ ./Logos.sh dirlink$ ./Logos.sh shortcut<br />
0 -
And once Logos finishes indexing, create a copies of the index folders--and update them from time to time!--to avoid having to wade through the (potentially hours of) indexing again.
0 -
Has anyone else come across updates to libsdl2 that wants to remove Wine in order to update? Can't update or remove it to reinstall without removing Wine.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Frank Sauer said:
Has anyone else come across updates to libsdl2 that wants to remove Wine in order to update? Can't update or remove it to reinstall without removing Wine.
This is one package with Dependency Conflict.
Since you didn't posted the error message here, I'll just give one reference to a short Debian guide on how to resolve this type of issue:
http://books.msspace.net/mirrorbooks/linuxcookbook/0596006403/linuxckbk-CHP-3-SECT-13.html
0 -
Daniel Ribeiro da Silva said:Frank Sauer said:
Has anyone else come across updates to libsdl2 that wants to remove Wine in order to update? Can't update or remove it to reinstall without removing Wine.
This is one package with Dependency Conflict.
Since you didn't posted the error message here, I'll just give one reference to a short Debian guide on how to resolve this type of issue:
http://books.msspace.net/mirrorbooks/linuxcookbook/0596006403/linuxckbk-CHP-3-SECT-13.html
There was no error message. I have the normal updates available notification. The two libsdl2 files that there are updates for notify me when I select them for update, that Wine will have to be removed to update the libsdl2 files.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Frank Sauer said:
...
There was no error message. I have the normal updates available notification. The two libsdl2 files that there are updates for notify me when I select them for update, that Wine will have to be removed to update the libsdl2 files.
Good. In this case, just hold on to the libsdl2 update for a while, someone will eventually fix the issue in the repositories and the conflict will automatically disappear (although it may take a while).
0 -
I'm dual booting Ubuntu and Windows, and I was wondering if there's any possibility of installing Logos on both Windows and Linux. I'd want it on Linux because that's the operating system I use most often, and I'd want it on Windows as well in case I ever need to do something that doesn't work on either the Linux version or the Web App (like some media).
I have successfully installed two separate versions of Logos on Linux and Windows, but since they were completely separate, they wouldn't sync any updated data or notes or anything, and they together took up more space than I would like on my hard drive (twice the normal size of the Logos folder).
I also tried installing Logos through WINE on an external hard drive (ultimately, I would have wanted it on a D drive on my computer accessible in both operating systems, but my D drive was too small at the time) and got it to work on Linux, but when I tried opening it on Windows, it said that the some documents required the latest version of Logos (following some instructions I found on this forum, the Logos installer wasn't the most up-to-date).
So now my thoughts are that the most ideal way to do it would be to have two Logos folders on a D drive available in both Linux and Windows, but to have it somehow share the same data folder (and any other folders that might be necessary, like the Documents folder). That way, I could run Logos in either Linux or Windows without having to store all my data twice for each version of Logos. I just don't know how or even if it's possible to get Logos to use an alternate path to a data folder. Does anyone have any ideas? Like some script that could redirect a ./Data query from the main Logos folder to ../LogosData/Data? Or maybe somehow replace the Data folder in both Logos installations to some other Logos Data folder that would contain the data shared by both versions of Logos? Does anyone know if this would be possible? Or does anyone have any better ideas for how to install Logos on both Linux and Windows?
0 -
I think you'd have a good chance of getting it to work by replacing the data folders in the linux installation with links to the same in the windows installation. Its documents, users and data...
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
John Goodman said:
I think you'd have a good chance of getting it to work by replacing the data folders in the linux installation with links to the same in the windows installation. Its documents, users and data...
Caution: inside some SQLite database files is the path to Resources, ... so dual booting operating systems needs identical Logos installation path.
Thread => Logos 8 Mac System Recommendations (what you'd actually want as a user) includes my 27" iMac dual boot configuration that shares my Logos (purchased library) and Verbum (demonstration account) installations (same path to application files in both operating systems).
Keep Smiling [:)]
0 -
I'm getting persistent crashes for LogosIndexer.exe for a while now... I've been thinking about updating (I'm still running Logos 8.8 in WINE 4.18 and it won't update on its own), and figure this is as good a time as any, but not quite sure how to go about it. I used Rik's method when I first installed Logos (the instructions on the Google doc page). There are also "beta instructions" for updating Logos. Is that my best bet?
[...later...]
Well, I tried just going for the full "install" rather than an "update". Figured this might be safer since things were acting broken. First time through I was asked if I wanted to delete my current folders and rebuild them. I said yes, since I have a backup of my data folders. In the end, I got an error saying Logos Setup had quit because .NET 4.7.2 wasn't found on my computer. During the install, I got a message saying that .NET 4.8 was being installed--and that it could take 30 minutes (thankfully, it didn't!)--but I didn't see anything about trying to install .NET 4.7.2... After the "Installing .NET 4.8" window, there was one about installing Corefonts. That's when it quit.
It worked second time through. Just trying to install resources (from backup) and then see if indexing will work...
0 -
Paul Unger said:
I'm getting persistent crashes for LogosIndexer.exe for a while now... I've been thinking about updating (I'm still running Logos 8.8 in WINE 4.18 and it won't update on its own), and figure this is as good a time as any, but not quite sure how to go about it. I used Rik's method when I first installed Logos (the instructions on the Google doc page). There are also "beta instructions" for updating Logos. Is that my best bet?
I would definitely recommend updating Wine, a lot of fixes have been completed that greatly enhance the Logos experience on Linux.
In relation to what's best...
Depends - if your only issue is the indexer crash, you can try the solution I posted previously for those types of issues. Clear out the index folders and library catalog folders if there are more files than a clean install. This usually works for the issue with the indexer it seems you are experiencing. There were issues with indexing in earlier versions of Wine, so that could be the needed solution for your indexer issue as well.
For updating Logos, there is a major bug that needs to be fixed right now. Updating through the application has been deleting all downloaded resources - so the work around has been to download the executable and upgrade by that means. So far no deleting of resource with that method.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Frank Sauer said:
I would definitely recommend updating Wine, a lot of fixes have been completed that greatly enhance the Logos experience on Linux.
OK. There are instructions in the Google doc for updating Wine (bottom of p. 7), but the preamble ends with a dire warning... Is there another method I should try? Recommended version?
0 -
Paul Unger said:Frank Sauer said:
I would definitely recommend updating Wine, a lot of fixes have been completed that greatly enhance the Logos experience on Linux.
OK. There are instructions in the Google doc for updating Wine (bottom of p. 7), but the preamble ends with a dire warning... Is there another method I should try? Recommended version?
Paul, I have been in contact with Daniel who is leading the bug stomping effort.... there are a few problems with newer versions of wine as well (some regressions, etc.) The main effort is to try and get 64bit Logos to work with wine since we know Faithlife will drop 32bit support sometime in the somewhat near future.
As you have noted, some updates I made to wasta-logos-setup a few months back moved from .NET 4.7.2 to .NET 4.8 which installs much faster and didn't have negative side effects. But as there are some issues with newer wine I have played it "conservative" not moving wine versions for the wasta process until we are more confident it is an improvement.
So, in summary indeed wine in wasta-logos-setup is an older version, and as you note there are occasional (even frequent) indexer challenges, but eventually it seems to work for most people.
NOTE for updating Logos itself I made some quick edits to the guide you reference. In short, you can re-run wasta-logos-setup (effectively what was recommended by others: updating "outside" of Logos itself) withOUT deleting the current wine install, and it will upgrade you to Logos 8.13. I haven't put a newer version in wasta-logos-setup yet but if you manually download a newer version and place it in your Downloads folder (named Logos-x86.msi), then run wasta-logos-setup it will use it (the one in Downloads) instead of version 8.13. So you can again always run wasta-logos-setup with a newer version of the installer in Downloads to update Logos.
Make sure you backup first if you don't want to re-download everything. However, we have noted that certain Logos upgrades required re-downloading ALL resources again regardless, so be prepared for internet use, but it should work in the end.
Once Daniel feels things have stabilized I can incorporate the newer wine version into the wasta-logos-setup process, will likely move to 64bit Logos, and will clean up the documentation as well, but again I am taking a back seat to Daniel's excellent efforts.
If you want to be more experimental with newer wine versions, etc. then check out Daniel's "AppImage" approach. It may use lower CPU, etc., and if you have the time he may appreciate further testing. The most responsive way to get feedback is through the Telegram channel: https://t.me/linux_logos
Good Luck, keep us posted!
Rik
0 -
Frank Sauer said:
Updating through the application has been deleting all downloaded resources - so the work around has been to download the executable and upgrade by that means.
Frank:
Could you share the link in the forums or how download executable and upgrade.
Thanks Al
Frank Sauer said:Updating through the application has been deleting all downloaded resources - so the work around has been to download the executable and upgrade by that means.
0 -
Rik Shaw said:
So, in summary indeed wine in wasta-logos-setup is an older version, and as you note there are occasional (even frequent) indexer challenges, but eventually it seems to work for most people.
...
Once Daniel feels things have stabilized I can incorporate the newer wine version into the wasta-logos-setup process, will likely move to 64bit Logos, and will clean up the documentation as well, but again I am taking a back seat to Daniel's excellent efforts.
Thanks for the update, Rik. I was just composing a message about having been at this Linux thing for a while, and being really pleased when it works, but once again finding myself up against the wall of "not-really-knowing-what-I'm-doing-but-only-having-instructions-that-assume-I-do"... I was at the point of having a look at Daniel's "script", just so see if I could make that work for me, but got hung up on step 00:
00- Download and execute:
You can download the last release [HERE].
Well, I didn't find anything obvious HERE, but there are four "Assets" at the bottom of the page. I had no idea what to download, but after looking at some of the command line stuff I figured it was "install_AppImageWine_and_Logos.sh". I still had no idea what to do with it...
So it's good to know that a more stable update is in the works. I will continue on with Wine 4.18 and wait for an update to 64bit. And if you're cleaning up the documentation, could you /please/ assume that some of us are starting from "itch" (i.e., one step before starting from "scratch")? E.g., "Download *this* file to *this* directory. Open a terminal and *change directory* (if required) and run *this* command," etc. Your help is enormously appreciated!
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.
0 -
My indexing stopped working on Ubuntu 18.04.
I had a working version of Logos, but it recently began crashing more often. I though perhaps an update would fix it, so I followed the instructions in the Google Doc regarding the update with the newest installer in my Downloads folder. After a successful update, the indexing program failed, so I tried deleting the contents of the BibleIndex, etc. folders as has been discussed here. That did not fix the indexing.
I then reinstalled Logos without any .msi file in my Downloads folder,hoping to restore the previous setup. The indexer still crashes. I deleted the BibleIndex, etc. folders again after this installation, but indexing still crashes.
I then tried winetricks arch=32 -q dotnet472 corefonts ddr=gdi fontsmooth=rgb win7, plus winecfg and changing the default setting to XP. Still no luck.
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
