Linux version of Logos Bible Software

Sorry, Michael,

To be more accurate, and to the point, Taylor thought this problem was solved with Wine 9.12+. Don’t know which version of CrossOver it would be ?

God bless.

Yvan

Or Debian which they are both derived from from and which the vast majority of distros are derived from. If you just target Mint or Ubuntu you may get stuck with Canonical specific packages that Debian, and others, do not use so you are limiting the audience. The real issue is though that recoding Logos so it can work on Linux natively would be extremely difficult.

You're not far off. They could use Flatpak (I do not like snap at all) which would allow dependencies to be contained, and updates as Logos needs them. It would also standardize the distribution, and not require a specific virtualization platform (i.e. KVM, Virtualbox, XEN, etc. etc.) some of which can be daunting to a regular user. Most all the "technical" hindrances can be overcome, I've told people this for years, as that's one of the things that makes Linux desktops so great, we're not limited in options.

but, I've noted the "Layouts" option won't open after a couple of menu opens, no matter how much you double click.

We like to call that "The Menu Bug" expand and/or collapse the left navbar to click again. We don't know why that happens.

Also, How do you get winetricks to install a browser or something into that image?

The wineprefix is located in ~/LogosBible10/data/wine64_bottle.

If you happened to have a firefox windows installer downloaded (shown below as ~/Downloads/FirefoxInstaller.exe), you could do something like:

export WINEPREFIX=~/LogosBible10/data/wine64_bottle/
~/LogosBible10/data/bin/wine64 msiexec /i ~/Downloads/FirefoxInstaller.exe 

(Sorry about some spelling issues, after spinal surgery using my left hand can be a challenge).

I didn't notice, hope you're recovering well!

The problem I'm running into is that they all fail.. They act like (Logos as well) at times like they can't access the internet. I'm having to manually download new books, which it will do, but auto download, etc. keep turning themselves off.

Firefox and brave browsers both crash and burn.

Logos on Kubuntu 24.10 using the ou dedetai install works great for the most part, I just have to manually do the Logos updates, and downloads of new books. I've found the filters in the Library that should tell me if I'm missing any, so no worries there.

I did experience some fall overs early on, but this latest installer and versions of Logos otherwise run well enough that I felt comfy removing windows altogether. So, I share Frank Sauer's sentiment on this being Well Done!
I'm happy I can run it on Linux along with the Web versions and Bible research and Study is much easier and portable.
So, Thank You for the installer!!

Oh, and Nathan Shaaban the collapse menu and reopen trick works, thanks for that tip as well. The command line for opening winetricks works with some caveat:

export WINEPREFIX=~/LogosBible10/data/wine64_bottle/
~/LogosBible10/data/bin/wine64 winetricks

had to be changed to my actual home directory path instead of the "~/", for that to work. And, firefox complains about missing CRYPTO and some other library (which is why it's installer crashes), and Brave just says it can't access the internet and dies. But, we'll live. :D

I did run into the issue that my Library will not download and the program crashes each time I try to download.

What installer version are you using? We recently fixed a bug like that. Try the latest version if you aren't already. You don't need to reinstall, just update the installer then launch again.

There is a little ">" symbol in the lower left part of the logos screen. Clicking there will expand or collapse the menu. Doing so will overcome the "Menu Bug", for the moment, allowing you to do what you need to do.

The blue hand-drawn arrow points to it on this screenshot:

Hey Nathan,

I was using V4 Beta 8 - I downloaded Beta 7 and it seems to be working. Beta 8 installed quite quickly in comparison, so I wonder if it was incomplete, where Beta took longer to install.

AppImage is the way to go.

Flatpak. They can go open source if they need more eyes to look at it. Maybe keep the access of the resources proprietary, but open source the rest so we can make it work on Linux.

With the state of the world, forcing us to use the two operating systems which can basically spy on your everything you see and hear with AI is not good.

@Al Graham, most likely the file didn't download correctly. Trying clearing the .cache/FaithLife-Community of the offending file and try again.

Wine Staging was suddenly broken and would not update on my system. I uninstalled Wine Staging. Should I just reinstall it, or would it be better to also uninstall Logos also and re-install using the new install script?

Thanks. I just installed Wine stable, opened Logos, and everything worked.

I was able to install Logos 10 in Manjaro (Arch-based) Linux.

The oudedetai install script was designed for Ubuntu. When I tried to use it to install in Mint (Ubuntu version) it failed repeatedly, and also failed in Mint (Debian version), nor would it complete installation in Manjaro or another Arch Linux version I tried it in.

So I'm typing the instructions out as simple as possible for those new to Linux, and using Manjaro (this might work in other versions of Linux also):

1. I installed Ubuntu, then installed Logos 10 in Ubuntu using oudedetai. Get it here (https://github.com/FaithLife-Community/OuDedetai) and follow instructions on that page to install it. More detailed instructions are here (https://github.com/FaithLife-Community/OuDedetai/wiki/Install-Guide). It worked perfectly at the first attempt to install it in Ubuntu. Complete the installation of Logos, but do not run it yet if you have saved Logos data files to transfer into it. This will avoid the time and cost of downloading the data files from Logos.

2. I pasted my saved data files into LogosBible10 (in the Home directory of Ubuntu), and checked that everything was working right (be sure you paste the data files into the correct location inside the LogosBible10 folder tree. Here is the usual location to look: /LogosBible10/data/wine64_bottle/drive_c/users/your-user-name/ AppData/Local/Logos/).

If you don't have saved data files, you will have to download all your data from Logos after you install the program.

3. Then I copied the entire LogosBible10 directory into the Home folder of Manjaro.

4. Then I found the Manjaro Wine Dependencies for Logos at this link, https://github.com/FaithLife-Community/OuDedetai/wiki/System-Dependencies (Copy the dependencies for your version of Linux)

5. Open a command box (Terminal) in Linux. In Manjaro you would type: sudo pamac install (then paste the names of the dependencies here). Press "enter" If you receive the message that pamac is not found, then use pacman instead: sudo pacman -Syu names-of-dependencies-here (In Ubuntu or Wine you would type: sudo apt install names-of-dependencies)

6. Then to install WINE (If using wine from the manjaro repository) run: sudo pamac install wine

7. Then run: cd ~/LogosBible10

8. Then run: ./oudedetai (If the oudedetai script is not in the LogosBible10 directory, then copy and paste it in from wherever you have previously downloaded it to.)

9. Now when the oudedetai install program runs, it should no longer say "Install Logos 10" but "Run Logos 10" Before you run it, click on "Run Indexing" or "Update Index" If it seems to run forever, you might have to close oudedetai and restart it, then click "Run Logos10"

10. If all goes well, it will work in your version of Linux, AND it will install a Logos start link in your application menus, probably under "Education." If Logos does not start, try installing components from the oudedetai script, and run wincfg, setting the Windows version to Win10. You may also have to run a system update and upgrade in the Terminal.

May God bless your efforts to run Logos10 in Linux!

I am using Pop_OS (Ubuntu-ish) and as of RC9 I have Logos running! I initially had a failure to launch after I changed some settings, but I deleted my index files and performed the ICU operation and it started again successfully. It did not work on RC7, I could never get past the initialization wizard.

I have an IT/Cyber background and would be happy to do what I can to support the project. I'm invested in having my Logos tools work on Linux if at all possible. Right now I am on Windows for reliability with Logos but I hope to have a Linux-only future and finally shed MS altogether (and there's no way I want to be in the Mac ecosystem, or pay Mac money).

It would be a huge blessing if FL would support Linux, especially as we look to a future where persecution may force believers toward less "centralized" or "connected" big tech options. We're seeing the seeds of it in the West.

Maybe we'll hit Bob's 8% number soon. Up over 1% in one year.

https://www.tomshardware.com/software/linux/linux-market-share-approaching-45-for-first-time-could-hit-5-by-1q25

Well, not as dead as I thought. I was able to go back to v8 and get it re-installed. But, hopefully it's a small fix in v9. :D

I tried to edit the previous post as I meant to include this there, but when I do I get "Page Not Found". must be a part of the changes they're putting in. Also seems like Faith Life is actively blocking Linux as you can't even download logos for Windows if you're browser user agent doesn't report Windows. Seems a little petty to me. :D

Videos don't seem to work at all on my Linux install. Is this a known issue or is there something I should do? It's not the end of the world, but it would be nice if they worked!

Thank you all who have been putting in (I'm sure) long hours to get Logos running on Linux. I just installed on Linux Mint 22.1 desktop computer and it's downloading/indexing my library as I type. This removes the final barrier to getting rid of Windows from my laptop.

A good place to start is here:

https://github.com/FaithLife-Community/OuDedetai/wiki/Install-Guide

This is slightly outdated but most of what it has holds true. The most of what has changed is we have implemented a default and advanced installer. The wiki page there has steps for what is now the advanced install. If you choose the default install, it is even more simplified.