Linux version of Logos Bible Software

As a pastor of a cash strapped church, and as someone who invests in this tool. I think it is a great idea to get logos to work on linux and then start a ministry of refurbishing older computers installing this on them to send to impoverished areas with our country and around the world. But that is just me. I understand the costs and all and that is why i still have one windows computer. I just think it would be nice to be able to provide lower income ministries access to great tools without having to pay as much for it. 

As a pastor of a cash strapped church, and as someone who invests in this tool. I think it is a great idea to get logos to work on linux and then start a ministry of refurbishing older computers installing this on them to send to impoverished areas with our country and around the world. But that is just me. I understand the costs and all and that is why i still have one windows computer. I just think it would be nice to be able to provide lower income ministries access to great tools without having to pay as much for it. 

After this long, I'm not so concerned about Faithlife targeting Linux... They have been supportive of the effort e.g. supplying information, allowing binary distribution, commenting on wine bugs etc. We already have the windows version running very smoothly on Linux. I use it nearly every day. Video, audio and speech will follow soon but since they work in the webapp it is no real problem. Folks must not forget that the webapp is a response to the need to support more niche platforms, Linux and ChromeOS. In short, Faithlife has not ignored Linux users.

Looking forward, at some point (v10?) Logos will be built on .NET 6 and it will be easier both for wine but also for a native port. I would hope that because of .NET 6 FL might reconsider the cost / benefit of a fully native build again as it might not be nearly as difficult as it has been up to now.

We are already testing Box64, which will most likely see near native speeds for ARM (currently there are missing instructions and it crashes). This is similar to how Rosetta2 works on m1 macs. It somewhat cleverly swaps out libraries for native ones etc. So even Logos for raspberry pi is looking likely.

Thinking about Stephen's point about the safety of our investments in Logos, this Linux work is already really important to believers in certain regions and I think concern over how secure Logos is for the future is a relevant topic. I know that Bob has written about this in the past so I'm grateful it is considered. I personally miss the 'send to kindle' feature which felt like a helpful backup, a safety net. I bought an onyx boox instead of my kindle which at least gives me the eInk reading experience but the books are still only in Logos and I'm relying on Logos to work.

MJ. Smith said:

As a retiree from IT, I don't want FL wasting it's time porting to Linux or building interfaces to external products. Linux has it's place but it is not as a competitor in the general user market. Interfaces have their place but they come with a high maintenance cost unless done solely via standardized formatting. As FL does not borrow money, I want them to concentrate their energies on meeting the needs of their core market -- and spending any surplus on supporting the churches in diaspora after being exiled from their Middle Eastern homes. I post this only to show that there are multiple opinions that FL has to take into consideration.

What is FL? Oh FAith life LOL  I have downloaded Zorin OS 16 since it is super easy to parallel install next to windows.  I'm hoping we don't have a crash of all things microsoft, but if we do, I'd like to still be able to use my full version of Logos.  

I don't understand the WINE thing and how to program it?  I think most people are like me, and want a "plug and play" version.  

Thanks for all the input into this thread!  I saw where someone said to install a windows emulator, but that sounds like it defeats the purpose here.  There's got to be someone that can have a linux version, ready to go in case windows (owned by the most evil man on the planet) goes bye bye.  Just saying, we have a lot of new light on this old topic.

Michael Lindner said:

I am loath to support companies like MS that publicly and adamantly attack Christian morality and life. Yes, it's almost impossible not to these days, but it can't happen without alternatives.

FL, of course, is a business and must support its users and make money for its employees, but they have been great in helping people get going with WINE and I, for one, would welcome a Linux native version, if only to have one less reason to need Apple or MS products.

If Microsoft crashes, lets say in a cyber attack from Russia (wild guess here), then any company depending on that software to make money, will have NO BOTTOM LINE at all.  So maybe the wise thing is to have a native linux version as a backup for it.  AGAIN, I'm totally guessing here.  Absolutely nothing will probably crash at all.

It’s worth looking at and understanding wine. Wine works very well, there are bugs but that is true on any system. When Logos is built with .NET 6 I think we will have a giant step forward. (Probably a brief step back first) We may even get a good result on arm too!

Yes it works with Zorin

You can install the latest version, I think the script defaults to an older version because of a bug which was introduced afterwards. The choice is use an older version or double click menus instead of single click. Obviously we hope to get the menus back to a single click but the change was on the Logos side which means wine needs to catch up. Because it isn't technically a 'regression' wine will take a little while to get round to addressing the issue. Alternatively you can turn off local window manager decorations etc in wine config and you'll get back the correct function I believe.

Yes, just change the version number at the top of the script. It only appears once.

If you can replicate the crash then please post it as a bug on winehq together with the terminal log. The backtrace is less likely to be helpful. Then share a link to your bug and we'll try to get it sorted.

For the terminal log: launch logos in a terminal not with a shortcut. E.g. Logos.sh or wine64 /path/to/logos.exe

Then in your terminal app e.g. konsole, save the terminal output to a text file and include attach it to the bug report. Don't cut and paste as the dev's like to keep messages separate from logs.

thanks

Thanks, I've connected that on wine appdb and we'll do our best to figure it out.

Seems to be a lot of errors in that log... Makes me wonder if dotnet48 installed correctly. I'd probably start there myself. But I'm also viewing it on my phone screen...

Gabriel, welcome to the Faithlife forums.

Here is the link to the developer’s GitHub site that uses an app image to install Logos using wine: https://github.com/ferion11/LogosLinuxInstaller 

We don’t know your proficiency in working with Linux, so you’ll need to reach out here if you need help..

Bill Anderson said:

Gabriel, welcome to the Faithlife forums.

Here is the link to the developer’s GitHub site that uses an app image to install Logos using wine: https://github.com/ferion11/LogosLinuxInstaller 

We don’t know your proficiency in working with Linux, so you’ll need to reach out here if you need help..

Thanks very much for this link! I am also about to start the process of getting as far from windows as possible, I refuse to use windows 11. I work in IT and long ago, maybe 10 years now, I imaged a bunch of Linux machines but at this point I am a complete Linux newb. I use Logos 9 a great deal and love it, that's the only reason I would consider keeping a win10 machine around.

I'm considering the Arch distro but still researching Linux and hardware as I need to build a new machine. Depending on the hardware needed for Linux, I may build a 2nd machine or rebuild my laptop for logos. So glad to see Logos on Linux is possible, I don't want to leave logos, but if my only option was to run it on windows 11, I think I would.

I've been using the 'ferion scrip' version for a while, without serious trouble. Today Logos downloaded 85 MB of 'updates' and now it will start, but if I try to open a resource, Logos just disappears -- no crash report window, nothing... I'm running Logos 9.5.0.0019. Advice appreciated! ;-)

Thanks, Frank. How would I find out if I downloaded the troublesome datasets? I do *not* have to double-click to open menus, and I can open things like Tools > Atlas and Notes. But as soon as I try to open a resource -- crashola...

I ran ./Logos.sh indexing; I see a bunch of things like:

0024:fixme:path:parse_url failed to parse L"System.Windows.Forms"
0024:fixme:path:parse_url failed to parse L"System.Security"
0024:fixme:path:parse_url failed to parse L"System.Xml"

but the final two lines say:

00a8:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003
======= indexing of LogosBible run done! =======

After doing this, the problem remains... I have the full terminal output from my attempt at indexing, if that would be of any help.

I, too, have this bug. It causes Logos to crash right after the startup sound and before it loads anything. I had 9.09 I think. I guess it's time to upgrade to a newer version with the menu bug.

"Following installation please ensure the LogosIndexer.exe is set to 'vista' and Logos.exe is set to 'win7' for best performance."

I tried unsuccessfully to do the fast-install ferion11 script. Through ./controlPanel.sh winetricks, I can set something to win7 or vista, but how do I individually set an .exe to one or the other? Thanks!

Is it through the manual process, something like #7?

"https://downloads.logoscdn.com/LBS9/Installer/9.6.0.0024/Logos-x64.msi

Manual Install Procedure:
1 Install wine 6 or newer
2 winetricks corefonts
3 winetricks settings fontsmooth=rgb
4 winetricks dotnet48
5 winetricks settings renderer=gdi (you might need to set the reg key manually)
6 Install the Logos.msi download but don't run it.
7 wine64 reg add "HKCU\\Software\\Wine\\AppDefaults\\LogosIndexer.exe" /v Version /t REG_SZ /d vista /f
8 Run Logos and sign in with your free account."

Dean Chia said:

"Following installation please ensure the LogosIndexer.exe is set to 'vista' and Logos.exe is set to 'win7' for best performance."

I tried unsuccessfully to do the fast-install ferion11 script. Through ./controlPanel.sh winetricks, I can set something to win7 or vista, but how do I individually set an .exe to one or the other? Thanks!

I'm trying to work through the update process myself, Dean Chia (following the instructions here: https://github.com/ferion11/logoslinuxinstaller#25--to-update). Not going so well... In the terminal I had to "cd LogosBible_Linux_P" and then "./Logos.sh winetricks". When Winetricks opened, I selected "Run winecfg" then clicked OK. A Windows-y "Wine configuration" window opens, and on the Applications tab you can set LogosIndexer.exe to Windows 7; mine was on Windows Vista. Despite changing this, I'm still crashing after the "Preparing your library' popup appears. I'm going to try a restart and see if that helps. :-|

I'm really at a loss. I have been trying for two days to install this on my new System76 Pangolin11 (AMD) Pop!_OS 22.04.

I have tried using the newly updated ferion11 script today for Logos 9.11. Interestingly, I can consistently open up BDAG after downloading it. I believe I can also preview other Bibles that I have not previously downloaded and view the preview. Once I download it, then opening any Bible results in an immediate crash. I have attached the crash output as a txt: 8535.logosDump.txt

I have tried Hebrew and English Bibles and NA28. No good. Immediate crash. I bought my new computer specifically to run Linux faster (+ bigger screen and supporting System76).

I decided to try and look at what version I installed Logos on my older ThinkPad X1 Carbon Gen 3 (Intel) Pop!_OS 22.04. But now I don't know why, but now Logos doesn't work on the old laptop either!

Yes complete new install. No copying pasting any old data. Clean install from scratch. No bandwidth saving. :P I am trying Debian Stable and seeing if there's any luck with the ferion11 script...

Thanks for that, Frank. I used ./Logos.sh winetricks to set LogosIndexer.exe to Vista (just winecfg opened a config window, but there was no LogosIndexer.exe in Applications, just Default Settings [set to Windows 7]), ran ./Logos.sh indexing ("indexing of LogosBible run done!"), and finally ran ./Logos.sh, but it crashed at the "Preparing..." screen.

Here's a question: what version of Wine should I be running? At the end of the crash log, I see System Information, Wine build: wine-5.0 (Ubuntu 5.0-3ubuntu1). Is that correct? I sure hope so, because every time I work with wine and bottles and vintages, it's like I have to learn it all over again...

In relation to the bug that Passage Analysis crashes Logos - here is the LogosCrash Log

Error ID: 8546
Error detail: COMException: Exception from HRESULT: 0x88980406

System.Runtime.InteropServices.COMException (0x88980406): Exception from HRESULT: 0x88980406
at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam)
at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.UnsafeSendMessage(IntPtr hWnd, WindowMessage msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Window.InternalClose(Boolean shutdown, Boolean ignoreCancel)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at LDLS4.OurApp.InitializeAndRun(ReadOnlyCollection`1 listArgs, SingleInstanceManager sim, Scope telemetryStep)
at LDLS4.OurApp.Main(String[] astrArgs)

Pending is a temporary folder

Dean Chia said:

If you didn't open Logos yet after install, LogosIndexer.exe might be in a folder named Pending