Linux version of Logos Bible Software
Comments
-
It is also worth looking at https://appdb.winehq.org/objectManager.php?sClass=version&iId=39484
We keep the appdb fairly up to date with info, tests and bugs. We've rated Logos Silver for a long time. What works, is very stable but some things don't work. E.g. video and audio playback in the app. These are things you can easily pick up with the web app. For that reason, I feel you can have a very complete Logos experience on Linux but we still have work to do.
Much of the remaining work has to do with speech, media codecs and quite complicated dependencies. Developers from codeweavers and steam are working on these areas so we expect to get there eventually.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
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! ;-)
0 -
If the updates you downloaded were the datasets that Rick posted about an update being released - you'll have to update to Logos 9.13 and be inconvenienced by the Menu bug until we are able to figure out what is causing the crashing. Log files point to the Pericope Dataset that was updated. But your layouts will open with 9.13
https://downloads.logoscdn.com/LBS9/Installer/9.13.0.0018/Logos-x64.msi
Paul Unger said: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! ;-)
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
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.
0 -
Hey Paul,
You wouldn't have the Menu bug if you are running Logos 9.9 or lower. To bypass the crash on opening a layout or resource, it appears we need to update to a Logos version with the Menu Bug. I was only able to open resources like audio books or videos. Any other resource seemed to crash Logos.
I'd backup my Data, Documents and Users directory and give the 9.13 a look. Once that installs copy over your backup folders to avoid redownloading and reindexing everything.
Paul Unger said: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.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
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.
0 -
I tried following the fast-script w/ AppImage. Same: I can open a Greek lexicon, but other bibles crash, whether BHS or ESV or CSB, etc.
I included the txt of terminal dump? I'm on new Pop_OS 22.04 (Pangolin 11 - AMD)
0 -
"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."0 -
I tried this with wine-devel 7.8 (jammy - I'm on Pop_OS! 22.04) and it says I need LogosInstaller.exe for NET 4.7.2, so I am not able to complete step 6. Would installing Mono do the trick or is that something we don't want to install?
0 -
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. :-|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!
0 -
Well, I think my install is knackered... :-( Restart and indexing didn't do anything -- it's still crashing; and I don't know what else to try. It sure was nice when it just worked. :-P
I'd be game to start from scratch, but the thought of downloading everything again gives me chills. I know people say you can save your existing downloaded resources (I still have /home/*username*/LogosBible_Linux_P_old/data/wine64_bottle/drive_c/users/*username*/Local Settings/Application Data/Logos/Data/zwgbtstt.hmi/ResourceManager/Resources), but copying them has never worked for me... Fool-proof instructions appreciated! ;-)
0 -
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!
0 -
Funny, I was able to open BDAG as well -- before I tried to upgrade. I had it as a 'favourite' icon in the top bar, and I clicked it and the Atlas icon I have up there and they both opened (I was also able to open the Atlas from the Tools menu, as I mentioned earlier).
You're doing a new install, right? Not upgrading?
Bummer about Logos no longer running on your X1... If it's just a paperweight (albeit a light one!), you could toss it my way! Joke!!! :-P
0 -
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...
0 -
For those who are experiencing Logos crashing on open of resources or when Logos attempt to load a layout - we are trying to pinpoint the issue.
This bug appeared after the dataset updates a few days ago - one of the logos crash logs seems to point towards the Pericope Dataset.
Thus far, I have been able to get Logos to open with the updated Datasets by running the latest Logos 9.13 (The latest 9.14 Beta also works).The trade off is we now have to deal with the bug that popped up with the CEF update - it's a slight annoyance of having to double click Menu Headers to access the Menus.
I personally do not use the ferion script - but the recommendation at this time is this:
Logos 9.13
LogosIndexer.exe set to Vista in winecfg (Indexer will not function correctly if not)
Run install and application updates with the prefix default set to Win 10
Once the install is complete - change the prefix default to Win 7 (This allows printing to function and the app load time seems to improve - Win 7 also allows resources to update while not recognizing Program update - which is a positive to avoid installing new Logos versions that haven't been tested for new bugs or regressions)
In Logos Program Settings - turn off automatic updates
***Side Notes
Double Check what renderer is set in Wine (gdi has been the most consistent)
Double check that dotnet48 is installed
Always keep a clean and up to date back up of your Data, Documents and Users directories due to the bug that wipes data on Program Updates.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
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...
0 -
Wine-Stable 7.0 would be a good start.
To find logosindexer.exe - you need to navigate to the logos directory in your Wine install - LogosIndexer.exe is located in the System Directory of the Logos install folder
Paul Unger said: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...
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
In relation to the bug that Passage Analysis crashes Logos - here is the LogosCrash Log
Error ID: 8546
Error detail: COMException: Exception from HRESULT: 0x88980406System.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)Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
If you didn't open Logos yet after install, LogosIndexer.exe might be in a folder named Pending
0 -
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
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Yes, I realized that. Sorry! I was going to delete the comment but I wasn't sure how to. On another note, I tried installing Logos 9.13 and manually setting everything per your instructions. For some reason I can't find wine 7.0, so I had to use wine-devel=7.8~jammy-1 for my Pop_OS (Ubuntu) 22.04. I couldn't even get the LogosSetup.exe to work, so I had to follow WineHQ instructions to manually add Microsoft dotNet 4.0 (in XP) then dotNet 4.7.2/4.8. Eventually I got it installed, then I switched the indexer to Vista. I even used (per WineHQ instructions) the Library exception to use mscoree -> native rather than built-in. However, after doing all the initial work, when I tried starting up the actual Logos.exe, it couldn't on account of the mscoree.dll not being found! Terminal output/wine debug: 1362.logosManualDump.txt
Looks like I'm going to have to try ferion11 script one more time w/ Logos 9.13 MSI, though last time it didn't work. Thank you all for your tireless work! I'll probably make do with the web app for now.
0 -
Just an update: The Ferion Script (v.2.39) has Logos9.13. I did do a Custom install -> deselected automatic updates just in case. And did a Quick install instead of download everything. I am happy to say Logos Desktop app is working again! So Paul, it may be time for a full reinstall.
It finally worked for me!0 -
Likely spam?
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Written by a spam ai?
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Question: is there a way to use different versions of Wine for different programs?
A few weeks ago Logos stopped working for me, and the advice here (after a failed attempt to do an 'update') was to do a complete install using Wine 7. I also use PDFXChange Editor in Wine. I have only gotten it to work using PlayonLinux; settings show that it uses the 'system' version of Wine, which is 5.0-3ubuntu1 (per Synaptic Package Manager). Synaptic isn't showing an update available for my 'system' version of Wine, so it seems I'll have to download and install it from the Wine site. But I'd hate to mess up PDFXChange Editor, which is working fine. Can someone offer me some advice / instructions on a way forward? I'd sure appreciate it!
0 -
Paul and others,
If you are on Ubuntu 20.04 / Wasta-Linux 20.04 I would suggest staying with the "Wasta-Logos" method, it keeps its version of wine isolated by using "Wasta-Wine" and, in my opinion (as the creator of Wasta-Linux and the Wasta-Logos-Setup method so YMMV [:D]) is a very good "stable" way to use Logos in Linux, especially if you are not an "enthusiast" willing and eager to tinker and debug more cutting-edge versions of Logos or Wine. I don't release new Logos or Wasta-Wine versions until they are confirmed to not introduce regressions. Currently this means Logos version 9.9.x and Wine version 7.0.x
Wasta-Wine will not touch your existing Wine / PlayonLinux / etc. configurations or installs. Also the Wasta-Logos method will install your Logos configuration, resources, etc. to ~/.logos-data so that any re-installs, etc. will not lose your downloaded resources.
Here again is the guide for using Wasta-Logos-Setup (again only for Ubuntu-based LTS and derivatives such as Linux Mint, ZorinOS, elementaryOS, Pop!_OS, etc.)
The "script / AppImage" method is also a good way to go, but as you are noting there are sometimes that updates / etc. may introduce some regressions.
0 -
Just in case people don't like digging for links, the "script /AppImage" route is https://github.com/ferion11/LogosLinuxInstaller
The most recent version works! And it isolates one wine "bottle" to just Linux and does not use a new wine version if you choose to use the prepackaged 6.5 App Image. It won't touch your other wine apps nor will it require you install wine beforehand.
0 -
Thanks Rik, I'll give that a try. Stable sounds nice.
Q: I have a folder of resources in /home/username/LogosBible_Linux_P_old/data/wine64_bottle/drive_c/users/username/Local Settings/Application Data/Logos/Data/random_string/ResourceManager/Resources. Can they be copied to /.logos-data? If so, at what level of the folder tree should I copy them over? And at what point in the installation process should I do it?
Oh, and it looks like the link to the "Wasta-Logos-Setup" method you tried to point to didn't come through. It's:
https://docs.google.com/document/d/1EiFjlONDHKmvJNJPSfcCk2MBVe_0bxKXPslXbC831Gc
0 -
Currently indexing.[Y] And my other wine program still works. Many thanks!
For the record, I copied the individual files from /LogosBible_Linux_P_old/.../Data/random_string/ResourceManager/Resources to /.logos-data/Data/random_string/ResourceManager/Resources after Logos installed and before I clicked OK on the window inviting me to download all the resources. Books are opening, so it seems to have worked.
0
