Linux version of Logos Bible Software
Comments
-
yes sure.
I've switched to VirtualBox for now, until Logos 9 works on Linux. I am surprised how performant it works.
0 -
Logos 9 installs using
install_AppImageWine_and_Logos.shscript.When Logos 9 starts it does not run long. Attached is the backtrace from Wine.
Thanks for all the work the Linux team is doing.
(Lubuntu 20.04)
0 -
The terminal output is usually much more helpful than the backtrace. If you can attach the terminal output that could help. Thanks.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
6330.TerminalOutputLogosWine.txt
John Goodman said:The terminal output is usually much more helpful than the backtrace. If you can attach the terminal output that could help. Thanks.
John:
Please find attached the terminal output which occurs shortly after Logos 9 starts up. (Lubuntu 20.04.01 LTS).
Thanks again for all the work you Daniel, Rik and others are doing with Linux and Logos.
0 -
Indexing is running after a large update and it doesn't seem to finish. I've tried several times to rebuild via ./Logos.sh removeAllIndex followed by 'indexing' It is running but I see the attached error message. I see it if I start Logos.sh and it kicks off indexing or if I run indexing directly. Is this a normal error message? Anything else I should try?
0 -
That's exactly what I'm seeing, Rob.
0 -
I am in the same position as Rob and Nick. Indexer runs, but does not complete.
I also have the clipboard issue discussed earlier. When I run "sudo ./Logos.sh wine64 regedit" I get:
======= Running wine64 only: =======
wine: '/home/USER/LogosBible_Linux_P/data/wine64_bottle' is not owned by you
wineserver: /home/USER/LogosBible_Linux_P/data/wine64_bottle is not owned by you0 -
Al Graham said:
Logos 9 installs using
install_AppImageWine_and_Logos.shscript.When Logos 9 starts it does not run long. Attached is the backtrace from Wine.
Thanks for all the work the Linux team is doing.
(Lubuntu 20.04)
You are being quite adventurous here. Using your native, old, wine-5.0 (vanilla), without any patches (nor the staging set), and still trying to do the installation using install_AppImageWine_and_Logos.sh.
If the goal isn't the adventure, and you just want it to work, then install using the script fast_install_AppImageWine_and_Logos.sh and select the option with the AppImage.Rob Perry said:Indexing is running after a large update and it doesn't seem to finish. I've tried several times to rebuild via ./Logos.sh removeAllIndex followed by 'indexing' It is running but I see the attached error message. I see it if I start Logos.sh and it kicks off indexing or if I run indexing directly. Is this a normal error message? Anything else I should try?
This message is quite normal. And in fact at the end of the index, it seems that the LogosBible index stopped for good (in my case it was 51%). You can see this through the CPU usage by the index process. But after closing and reopening, the index was ready and working. At least that's what happened here. But we don't have much guarantee due to the recent changes.
0 -
Daniel:
Thanks for your help.
Attached is the terminal output when I use fast_install_AppImageWine_and_Logos.sh.
0 -
Al Graham said:
Daniel:
Thanks for your help.
Attached is the terminal output when I use fast_install_AppImageWine_and_Logos.sh.
...
You are getting the error message:
err:seh:segv_handler_early Got unexpected trap 6 during process initialization
This kind of error normally happens when using liveUSB and WINE cannot write to the USB, or when using liveISO in RAM and you don't have enough RAM to write all the data. But that doesn't seem to be the case here.
I saw from your previous log that you are using Ubuntu, but I don't know which version. Perhaps some incompatibility with glibc (one Ubuntu update maybe can solve it).
A good try would be to install wine-staging-5.11 from winehq.org:
wiki.winehq.org/Ubuntuusing something like (you can change the "bionic" to your version):
sudo apt-get install winehq-staging=5.11~bionic wine-staging=5.11~bionic wine-staging-amd64=5.11~bionic wine-staging-i386=5.11~bionicthen try using the option with native WINE on fast_install_AppImageWine_and_Logos.sh
This will ensure better compatibility with glibc.
I would like to make one AppImage with all dependencies for 64 bits (including glibc), as I had done for 32 bits, but there are some technical impossibilities, like the double glibc combo for WINE WoW64 (and now a new bug too), that has been holding me back for quite a while. For only then, we could have more guarantee that all the installations would behave in the same way. Without me having to say that it works very well on the test server using Ubuntu bionic (and on my local machine using Gentoo Linux), as you can see here: github.com/ferion11/LogosLinuxInstallTests/releases/download/v2.20/videoa.mp4
But for now, we will have to live with the peculiarities of each Linux distribution and its different versions too.0 -
I'm getting the following error during a fresh install on Ubuntu 20.10. I have installed on this OS before without errors, but I see that the fast_install script was updated 2 days ago.
"./fast_install_AppImageWine_and_Logos.sh"
Returns:
./fast_install_AppImageWine_and_Logos.sh: line 6: syntax error near unexpected token `newline'
./fast_install_AppImageWine_and_Logos.sh: line 6: `<!DOCTYPE html>'Any suggestions are much appreciated.
0 -
Purist said:
I'm getting the following error during a fresh install on Ubuntu 20.10. I have installed on this OS before without errors, but I see that the fast_install script was updated 2 days ago.
"./fast_install_AppImageWine_and_Logos.sh"
Returns:
./fast_install_AppImageWine_and_Logos.sh: line 6: syntax error near unexpected token `newline'
./fast_install_AppImageWine_and_Logos.sh: line 6: `<!DOCTYPE html>'Any suggestions are much appreciated.
You downloaded the wrong file.
We can easily be fooled with the "blob" version (made to be used only by the web browser) instead of the "raw" version (the real file) in the URL. They are generally similar in size and have the same name too, but the blob format is html, and the raw, in this case it would be a bash script.
The raw link for the v2.20 is:
https://github.com/ferion11/LogosLinuxInstaller/releases/download/v2.20/fast_install_AppImageWine_and_Logos.sh0 -
Daniel Ribeiro da Silva said:
The raw link for the v2.20 is:
https://github.com/ferion11/LogosLinuxInstaller/releases/download/v2.20/fast_install_AppImageWine_and_Logos.shThat runs. Thanks.
0 -
For me the script (v2.20 fast AppImage) works very well on Ubuntu 20.10. I only changed the LOGOS version number in the script to 9.0.0.0181 before I ran it.
Thanks a lot for the good work. [Y]
0 -
Hello everyone,
I've updated the wasta-logos-setup process to use 32-bit wine 5.20-staging with the latest Logos 8 32-bit installer, 8.17.0.0014. With the wine updates and Logos updates it seems to run really well, with it only taking approximately 10-12 minutes to do a clean install from scratch (to install .NET 4.8, run the Logos installer, etc). Also, the Logos Indexer seems to be responsive and perform decently well (certainly much better than with older versions of Logos 8).
In summary, for those taking the conservative route waiting for 64-bit wine to be more stable, it seems like a good option to update to this "last of the 32-bit installers". I have re-organized the wasta packages, placing things in a "Wasta-Wine" Ubuntu PPA rather than the previous "Wasta Logos" PPA. The documentation on getting it setup and installed is on the Logos 8 Wine Installation Google Doc
If you are on the older wasta-logos-setup and everything is running well you may not want to update. If you do update, please save your Data, Documents, and Users directories from your current install so you can restore them later. Likely the updated Logos version may require some additional resource updates, but you may save some bandwidth by saving and restoring these folders. This is explained in the above guide.
Rik
0 -
Rik Shaw said:
for those taking the conservative route waiting for 64-bit wine to be more stable, it seems like a good option to update to this "last of the 32-bit installers
I appreciate this, Rik. I am currently on Logos 9 64-bit AppImage, with no indexing or search features working. I'd love to revert, but I wonder how we can keep Logos 8 from updating to Logos 9 from within the app itself. Is there a "Do Not Update" setting somewhere?
Also, do you know if those of us with version 9 licenses and features activated can go back to v.8?
0 -
While following the new wasta instructions provided by Rik, nothing happens when I run "wasta [Logos] Setup" from the Main Menu.
When I run "sudo wasta-logos-setup" in Terminal on Ubuntu 20.10 I see:
wasta-logos-setup started as root user.
No processing done. Exiting....0 -
That's funny. I just ran it without "sudo" and it started the installer. It proceeds until I say yes to corefonts, then hangs:
------------------------------------------------------
Running /opt/wasta-wine/bin/wineserver -w. This will hang until all wine processes in prefix=/home/purist/.wine-logos terminate
------------------------------------------------------0 -
@purist: 32-bit will not upgrade to version 9 because there is no Logos 9 32-bit (we are going to be stuck on Logos 8 for 32-bit).
Yes, you can NOT use sudo to run wasta-logos-setup because it is a user level process. I should make the error message more clear to restart without sudo.
The wineserver message is "normal" but after some time it should continue....
Now, to the main problem you may see: what Ubuntu version are you on? I am having problems with 18.04 with wine 5.20-staging. It is crashing after activating Logos with this message:
RtlConvertToAutoInheritSecurityObject () at Z:\root\wine-git\dlls\ntdll\sec.c:1721
0x7bc565c9 RtlConvertToAutoInheritSecurityObject+0x199 [Z:\root\wine-git\dlls\ntdll\sec.c:1721] in ntdll: ret
Unable to access file 'Z:\root\wine-git\dlls\ntdll\sec.c'I put a note on the Google Doc saying if you are running 18.04 to WAIT until we sort out if this is possible to get around, but the error is coming from an update to wine 5.17+. I don't know why 20.04 isn't hit with the same crash, mysteries abound.
It may be that we need to roll back to the "safe" wine 4.18 for Ubuntu 18.04 users. Or it may mean if I re-compile wine with a reversion of that "fix" that causes the crash it will work. Using 4.18 means it will take longer to install, but it may be "stable". I'll report back after further testing.
0 -
Rik Shaw said:
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.
0 -
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
