It may be that we need to roll back to the "safe" wine 4.18 for Ubuntu 18.04 users. Using 4.18 means it will take longer to install, but it may be "stable". I'll report back after further testing.I have rolled back wasta-wine to version 4.18 for Ubuntu 18.04 'bionic' users. If you already installed wasta-wine version 5.20 then please remove it, and then install wasta-logos-setup again which should bring in wasta-wine version 4.18.
Negatives of version 4.18 of wine include a much longer .NET 4.8 install (with it sometimes "hanging" meaning you may need to force close it and re-run wasta-logos-setup again to hopefully get it installed). It could take around 40 minutes (or more!) to complete the .NET 4.8 installation (compared to about 6-7 minutes for wine 5.20 in Ubuntu 20.04). Additionally, running Logos with wine 4.18 will result in an initial crash the first time you start Logos. Just restart Logos and it should work the second time.
So in summary, Ubuntu 20.04 / 20.10 with wasta-wine 5.20 (staging) is preferred, but for the 18.04 users at least Logos should remain functional using the older 4.18 wasta-wine version.
Linux version of Logos Bible Software
Comments
-
Hello everybody,
Many thanks Rik for your great job. [:)] I used yesterday afternoon the wasta install and it was fine for me.
I had to add "sudo apt upgrade" after the update because of broken dependancies, and then all was ok for me, Logos 8 works great now, and also the indexer.
For the hanging issue, I also had it, but hitting Ctrl^C allowed the install procedure to continue.
Hoping this could help for someone.
Jon
0 -
Rik,
I'm running Ubuntu 20.10, with update and dist-upgrade complete. The process hangs permanently after agreeing to install corefonts.
Update: This issue is resolved. Further issues with my installation on 20.10 are being worked out in the Google Doc comment section.0 -
@purist, I think I just replied to you on the Google Doc. But it may be getting stuck in either setting "ddr=gdi" or in "font smoothing", both of which are done after corefonts before installing Logos. As Jonathan reported, possibly a "ctrl + c" would work to cancel the hung process and it may continue with the install.
In my reply I left a hint on piping your output to a text file so we can examine the problem further. Please keep us posted!
Rik
0 -
Again, just a reminder that if you haven't upvoted the project on WineHQ, you can help by logging in and voting on the Top 25 list. You can cast up to three votes with your account.
For those of us with limited technical ability, this is one thing we can do to attract skilled attention to the project.0 -
Update on 32-bit wasta-logos-setup with Logos 8.17.0.0014 and wine 5.20-staging for Ubuntu 18.04, 20.04, and 20.10:
I found that libjpeg62:i386 needed to be added as a dependency, and after adding it I am no longer seeing crashes on 18.04 like previously. My 20.04 test machine had that package installed, which is why I didn't originally see the crash but others did. I have pushed updates to wasta-wine (version 5.20.1) for 18.04, 20.04, and 20.10 to the "Wasta-Wine PPA."
So, if you are willing to test, you can follow the Google Doc guide and hopefully you won't experience crashes. Please let us know your experience, either here or directly on the Google Doc (preferable).
As a reminder, this wasta-logos-setup process will not be able to be updated to Logos 9 since the Wasta process is only 32-bit. But hopefully it will stand as a "best possible 32-bit install" while we finalize testing, etc. with 64-bit Logos 9 installs.
0 -
I'm running Linux Mint 20
I'm very new to this
I'm trying to figure out how to install the .net packages from a comand line.
Could please give specific instructions.
Thanks
Walter
0 -
Loye Young said:
I have been able to get Logos 8 (Windows) running on Fedora Linux, using Wine, in 64 bit.
<rant>
The developers of Logos 8 need not be afraid of supporting Linux users on Wine, or even distributing Logos 8 packaged to run on Linux natively. (.NET code can run on Mono natively, with full Microsoft support.)There is nothing about Linux that prevents installation and use of proprietary software. There is absolutely no requirement for source code to be available for every program on a Linux machine. The owner of the machine can, if desired, install a proprietary binary blob of code, without any technical or legal prohibition or impediment. It is up to the owner of the machine to decide. (That's called "freedom.")
</rant>The following is merely the bare outline of what I did. I'm not attempting to give a detailed "How To" article. (Also, I probably will not answer questions or help with your installation.)
System:
Fedora release 32 (Thirty Two)
wine-5.17 (Staging)
winetricks-20200412-1
Processor Information
Socket Designation: SOCKET 0
Type: Central Processor
Family: Core i5
Manufacturer: Intel
Version: Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz
Voltage: 1.2 V
External Clock: 100 MHz
Max Speed: 2500 MHz
Current Speed: 2500 MHz
Core Count: 2
Core Enabled: 2
Thread Count: 4
Characteristics:
64-bit capableComments:
1. I used Winetricks to install Microsoft's .NET 4.7.2 and 4.8, after a failed attempt to install. (I had set the wineprefix to Windows 10, using the graphical "Wine Configuration" tool.)
- Run Winetricks from the command line, which will give you great visibility into what's going on under the hood. There are a lot of "fixme" and similar comments, but almost all of them are not going to get in the way of running Logos (even if they sound scary).
- Ignore the pop-ups and warnings that complain about 64 bit and Mono not being present. If it says "Mono is not present", that is a Good Thing, because it's trying to remove Mono, which is for running .NET natively on Linux and conflicts with the Wine installation of MS .NET (even though MS is the sponsor of Mono).
- Winetricks will install earlier versions of .NET. I'm not sure if they are required, but I figure the developer had some reason to install them, so let it do what it did.
- .NET graphical installers will open from time to time. They will complain about not finding an installer program and warn you of mysterious and unstated problems in the future. Ignore and click "Continue". (The Wine peeps fixed that problem a few years ago.)
- After installing each .NET package, .NET will say you need to reboot. In this situation, that does not mean reboot your machine. it just needs to restart the wineserver. Click the reboot button in the .NET graphical. (I think "Reboot Now" is what it's called, but my memory might be wrong.)
- After the .NET graphical finishes, the command line will say something like "Running wineserver -w, which will hang until . . . . " Open another command line session and run "wineserver -k", which will kill the extraneous processes and Winetricks will move on.
- Have patience.
2. Likewise, I installed Logos from the command line: "wine [path\to\LogosSetup.exe]"
- As mentioned above, I had previously configured the wineprefix to run as Windows 10 (which Faithlife says is a minimum), but somewhere along the way, Winetricks seems to have changed the setting to Windows 7. Logos doesn't complain. (I wonder if the attempted installation of Logos before installing .NET might work better, but since my installation is working, I'm not going to try to figure it out.)
- My implementation of Wine requires the use of back-slashes, in the style of Microsoft. [shrug]
- Wine installed the program at ".\.wine\drive_c\users\[username]\Local Settings\Application Data\Logos\Logos.exe" Such location seems odd to me, but perhaps Windows these days installs programs there. Or perhaps the Faithlife peeps put it there to prevent others on the machine or network from running Logos without paying for another license. They gotta make a living, and as the Apostle said, "Don't muzzle an ox when he is treading."
3. If Logos fails to start from the desktop or your Wine menu, or starts and then immediately closes, run Logos from the command line and look at the command line output for debugging information. If that doesn't work for you, try running in a Virtual Machine, or maybe consider whether your kung-fu level is ready for Logos-on-Linux. (I watched Kung Fu Panda last night. Great flick.)
4. When running a program designed for Windows, the program may in fact perform like it does on a Windows machine, to wit: needless CPU activity, bloated RAM, and lots of disc activity, all of which make for poor performance. YMMV, depending on how fast your machine is. Mine is old (circa 2014) and slow, so I get what I get. I need to buy a new rig anyway, so that will probably help.
- The first time you fire up Logos, it will need to download and index the data files. The download is not horrible, but the indexing is very painful. The indexing is greedy for CPU (every CPU core and thread was at 100%) and disc IO. Just be patient and let it run overnight. Fortunately, I have an SSD, which makes the disk I/O much faster.
- 8GB of RAM is not enough, even without indexing going on. When running Linux natively, 8GB is plenty, so I didn't even have a swap partition. But performance tanked when running Logos 8, so I added a swap partition of 8GB, which made a big difference. I set system swappiness at 20. (Google "linux swappiness"). Probably would have been better to do that before installing.
Good luck.
Happy Trails,Loye W. Young, OP, JD
I'm running Linux Mint 20
I'm very new to this
I'm trying to figure out how to install the .net packages from a comand line.
Could please give specific instructions.
Thanks
Walter
0 -
@ Rik Shaw: Thanks for your ongoing work with this!
I confess I got a bit confused following the directions in the Google doc... I ran sudo add-apt-repository ppa:wasta-linux/wasta-wine and got a bunch of "Get" and "Hit" lines with a final line of "Reading package lists... Done." That seemed normal, so I then ran sudo apt update and got a bunch more "Get" and "Hit" lines; but this time, after the line "Reading package lists... Done", there's the line "18 packages can be upgraded. Run 'apt list --upgradable' to see them." I went ahead and ran apt list --upgradable and found 4 wasta-logos / -wine / -winetricks packages in the list. Since sudo apt update didn't install them, I was at a bit of a loss. Back in the Google doc, though, I re-read the next "Optional" line and saw it was sudo apt upgrade rather than update! Running that installed the packages I needed to continue. It might be good to highlight that difference for us noobs...
[...later...] No hangup on installing Core fonts here. I was asked to affirm installation of .NET 4.0 and 4.8, and then request to restart. I went ahead with [Restart now] and was then requested to install Core fonts--but there was no restart! The terminal churned away for a good while until I got the Welcome to Logos Bible Software Setup window. I selected [Next] [Typical] [Install] and waited until I could click [Finish]. A bit more terminal and I got a "Logos setup complete!" window, with instructions for copying Data, Documents, and User folders back to my new Logos profile folder, which I did. When I started Logos there were 1.9 GBs to download, but that's now done (ten minutes later?). When I opened a Layout (which were saved), all my resources say, "This resource is not currently available on this device, but here's a preview..." [Download now] [Open in Web App]. So it looks like I'm going to have to figure out how to re-download all my resources. :-( I'm hoping there's an easy way to do that, since I skipped that step when I first opened Logos.
Paul
0 -
4010.winelogosTerminalOutput.txt
Rik Shaw said:Update on 32-bit wasta-logos-setup with Logos 8.17.0.0014 and wine 5.20-staging for Ubuntu 18.04, 20.04, and 20.10:
I found that libjpeg62:i386 needed to be added as a dependency, and after adding it I am no longer seeing crashes on 18.04 like previously. My 20.04 test machine had that package installed, which is why I didn't originally see the crash but others did. I have pushed updates to wasta-wine (version 5.20.1) for 18.04, 20.04, and 20.10 to the "Wasta-Wine PPA."
So, if you are willing to test, you can follow the Google Doc guide and hopefully you won't experience crashes. Please let us know your experience, either here or directly on the Google Doc (preferable).
As a reminder, this wasta-logos-setup process will not be able to be updated to Logos 9 since the Wasta process is only 32-bit. But hopefully it will stand as a "best possible 32-bit install" while we finalize testing, etc. with 64-bit Logos 9 installs.
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.
0 -
Walter D. Huyck Jr. said:
I'm running Linux Mint 20
I'm very new to this
I'm trying to figure out how to install the .net packages from a comand line.
Could please give specific instructions.
Thanks
Walter
Walter, since Linux Mint 20 is based on Ubuntu, you can follow the guide for wasta-logos-setup here
The wasta-logos-setup process will take care of installing .NET, etc. so you do not need to manually do it.
Rik
0 -
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 -
Al Graham said:
Wine 5.20 is the version being used.
Thanks again for your help.
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 -
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:
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 -
I installed Logos 9 on Ubuntu 20.04 using this method, and I got basic functionality working, but not everything is working. Let me know if anyone has any different results.
Tools
- Atlas causes "Program Error: This can be caused by a problem in the program or a deficiency in Wine. You may want to check the Application Database for tips about running this application."
- Canvas kind of works except for Insert Passage, which kind of defeats its purpose.
- Bible Search doesn't work
Guides
- It seems like none of the guides are working
Trying to close any of the above crashes Logos (though keeping them open is fine).
Docs
- It looks like the docs do work
Let me know if you have anything to add or if anything that's not working for me is working for you.
Note, I've also been testing out using a virtual machine, and it works pretty well, but there are two things to keep in mind if you want to try using that for running Logos 9. First, the Windows 10 operating system takes up about 20 GB, so if you want to install Logos in a virtual machine, you'll need an extra 20-30 GB in addition to however large your Logos data folder is. Second, when installing Windows 10 onto a virtual machine, it will ask you for a registration code. You can skip this step by saying that you don't have a registration code, and you can use Windows just fine without ever activating it. However, technically, doing so goes against the Terms and Agreements. So if you plan on using a virtual machine for Logos long term, you'll have to purchase a Windows registration key (or if you already own an old Windows 10 computer, you might be able to snatch it's registration key and use that as long as you uninstall Windows from that old computer). Also, you would still technically be using Windows, so if you're a Linux purist or a privacy enthusiast, you might not want to use a virtual machine. Other than that, the only performance issues I've ever had with the virtual machine was that the videos in Logos would lag, but they could also just be watched on Linus through the web app.
0 -
Dominik Wagner said:
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
Because openSUSE Leap is still using glibc 2.26:
Why Leap 15.2 still is using glibc 2.26?Brian Hollifield said: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
BrianAlong with improvements, there are several bugs in the new versions of WINE. The new version isn't always the most compatible. Namely, many applications still work better with old versions 3.x of WINE (it's a well known fact).
0 -
New issue that I just experienced:
I noticed that 9.2 was released and attempted an Update Now, that didn't see an update. I then downloaded the Logos Setup and when running it, it throws an error that Windows needs to be updated to install.
Update:
The issue was having the prefix set to Win7 to allow indexing and fast load times. Switching back to Win10 allowed the update to go through with no issue. I don't recall this issue in previous versions
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Read the guide for an update. Backup your data first. We install with windows version set to 10 but run Logos with windows version set to 7. This is due to a bug in .NET rather than wine or Logos. Updating doesn't really work. Essentially you backup your data, do a fresh install and replace your data into the new install.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Been playing around a little with L9 and the indexing issue is a major issue. The Win7 workaround does not work as of this time for a library with more than a small amount of resources.
The parse_url error that spams like crazy is:
0134:fixme:path:parse_url failed to parse L"Libronix.DigitalLibrary.Utility.resources"
I tried running the indexer with the LC_ALL=C command, as that had worked with a previous parse_url spamming error, but it does not seem to work the same way.
Former workarounds: As stated setting to Win7, deleting the files in the Index Folders and running Rebuild Index also seem to not work.
Rebuild Index, does set the three Index folders to 2 files each, which is in line with how it worked previously, but there is no action with the files at all - which is not in line with past action, when the indexer would complete.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Update:
I'm running the Logos 9 Indexer on a system with 12 gigs of Ram and I setup a 24 gig swapfile to add significant swap resource for the process. SSD and i7 processor, so system power and resources should not be a problem - never have been on Windows, nor on any version of Linux up until very recently. Now even the overkill of system resources available is getting no movement at all and kills after eclipsing all the resources available - with no movement at all on the index files of any kind.
Maybe @BradleyGrainger can give some insight as to anything that may have changed with the LogosIndexer.exe process that we can research within the wine setup. Calling different dlls, new permissions, etc.
The fact that there is absolutely no movement on the Index files is what bothers me most - the process runs for hours at full cpu and nothing accomplished at all - at least if there was some movement with the files, we could know that the indexer was at least doing something.
This is the same under winxp, win7, win 8, win8.1 and win10 settings for the prefix in wine
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Working with Bradley, we were able to establish a workaround for those who also have a working Windows install.
There is an issue with the AutoComplete database not completing on the Linux install. If you have a fully indexed Windows install you can copy the two files from the AutoComplete directory into the same directory in the Logos Data wine folder.
Doing so allowed the indexer to fully complete on win with windows version set to Win10!
It also allowed the indexer to rely heavily on the CPU, rather than RAM, which is part of the problem with whatever is going on with the AutoComplete database hanging the Linux install.
My AutoComplete database file in Linux was a small fraction of the 150 MB completed Windows file.
Hopefully Bradley and the Dev team may be able to shed some light on the process in the future so we can try to locate the bug causing this in wine, since the logs seem to not give us any information useful to the devs at WineHQ
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Update: New workaround from Linux only.
Using winecfg set LogosIndexer.exe to windows version winxp. Run the indexing. Once AutoComplete.db is finished kill the indexer. You'll see the file stop growing if you view it in a file manager. Then set windows version to win10 and run the indexer again.
I think we now understand why this happens so hopefully it won't be too long before we have it working without this extra few steps.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Has Logos 9 continued working well on Manjaro KDE since you installed it in December? Any problems?
0 -
Had to reinstall due to unrelated crash and data loss. Linux Mint 20.1 xfce.
Tried both the Wasta Script and Daniel's regular AppImg script. They both fail after installing Net 4.0 when it tries to install the MS DotNet 4.8 update. I get the warning "Unable to create or save new files in the folder into which the files are being extracted. Please check the folder properties to ensure you have permission on the folder to write files and that the folder is not read-only.
Daniels's "fast_install_AppImageWine_and_Logos.sh." script does complete successfully. It executes and downloads the resources. but then crashes every time. The Logos windows disappear and the Indexer remains running in the background."
Saved and attached the Backtrace.
0
