Linux version of Logos Bible Software
Comments
-
John Goodman said:
If you have crashes it would be really helpful for you to save the terminal output into a txt file and post it to us on the telegram group. https://t.me/linux_logos
I'm not sure how I would do that, John. I don't think the terminal runs when I start Logos (I just use the desktop icon that was installed), so I'm not sure what I would copy? Are there logs kept somewhere? I could send those, if they exist / would be helpful.
As for the "telegram group", I clicked the link you provided, but have no idea what to do with what I see: a "View in Telegram" button below "RL | Running Logos Bible Software on Linux | 110 members, 7 online" (which does nothing when I click it), and a "Download" button (which I'm not in a big hurry to click, again, not knowing what it will do). :-\ Sorry.
0 -
Telegram is a program that can be installed to your system. You can also join us on Matrix, another chat program: https://matrix.to/#/#logosbible:matrix.org The Telegram and Matrix channels are bridged.
The Ferion11 script is up-to-date and basic install instructions are on the script's README.
https://github.com/ferion11/LogosLinuxInstaller
There are some incoming bug fixes for the script as well. You can keep your eyes on the releases page for when a new version is released:
0 -
Logos10 has been running OK since I got it installed -- pretty glitchy graphically, but otherwise OK.
Today I was informed of 469 MB of updates waiting to install. I clicked OK and it installed and indexed. When I came back to my machine it said there was another 11.9 GB of program updates to install! :-0 Again, I clicked OK and left. I came back after not too long to do something else and found that Logos was done and wanted to be restarted. I was surprised it went so quickly, but I went ahead and clicked "Restart". And it never did... It shut down, but never came back -- and still hasn't, despite logging out of the desktop, restarting my machine, and trying to start Logos about ten times. I get the splash screen and "Preparing your library", but watching System Monitor > Processes, those both end withing about ten second...
Any suggestions?
[For what it's worth, I still have Logos 9 installed, and it starts up and runs fine.]
0 -
Suggestion 1: join us on https://t.me/linux_logos for faster responses.
Suggestion 2: My guess is the library catalogue is corrupted. Run the script with ./Logos.sh
--remove-library-catalogIt takes a few minutes to regenerate the catalog the next time you run it with ./Logos.sh
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Re Suggestion 2: do I have to navigate to a certain folder to run the script? I've tried it in a few (e.g., root and /Logos10), and all I get is:
bash: ./Logos.sh: No such file or directory
[later...] Interestingly, when I look in /LogosBible_Linux_P (my Logos 9 install), there are two files (controlPanel.sh and Logos.sh) and a folder (/data). In /Logos10 there is only the folder /data. Looks like my Logos10 install got borked with the update?
0 -
The script created a LogosBible10 folder in your home dir. Name might be slightly different (going from memory). The terminal will only launch a script if it is in the current dir or path variable which is an important security feature of the system. The ./ tells it to look in the present dir.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Hi John,
As you can see farther up on this page, I used the manual install method after repeated fails following the normal route... So the folder in my home dir is /Logos10. Which is empty but for the /data folder ("View hidden files" is turned on).
Looks like I'm in for another trip through the install procedure... :-( Unless there's a way to restore 'disappeared' files like Logos.sh and controlPanel.sh? Given the graphical glitchiness I had with Logos 10, I may just stick with 9. It's working, and stable, and doesn't flicker.
Edit: I should mention that I appreciate the explanation / tip about terminal, launching scripts, and ./ . It's one of my biggest griefs with Linux -- "run this script", but *where*?!
0 -
Sorry missed that point. You can make do without the scripts but they are very good and useful. If you run the script command as mentioned it does this: rm -fv "\${LOGOS_DIR}"/Data/*/LibraryCatalog/*
You can do it manually. Hope that helps.גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
OK I've read back through the thread... apologies for missing the context. It looks like you've had a difficult time. If you wanted to give telegram a go we can share screen with it and I'm happy to have a call and help you in real time. I'm sure we can get your system working.
I have a theory about what went wrong...
When you tried the script there was an unfortunate bug which we fixed. You then tried the updated version but I think at that stage you might have had a partial download which could have prevented it working properly because it doesn't verify downloads. (we might try to build that feature).
So what can work?
I would try clearing any downloads from your ~/Downloads folder. E.g. LogosInstaller msi. Wine app image etc. Previous versions of the script.
Then I recommend to try again with the script and choose the appImage install options.
If I can help further let me know.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Just to clarify -- I did have Logos 10 running. I did have a difficult time with it, but it did work, for about a month. An update a few days ago killed it...
I tried removing the LibraryCatalog folder and running Logos 10 again. It loaded the Home screen, and there were (3) operations underway: Library cataloguing, Indexing 0%, and a notice about resources that had been installed! And then it crashed... I tried many times to restart it, but never succeeded.
I then went for a reinstall. I cleared the files you mentioned from the Downloads folder, grabbed the latest LogosLinuxInstaller.sh and ran it. At the Wine step, I chose the third option -- the one that didn't start with "custom". There were a few times I had to interact with the terminal, but it seemed to progress as expected. At the end I got the message:
A launch script has been placed in /home/paul/LogosBible10 for your use. The script's name is Logos.sh.\n\nDo you want to run it now?\n\nNOTE: There may be an error on first execution. You can close the error dialog. [Y/n]: y
I went with 'y' -- and that was it... Nothing... I tried clicking all around the screen, as on the last time the Logos 10 install /did/ work for me the 'login' screen never generated graphically and I only discovered it by accident when I clicked where it should have appeared (see a previous post). I've tried running ./Logos.sh from the LogosBible10 folder (yes, it is in there!), but nothing happens.
I don't know if you can help me without Telegram. I'm not interested in running social media messaging programs; just not somewhere I want to go... Sorry.
0 -
We could do a zoom call? I'm contactable via: https://faithlife.com/jg00dman
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
is this still an issue App Image install no longer working#178 from ferion11 / LogosLinuxInstaller
0 -
John Goodman worked with me to try to get Logos 10 installed, but we never succeeded... (after finding "#178" it looks like I'm the one he refers to there). He said he needed to do a bit of digging to find where it was failing for me. I haven't tried since using the script since, as I haven't seen an update to the script. I know this is all volunteer work, so this is not a criticism--just giving you my take on your question.Al Graham said:is this still an issue App Image install no longer working #178 from ferion11 / LogosLinuxInstaller
0 -
Al Graham said:
is this still an issue App Image install no longer working #178 from ferion11 / LogosLinuxInstaller
You can still use the script to install Logos using a previous Wine staging installation. I have done this successfully as recently as this past weekend.
0 -
Would you have any instructions as to how to go about that?Bill Anderson said:You can still use the script to install Logos using a previous Wine staging installation. I have done this successfully as recently as this past weekend.
0 -
Yes, please see the attached document that I drew up for another Logos user this past weekend.
Please note: This was a list of steps for installing Wine staging and Logos within a Debian Bullseye container on a Chromebook. Some steps will not apply.
0 -
Hi, first of all, thanks for all the work invested in making this work!!
I have followed the guide you provided and it seems I am running into a bug.
Maybe you or someone else has run into this too?OS: Ubuntu 23.04
Wine version: (tried with 8.0.1 and 8.0.10 from winehq packages - stable and development respectively)
- Install runs just fine, no erros that I can tell...
- when I try to start with Logos.sh the startup shows but not the login screen and it just hangs there
- when I try to start logos with : wine LogosBible10/data/wine64_bottle/drive_c/users/andi/AppData/Local/Logos/Logos.exe
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
010c:fixme:shcore:SetCurrentProcessExplicitAppUserModelID L"LogosBibleSoftware.Logos4": stub
0114:fixme:heap:GetNumaHighestNodeNumber semi-stub: 000000000029EFDC
0114:fixme:seh:WerRegisterRuntimeExceptionModule (L"Z:\\home\\andi\\LogosBible10\\data\\wine64_bottle\\drive_c\\users\\andi\\AppData\\Local\\Logos\\System\\mscordaccore.dll", 0000000000FC0000) stub
0114:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0114:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 00000000224910D0, 34) stub
0114:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0000000022488988, 17) stub
0114:fixme:ntdll:NtQuerySystemInformation (0x000000ce,0x29d430,0x00000008,(nil)) stub
0114:fixme:nls:get_dummy_preferred_ui_language (0x8 0x380a 000000000029D260 0000000000000000 000000000029D258) returning a dummy value (current locale)
0114:fixme:nls:get_dummy_preferred_ui_language (0x8 0x380a 000000000029D260 000000000029D1B0 000000000029D258) returning a dummy value (current locale)
0114:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 000000002248DD78, 38) stub
0114:err:virtual:virtual_setup_exception stack overflow 16 bytes addr (nil) stack 0x120ff0 (0x120000-0x121000-0x2a0000)Has anyone seen this last error in the log before and knows how to fix / avoid it?
Thanks,
Andi0 -
Please double check your Wine Version. Logos 10 currently requires Wine Staging. Other Wine builds will not allow Logos 10 to run at this time.
Karl Andreas Hennig said:Hi, first of all, thanks for all the work invested in making this work!!
I have followed the guide you provided and it seems I am running into a bug.
Maybe you or someone else has run into this too?OS: Ubuntu 23.04
Wine version: (tried with 8.0.1 and 8.0.10 from winehq packages - stable and development respectively)
- Install runs just fine, no erros that I can tell...
- when I try to start with Logos.sh the startup shows but not the login screen and it just hangs there
- when I try to start logos with : wine LogosBible10/data/wine64_bottle/drive_c/users/andi/AppData/Local/Logos/Logos.exe
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
010c:fixme:shcore:SetCurrentProcessExplicitAppUserModelID L"LogosBibleSoftware.Logos4": stub
0114:fixme:heap:GetNumaHighestNodeNumber semi-stub: 000000000029EFDC
0114:fixme:seh:WerRegisterRuntimeExceptionModule (L"Z:\\home\\andi\\LogosBible10\\data\\wine64_bottle\\drive_c\\users\\andi\\AppData\\Local\\Logos\\System\\mscordaccore.dll", 0000000000FC0000) stub
0114:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0114:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 00000000224910D0, 34) stub
0114:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0000000022488988, 17) stub
0114:fixme:ntdll:NtQuerySystemInformation (0x000000ce,0x29d430,0x00000008,(nil)) stub
0114:fixme:nls:get_dummy_preferred_ui_language (0x8 0x380a 000000000029D260 0000000000000000 000000000029D258) returning a dummy value (current locale)
0114:fixme:nls:get_dummy_preferred_ui_language (0x8 0x380a 000000000029D260 000000000029D1B0 000000000029D258) returning a dummy value (current locale)
0114:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 000000002248DD78, 38) stub
0114:err:virtual:virtual_setup_exception stack overflow 16 bytes addr (nil) stack 0x120ff0 (0x120000-0x121000-0x2a0000)Has anyone seen this last error in the log before and knows how to fix / avoid it?
Thanks,
AndiLogos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Just to clarify in response to Frank that my written instructions for Debian Bullseye that I posted here do explicitly provide the command to install Wine Staging.
I will emphasize again that these instructions are for installing Wine Staging using Debian Bullseye. There are different instructions on the Winehq website for Ubuntu that you must follow. Please see https://wiki.winehq.org/Download where you will find the instructions for Debian, Ubuntu and Fedora. There also distro binary packages for some other distros. I have followed the Ubuntu instructions there and they work for me.
0 -
Ah good pointer Frank, I will try that, just installed it.
# wine --version
wine-8.10 (Staging)Thanks
0 -
I'm running Logos 10 on Arch Linux with xmonad through wine 8.9 staging, and whenever I click on something that opens up a popup window, such as layouts, documents, library, etc, it works just fine the first time I open the popup window, but after that I cannot reopen the same popup window. So, I can open Layouts and then Documents, but after I close either one, I won't be able to reopen them. It will just instantly disappear if I try to reopen them. For library and documents, I can get around the issue by dragging the icon into one of the window panes so that it opens up as a tab rather than a floating window. But for layouts, you can't open the layouts window as a tab, so I'm unable to use the layouts feature.
I used to have both xmonad and KDE installed, and back then I didn't have the problem on KDE but I did on xmonad. I still have the problem when I use the minimal config described here: https://wiki.haskell.org/Xmonad/Config_archive I'm using xmonad 0.17.1.
Does anyone have any idea what might be causing this problem or how I might be able to solve it?
0 -
Elliot,
I think you are running into a known issue called the menu bug.
I get around it by right clicking and selecting open. It then opens for me.
You can also create a shortcut to the function as another workaround.
Double-clicking on it also has been said to work.
0 -
I managed to install Wine via the instructions here:
https://www.linuxuprising.com/2019/09/how-to-install-wine-staging-development.html
And then I installed Logos via the instructions here:
https://github.com/ferion11/LogosLinuxInstaller/wiki/Logos---Verbum-10-for-Linux-Release-Notes
doing the last part "GUI install"
Logos opens and seems to work, except that I get this error:
Is this a problem? Is there a way to fix it?
Here's what I have:
Logos Bible Study 26.1
26.1.32wine-8.12 (Staging)
Feren OS, based on Ubuntu 22.10
0 -
The way to fix it would be to have a native Logos App. You can suggest it at their real suggestions webpage.
DAL
0 -
Yes, that would be the best solution. I would be glad to be another to make that suggestion. Can you give me a link to that page?
In the mean time, I am looking for a solution I can apply myself, because even if they do implement a Linux app, it will probably take awhile.
0 -
You could trry removing the library catalogue and the index and letting it re-run those tasks the next time it opens. You could also try using the appImage install option. Or the snap install option. This is a fairly common bug and a common one to overcome.
When you run the Logos.sh script these flags will probably resolve it. Run these 3 commands in order.
./Logos.sh --remove-all-index<br />./Logos.sh --remove-library-catalog<br />./Logos.sh
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
I didn't use that script to install, and I didn't knowingly install the script. Will those 3 commands still work for me?
0 -
Generates an error message:
./Logos.sh --remove-all-index
bash: ./Logos.sh: No such file or directory
I suppose I need to install the script. Where do I get it, or how do I do it?
0 -
If you did the manual install then no they won't work. It is well worth using the script. It arranges everything very nicely in one folder and has tools like the above for resolving issues.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
So I need to uninstall what I did, and re-install using the script, right? I'm looking at instructions here:
https://github.com/ferion11/LogosLinuxInstaller
I see the text of the script, but it isn't clear to me how to put it onto my computer, and how to make it run.
0
