Linux version of Logos Bible Software
Comments
-
Al Graham said:
Thanks for all the work done on Logos for Linux.
I have been able to install Logos on Lubuntu 20.04.
Logos will start and run a short time.
Attached is the terminal output and the wine backtrace.
Any help would be appreciated.
Al, could you confirm what version of wasta-wine you have installed?
Rik
0 -
Great Thank You Rik. It looks like its running now and downloading resources.
Walter
0 -
I've been having some crashes since upgrading yesterday; indexing was also a struggle--I think it's done after multiple attempts, but I'm starting to wonder what effect that's going to have on my SSD... :-\ Anyway, I saved a 'backtrace' from my latest crash and noticed that, in the System information at the bottom, my Wine build is wine-5.20 (Staging). I ran sudo apt install wasta-wine thinking that I might need 5.20.1, but was told that "wasta-wine is already the newest version (5.20.1~ubuntu18.04.1)". So I'm not sure what's causing my crashes, but I can submit my saved 'backtrace' if that would be of any interest.Rik Shaw said:Al, wasta-wine 5.20.0 has the missing dependency which leads to the crashing. So you need to upgrade to wasta-wine 5.20.1. Please let us know if you have upgraded to that new(est) version.
0 -
Paul Unger said:
I ran sudo apt install wasta-wine thinking that I might need 5.20.1, but was told that "wasta-wine is already the newest version (5.20.1~ubuntu18.04.1)". So I'm not sure what's causing my crashes, but I can submit my saved 'backtrace' if that would be of any interest.
Paul, you have everything updated. Wine itself is version 5.20-staging. But the packaging of wasta-wine is what is 5.20.1 (I control the wasta-wine version number: the first 2 digits correspond to the wine version, the last digit, the original ".0" or the current ".1" correspond to the packaging version. So if there is a missing dependency or other packaging change needed, it would go to 5.20.2, even though it would still be wine 5.20-staging).
Please do post the backtrace somewhere as a downloadable file so we can inspect it. Also, please report if the crashes were related to any activity or what you were doing at the time or if it was just random.
Rik
0 -
Any thoughts on how to resolve the kerning issue? Note the spacing between "F" and "r".
0 -
I've got that issue as well. A solution would be marv!Taylor said:<snip>Any thoughts on how to resolve the kerning issue? Note the spacing between "F" and "r".
0 -
My backtrace is here: https://www.dropbox.com/s/jy3mlmwv5pcwz9w/Logos%20crash%2001.txt?dl=0Rik Shaw said:Please do post the backtrace somewhere as a downloadable file so we can inspect it. Also, please report if the crashes were related to any activity or what you were doing at the time or if it was just random.
Rik
The crashes were happening when I had the Notes tool open and I was clicking the note to try to view it in the corresponding resource. Though it may be something wonky with the specific resource I had open--I can scroll about a page or two before Logos crashes. I can scroll other resources.
0 -
Taylor said:
Any thoughts on how to resolve the kerning issue? Note the spacing between "F" and "r".
The problem shown in "1" isn't a font rendering issue, but a issue of special characters in a string not being ignored. We can see in "2" that the same doesn't happen.
Normally, to make it easier to add keyboard shortcuts, special characters are inserted in the strings (often "_", other times "/t" or others). The string here is probably something similar to "F_riends And Counseling" (to indicate that the keyboard shortcut is the "r" and not the "F"). But as this feature was not processed, the character remained there.
If you aren't using the keyboard shortcut, then don't worry too much about it. This issue doesn't cause any additional errors (except this visual effect).0 -
I have the same issue as @Taylor -- "F r___" often has a space between. This also affects smart quotes. Compare the green and red boxes below:
[I'd add an image if I could figure out how... The "Insert/Edit Image" button isn't working for me; all I get is a 'broken link' box. :-( You should be able to view it here: https://www.dropbox.com/s/whsnbzb8sqn1465/Linux%20smart%20quotes.png?dl=0]
Paul
0 -
I have updated wasta-logos-setup to version 1.3.1. Notable changes include:
- Any existing Logos Data (Data, Documents, Users folders) will be saved to ~/.logos-data and then will be symlinked to the new installation. This means it won't be removed if you delete or re-install the ~/.wine-logos folder. If you need to symlink to a different location because your home directory is not large enough for a Logos install, then please make a ~/.wine-logos symlink to your desired location before starting wasta-logos-setup.
- Re-worked dialogs (much more streamlined now)
- Fixed a dependency that was causing an error for some that were upgrading from older versions of wasta-logos-setup.
- Log files are now automatically created and saved to ~/.cache/wasta-logos-setup
- Hopefully solved some occasional "hanging" of the Logos install process (when installing .NET or Corefonts).
With the above change of saving the Logos Data outside of the Wine installation, it means that wasta-logos-setup can be re-run at anytime without losing your data in case you want to be sure you are "up-to-date" with the wasta-wine process.
As a reminder, wasta-logos-setup only works for Ubuntu and Ubuntu-derivatives like Wasta-Linux, and it also is only 32-bit which means it installs the last version of Logos 8 (8.17.0.0.0014). A 32-bit version of Logos 9 is not available.
Looking ahead, once installing 64-bit Logos has stabilized I will work to make wasta-logos64-setup for installing it.
As a reminder, here is the link to the wasta-logos-setup Installation Guide.
0 -
Thanks Rik, that sounds really good! Just to clarify: if one has already Logos installed using wasta-logos-setup, rerunning wasta-logos-setup will (?move ~ copy?) any existing Logos Data to the location ~/.logos-data? Or does one have to move it there before running wasta-logos-setup? What you wrote sounds like the former--it's all done automagically--but I do want confirm that. Downloading all the resources is not fun... And is it a 'move' or a 'copy'? Having two copies would take a fair chunk of space.
0 -
Paul Unger said:
Thanks Rik, that sounds really good! Just to clarify: if one has already Logos installed using wasta-logos-setup, rerunning wasta-logos-setup will (?move ~ copy?) any existing Logos Data to the location ~/.logos-data? Or does one have to move it there before running wasta-logos-setup? What you wrote sounds like the former--it's all done automagically--but I do want confirm that. Downloading all the resources is not fun... And is it a 'move' or a 'copy'? Having two copies would take a fair chunk of space.
Yes, having 2 copies is not a good idea for space reasons. Here is some more detail on the steps of wasta-logos-setup:
1. When running the new version (1.3.0 and higher) it will *move* the Logos Data to ~/.logos-data if you have *real* data in the ~/.wine-logos folder (which would be if you used an older wasta-logos-setup or if you manually installed yourself). It checks if the folders in the ~/.wine-logos are "real" and moves them if so. If they are *symlinks* (which the newer wasta-logos-setup would make), it doesn't do anything.
2. It then *deletes* the current ~/.wasta-logos folder entirely: meaning each time you run wasta-logos-setup, it will make sure to not lose your data but will always do a clean install of Logos. Previously it would ask if you wanted to re-install or just "repair" (meaning it wouldn't touch the wine install, but it would just start the Logos installer). But as data is not getting lost, I think it is best to just re-install if you run wasta-logos-setup to reduce the confusion. The install time (creating wine prefix, installing .NET, corefonts, running the Logos installer, etc) is now less than 10 minutes on my 5 year old laptop, not the 40+ minutes it used to be a year ago.
3. After install is complete, symlinks are made from the ~/.logos-data (Data, Documents, Users) to ~/.wine-logos/drive_c/users/<user>/Local Settings/Application Data/Logos/ folder. IF a user did not have existing data (a "new" install) in the ~/.logos-data folder, then the symlinks are still inserted, but the folders of course are empty. When launching Logos, they will be populated.
So, this means if you want to backup your Logos data, you only need to keep a copy of your ~/.logos-data folder. The ~/.wine-logos folder is replaceable. For example, in migrating to a new machine, just put your ~/.logos-data folder in place before starting wasta-logos-setup and you should be all set to go.
Note that this is a somewhat significant change, so there may be new bugs, etc. Again logs are now created and stored in ~/.cache/wasta-logos-setup so if you experience any problems we can refer to them. But until this is used more "in the wild" you may want to make sure to keep a copy of your Logos Data, Documents, and Users folders.
0 -
Thanks for documenting that, Rik. I found it helpful / reassuring.
0 -
@Paul and others,
In further testing there are a few bugs in getting the ~/.logos-data created correctly, plus there is still some instability in installing .NET / Corefonts in the wine setup process. If you can hold on I am trying to upload a fix for the first item tonight, tomorrow I'll try to inspect the second part.
0 -
Rik Shaw said:
@Paul and others,
In further testing there are a few bugs in getting the ~/.logos-data created correctly, plus there is still some instability in installing .NET / Corefonts in the wine setup process. If you can hold on I am trying to upload a fix for the first item tonight, tomorrow I'll try to inspect the second part.
Version 1.3.2 is currently building and should be in the Wasta Wine PPA in about a half hour. I am off to bed so will check in tomorrow! Good night! :-)
0 -
Rik Shaw said:Rik Shaw said:
@Paul and others,
In further testing there are a few bugs in getting the ~/.logos-data created correctly, plus there is still some instability in installing .NET / Corefonts in the wine setup process. If you can hold on I am trying to upload a fix for the first item tonight, tomorrow I'll try to inspect the second part.
Version 1.3.2 is currently building and should be in the Wasta Wine PPA in about a half hour. I am off to bed so will check in tomorrow! Good night! :-)
wasta-logos-setup version 1.3.3 is now building. Minor changes include prompting the user to manually open "System Monitor", searching for "mscorsvw.exe" and ending those processes IF the install of .NET 4.8 seems to "hang". This happens occasionally for some, and regularly for others. It isn't determined yet why the process doesn't end cleanly, but in practice it seems the install of .NET 4.8 has completed successfully, it just doesn't clean itself up.
Anyway, this is all the time I have for this right now. Hopefully this updated wasta-logos-setup process to use ~/.logos-data for storing the Logos Data outside of Wine is stable enough for usage.
0 -
Greetings, community,
I had installed Logos awhile back, and it was working very well. After some updates, the indexer started crashing. After the last update, Logos wouldn't start at all. I delete it and re-install it. Now Logos starts fine, but the indexer crashes. I'm attaching the backtrace from the wine debugger. 6013.backtrace.txt
I also filed a bug report with wine. Any help or guidance would be appreciated. Many thanks for all the work to bring Logos to Linux.
Benjamin
0 -
Thank you soo much I was just about to give linux another try, and when I realized that Logos might be an issue I almost wanted to stop again.
You solution is great and works perfect for me!
Thank you a lot
0 -
I previously mentioned that some efforts were being made to run x86 software on Arm architecture.
Box86 is such an endeavor. "Box86 lets you run x86 Linux programs (such as games) on non-x86 Linux, like ARM (host system needs to be 32bit little-endian)."
https://github.com/ptitSeb/box86
Wine is now partially working. If anyone has a Raspberry Pi 8g (unfortunately I do not) or another device suitable for testing, I'd be interested to know if you can get Wine installed and of course, Logos 8, on the Arm device in its present state.
0 -
I wanted to report that using Daniel's latest appimage script, I am running Logos 9.0.0.0168 on my Pixelbook Go, 8th generation i5Y processor, 16GB RAM and 128GB eMMC SSD. This is a Chromebook with the standard Debian Buster container installed using the Linux Beta feature. I may have needed to satisfy a dependency or two when installing (I can't remember), but other than that, the going was pretty smooth.
It boots up a little slower than I would like, but it's pretty usable in its current state. I am liking dark mode a lot on this machine.
A display issue that crashed Logos and couldn't be overcome in the past doesn't appear to be happening now. I prefer using Daniel's method on Chromebooks because I can stick with the Debian container. It is possible to switch out the Debian container with Ubuntu so that Rik's method can be used, but that's extra steps.
The higher-end Chromebooks that come with a 10th generation i5U or i7U processor and NVMe SSDs would make a performance difference, but I wonder how much. When running Logos on a Chromebook like this, you have the performance hit of using Wine plus an additional layer for the Debian container running on top of ChromeOS.
0 -
Hello together, today I installed the Logos 9.1 with the Logos Linux Installer Script (fast) 2.21 on my Manjaro KDE Plasma Linux.
For me it works very good. Thank you.
0 -
Does anyone know how well Logos works on virtual machines? And if it works, which ones it would probably work best on?
0 -
It runs pretty much as native on Qemu.
I pass-through a GPU, but that is for watching course videos fullscreen in the app rather than using app.logos.com. It still runs really well without this, just I have to watch the videos windowed or there is video lag and stuttering behind the audio.
0 -
I used qemu with kvm for the best performance although virtualbox isn't too bad. IMHO wine based installation is reliable enough for most study needs and definitely a nicer solution than a vm. I stopped using the VM since wine 4.18. More recently, I've been mac only... probably until the Christmas sales.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
My Dude,
I have an i7 dell that just was a beast with windows so slow for no reason that I could tell, it's not my daily driver but I wanted to get it working so I put Elementary on it, as you know that's a ubuntu/debian dirivitive, and well to be honest I like the looks of it, it's pretty to me sue me, Anyway long story short. I am now further into any Logos install i have ever attemtpted on a Lilnux machine. It's downloading the library now, I'm looking forward to seeing if it will run fully but this is an amazing accomplishment. I look forward to being able to run Logos 9 on this thing if that happens, until then I'll be happy with 8. Who knows if this goes as well as it could I may just switch to linux fully.
Great JOB
0 -
Hello all.
I have now tried to run LOGOS 9 on an openSUSE Leap 15.2 Linux.
Whenever it trys to start WINE during the installation I get this error message and the LOGOS setup does not start. Under Ubuntu everything works without problems.
I use the script from "github ferion11" (fast)002c:err:module:load_so_dll failed to load .so lib "/tmp/.mount_wine64syPVNU/lib64/wine/ucrtbase.dll.so": /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /tmp/.mount_wine64syPVNU/lib64/wine/ucrtbase.dll.so)
002c:err:module:import_dll Loading library ucrtbase.dll (which is needed by L"C:\\windows\\system32\\sechost.dll") failed (error c000007a).
002c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x7bc7e075
0024:err:module:load_so_dll failed to load .so lib "/tmp/.mount_wine64syPVNU/lib64/wine/ucrtbase.dll.so": /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /tmp/.mount_wine64syPVNU/lib64/wine/ucrtbase.dll.so)
0024:err:module:import_dll Loading library ucrtbase.dll (which is needed by L"C:\\windows\\system32\\sechost.dll") failed (error c000007a).
0024:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x7bc7e075Maybe someone has a hint for me
Greetings Dominik
0 -
Good morning. I read yesterday about the release of Wine 6, how does that impact/change the status of Logos on Linux?
I did use the scripts a few months back and had it running on a system, but I was unhappy with the performance - due primarily to the horsepower of the PC - so I reverted back to the Windows version for the time being.
Thanks
Brian0 -
My understanding of the status is this:
32bit Logos 8 is very stable. Without media playback, speech or printing.
Logos 9 is 64bit only and we weren't quite ready for it - of course that is the nature of trying to get apps working on wine.
Wine 6 still has problems we'd like to see fixed. We have some problems with indexing in 64bit. If you have a smaller library it might be ok. You will most likely need a swap file because it does use more than max ram even on 16GB systems. Obviously I don't have knowledge of under the hood changes but it appears that the indexer has gone through some improvements which broke compatibility with wine.
There are difficulties with installing .net in wine 6. Some great work has gone on in terms of media support so people might start to have more success playing videos.
Daniel's installer is the most reliable way to get success. I get very few test submissions on winehq these days to if more people could test / report bugs that would be very useful.
I should say I was out of it for a few months, not having a PC, so others might be more up to date than me. I do have a PC now so I'm trying to catch up.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0
