Linux version of Logos Bible Software
Comments
-
Zachary Rohman said:
Thanks Bill. I just read from page 37 on.
How is Logos currently working for you today?
Are there any pros or cons to using logos the way you are?
I'm eying a Lenovo C630 Chromebook with 8GB of RAM and an 8th gen i5 (I think the Pixelbook was only the 7th gen) so I'm hoping the specs are enough.
Could you update on how good it's running and what you've learned over time? What method works better and any bugs you've experienced?
I ran Logos on my Pixelbook, which had a 7th generation i7, 16gb of RAM and a 512 NVMe SSD. Logos ran adequately on the Pixelbook. I would recommend getting a Chromebook with 16gb RAM because right now "Crostini", the name of the Linux environment on Chromebooks, only allows half of your machine's physical RAM to be allocated to it. This is a limitation of the Linux container in Chromebooks as it is currently implemented, but evidently it is supposed to allow for more in the future. If your laptop has 8gb of RAM, that means you'll only have 4gb allocated to the Linux container and the performance of Logos running in the container could suffer. Also, I would recommend an NVMe SSD that is large enough for your library. Mine is 50gb, so I needed a larger SSD. The Lenovo has an eMMC SSD. eMMC is slower by far, and could also affect performance.
Basically, trying to run Logos in a Linux container on a Chromebook means that you are on your own with no official support from Faithlife apart from this one thread. Rik, John, Daniel and others who are doing the work on getting Logos working on Linux are quite knowledgeable and ready to help, but you should know this going in. You should be prepared to use the Logos web app or the Logos Android app when things break or when you run up against an issue.
I no longer have the Pixelbook, but I am looking at getting one of the new Chromebooks with similar specs as my Pixelbook.
Others in this thread can address the known bugs and limitations that currently exist.
0 -
hey guys, i have problem with Logos
http://i.imgur.com/F86g6zG.png
It was working stable and after couple months i get this error popup now?0 -
Could you give us more details? And how was it installed initially?
0 -
I had a stable working version in Linux Mint 19.2 xfce installed (using instructions at:
https://docs.google.com/document/d/1Gms_Bc2Q_OOH3G5lmP6twXnqiSWxrFFT7lCN3nRyymw/edit#
Last week I upgraded to Linux Mint 20 xfce and did a fresh install using the same instructions. It ran fine as usual for a few days, but today it crashes with the same notice Paul is getting. Clicking the "Show Details" button in the Wine dialog or the Logos window merely closes all the Logos app windows. When loading I getr the "Preparing" dialog and the frame for the Logos main window, then the crash notice.
0 -
Paul and Kevin,
Can you click the "show details" in the crash window to get more information? Also can you confirm your wine version (or wasta-wine version since I think you used this method) and your logos version?
Rik
0 -
Hi again, Rik. I have been dealing with a number of (mostly small) issues since upgrading to Linux Mint 20 and made a few changes, so I have opted to reinstall Logos from scratch. The new setup has wasta-logos-installer v.8.13.0.0008.0~ubuntu20.04.1; wasta-logos-setup v.1.1.2~ubuntu20.04.1; wasta-wine v.5.7.1~ubuntu20.04.1; and wasta-winetricks v.20200412.3~ubuntu20.04.1 -- All installed 2020-07-13.
The installer runs fine and Logos is now downloading resources. I will try this out first and get back here if it fails to solve the problem.
BTW -- all the windows just disappeared immediately when I clicked "show details".
Thanks for all your work on this!
Kevin
0 -
I have just installed Daniel's appimage in a Linux container on the new Acer Spin 713 Chromebook. This has a Comet Lake i5U processor, 8gb RAM and 128gb NVMe SSD. The script installed and is running well. BTW, for the adventurous who need a larger SSD, evidently you can install a larger SSD.
However, the installation didn't create a launcher icon, so I have to launch Logos from the terminal.
BTW, they fixed the issue that prevented more than half of your available RAM to be available to the container. With my 8gb of RAM, 6.5gb is allocated to the container when it is running, leaving 1.5gb to ChromeOS.
The performance is really good.
When installing, follow the Logos wiki article on copying over your Data, Users and Documents folders to your installation. I let the appimage install and then I shut down the installation at the point where it asked for your Logos credentials. That's when I copied over everything to the installation and it worked like a charm.
0 -
If I had to guess, I would say that version 5.x of wine still can't successfully full update LogosBible main application major versions, and when the LogosBible books's library is updated thinking that the application has been updated, causes an incompatibility problem (then the crash). But this guess still needs to be tested.
0 -
My wine-staging 5.11 is now successfully indexing and updating Logos via a command line install on debian bullseye 64 bit and win10 and dotnet48. Updating Logos wasn't working for me up to 5.9 staging (approx) but is now (I think there was a general problem with 5.10 staging). Indexing in win10 is successful. I haven't tested 5.12. Happy to provide how-to if you are interested. Currently running Logos 8.14.0.0010 for 2 weeks now with minor issues, broadly as listed on the winehq "Logos 8" page.
So 5.x of wine CAN work, if you use wine-staging.
0 -
Nick said:
My wine-staging 5.11 is now successfully indexing and updating Logos via a command line install on debian bullseye 64 bit and win10 and dotnet48. Updating Logos wasn't working for me up to 5.9 staging (approx) but is now (I think there was a general problem with 5.10 staging). Indexing in win10 is successful. I haven't tested 5.12. Happy to provide how-to if you are interested. Currently running Logos 8.14.0.0010 for 2 weeks now with minor issues, broadly as listed on the winehq "Logos 8" page.
So 5.x of wine CAN work, if you use wine-staging.
Hi Nick,
Was the update from version v8.13.0.0008 to v8.14.0.0010 using wine-staging 5.11?
I had bad times with the wine up to the v5.10 (It "...tested me ten times." Numbers 14:20-23). If the current versions survive another major update of LogosBible, then I will consider an update again.
0 -
@ Daniel: Yes, it was all the way from 8.10.0032 to 8.14.0.0010 using wine-staging 5.11
0 -
Nick said:
@ Daniel: Yes, it was all the way from 8.10.0032 to 8.14.0.0010 using wine-staging 5.11
Thanks.
Now I have multiple versions running here, to test (using the portable version). The wine-staging v5.12, from playonlinux, have one compilation bug, then I'm using the wine-staging v5.11 to test, but the "wineserver" process is still using 100% of the CPU, so my personal installation is still the wine-staging v4.21 that don't have this bug (because my machine is old and need more help on the performance side). Both versions are indexing correctly without requiring additional procedures.
The LogosBible v8.15.0.0004 is releasing very fast (ref. link), so I will try to test wine-staging 5.11 (or higher) up to the LogosBible v8.16.0.xxxx. But that bug of "wineserver" using 100% of CPU isn't a good thing. If you have one fast multicore CPU, it maybe ins't a problem having one core running at 100% just to the "wineserver" process, but it still isn't a good thing.
0 -
I have two things to share.
I have switched my primary phone from Android to a PinePhone and have been following its progress and its development. At present, the only solution to utilize Logos on a PinePhone would either be to export your material out of DE Logos and copy it to the PinePhone or to use the web browser. Anbox support is still in development but when done I hope to test the Logos app.
Secondly, there is the following project which should be given due attention.
https://github.com/ptitSeb/box86
This project seeks to allow Arm devices to run x86 programs. They mention that Wine is not currently supported but support is planned for the future. This potentially could allow Logos to run on Arm devices on Linux through box86 + Wine. We'll need to see where things go in the future, as these things take time, but there are good reasons to be hopeful for DE Logos on low-powered machines!
This is a related project that allows running x86_64 on aarch64.
0 -
I am running into an issue with installing Logos in a Debian Buster container on my chromebook. I installed Logos using the portable appimage, copied over my Data, Documents and User folders to the installation. How do I deal with this?
0 -
Bill Anderson said:
I am running into an issue with installing Logos in a Debian Buster container on my chromebook. I installed Logos using the portable appimage, copied over my Data, Documents and User folders to the installation. How do I deal with this?
Could you tell me what steps you followed? with the complete path of these folders
I don't know if this is the case, but giving one second thought, I discovered one serious flaw with the current portable version: Wine always creates a new user corresponding to the local user, so if users between 2 different machines don't have the same name, this type of error can happen. Sorry, It will take a while to try one fix for this.
0 -
Daniel Ribeiro da Silva said:
Could you tell me what steps you followed? with the complete path of these folders
I don't know if this is the case, but giving one second thought, I discovered one serious flaw with the current portable version: Wine always creates a new user corresponding to the local user, so if users between 2 different machines don't have the same name, this type of error can happen. Sorry, It will take a while to try one fix for this.
I had this running perfectly until the latest Logos update. I used the folder hierarchy that the portable version created. I installed Logos and entered my username and password. When it got to the point where Logos asked me how much of my library I wanted to download, I exited. Then I deleted the Data, Documents and Users folders under LogosBible_Linux_portable\Logos dir and replaced them with my backups. I then launched Logos. When it opened, it immediately started to work on installing the latest version of Logos. That's when the box popped up.
Is the solution to try the regular appimage or Rik's wasta-wine?
0 -
Bill Anderson said:
I had this running perfectly until the latest Logos update. I used the folder hierarchy that the portable version created. I installed Logos and entered my username and password. When it got to the point where Logos asked me how much of my library I wanted to download, I exited. Then I deleted the Data, Documents and Users folders under LogosBible_Linux_portable\Logos dir and replaced them with my backups. I then launched Logos. When it opened, it immediately started to work on installing the latest version of Logos. That's when the box popped up.
Is the solution to try the regular appimage or Rik's wasta-wine?
Thanks. I will need more test with this version.
My local test, with the portable version, was this way: 1- created one new local user, 2- extracted the portable version on this new user (that have different username), 3- logged in and the synchronized, 4- used it for some time after the indexing. So I have to test the copy of the old installation folders now.
Using another solution isn't quite a solution. As all internal users of Wine are administrators (having full access to everything inside the bottle), this error has no solution for now. Then you can try what work better for you.
That said, I will always recommend, first, the installation done with the Rik's wasta-wine, because it's the proper way of doing it with some good support. But if you can do it yourself, then I will recommend the installation made with the native Wine from your linux distribution (because of the easy and regular updates). Only after that, I can recommend the installation script with the AppImage (because it's more like one workaround to avoid complications), and for the last I can recommend the Portable version (but now, without the reusing of old installation files, unless you know how to fix this kind of problem). You can feel free to use any solution you like, we will still help, no matter what you choose, we will only change the instructions that will be different.
0 -
This time the problem, on my side, is bigger: neither the version with Wine-Staging v4.21 nor v5.11 could update the version v8.14.0.0010 to version v8.15.0.0004 of LogosBible. And when I tried, I got all of my installations corrupted.
For now, I removed the portable version. And I will work on the installer for the LogosBible v8.15.0.0004.
I'm sorry, but it seems that something fundamental has changed in this LogosBible update. I would not be surprised if all installations made with Wine were unable to make this last update.0 -
@Daniel, My Logos has successfully updated from 8.14.0.0010 to 8.15.0.0004 with 5.11 wine-staging although it did have a couple of hiccups, e.g. re-downloading 3.5Gb of resources, and I think it had two attempts at downloading. So far, after light use, I've not noted any particular additional issues, but these may emerge as I use it more.
The process I used to install may be different from yours (on Debian Bullseye):connect to winehq packages; install winbind, winetricks, and cabextract.
these have evolved from the method at https://appdb.winehq.org/objectManager.php?sClass=version&iId=38306
I imagine you could use the latest Logos version from that page, now, instead of the one I have used.
$ WINEPREFIX=$HOME/wine-5.11-staging/ WINEARCH=win64 wineboot - cancel Wine Mono installation
$ WINEPREFIX=$HOME/wine-5.11-staging/ winetricks -q win10 dotnet48 corefonts fontsmooth=rgb
$ cp -R wine-5.11-staging/ wine-logos-5.11-staging (just to create a point to return to if it goes wrong)
$ WINEPREFIX=~/wine-logos-5.11-staging/ winecfg ~/wine-logos-5.11-staging/ (and set to Windows 10 as default)
$ WINEPREFIX=$HOME/wine-logos-5.11-staging/ msiexec /i ~/Downloads/8.10.0.0032-x64.msi
$ WINEPREFIX=$HOME/wine-logos-5.11-staging/ wine64 ~/wine-logos-5.11-staging/drive_c/users/nick/Local\ Settings/Application\ Data/Logos/Logos.exe
And I generally have a couple of issues (I haven't applied the rendering workaround):
+ Login Screen has artifacts that make it hard to see where to enter user data.
+ Indexing seems to run at 80% of CPU on my system - and much faster! With the notification of indexing just before it jumps to 75% And I don't think I noticed the blue bar on the Logos Setup window, extending across the screen as indexing completes. It seems to peak at 1.66Gb RAM. CPU drops at 6% then everything fluctuates wildly with RAM usage between 0.4 and 4Gb. Seems to get stuck at 6% complete It seems to finish at 448,508 Kb with 0% CPU but still only 6% indexed. -> 448,568 Kb
+ closed and opened. Didn't open. rebooted. Opened. Wanted to download 3.5Gb updates. Completed successfully, with various program upgrades.I've not tested it with the most recent wine-staging (5.13)
0 -
Nick said:
@Daniel, My Logos has successfully updated from 8.14.0.0010 to 8.15.0.0004 with 5.11 wine-staging although it did have a couple of hiccups, e.g. re-downloading 3.5Gb of resources, and I think it had two attempts at downloading. So far, after light use, I've not noted any particular additional issues, but these may emerge as I use it more.
The process I used to install may be different from yours (on Debian Bullseye):connect to winehq packages; install winbind, winetricks, and cabextract.
these have evolved from the method at https://appdb.winehq.org/objectManager.php?sClass=version&iId=38306
I imagine you could use the latest Logos version from that page, now, instead of the one I have used.
$ WINEPREFIX=$HOME/wine-5.11-staging/ WINEARCH=win64 wineboot - cancel Wine Mono installation
$ WINEPREFIX=$HOME/wine-5.11-staging/ winetricks -q win10 dotnet48 corefonts fontsmooth=rgb
$ cp -R wine-5.11-staging/ wine-logos-5.11-staging (just to create a point to return to if it goes wrong)
$ WINEPREFIX=~/wine-logos-5.11-staging/ winecfg ~/wine-logos-5.11-staging/ (and set to Windows 10 as default)
$ WINEPREFIX=$HOME/wine-logos-5.11-staging/ msiexec /i ~/Downloads/8.10.0.0032-x64.msi
$ WINEPREFIX=$HOME/wine-logos-5.11-staging/ wine64 ~/wine-logos-5.11-staging/drive_c/users/nick/Local\ Settings/Application\ Data/Logos/Logos.exe
And I generally have a couple of issues (I haven't applied the rendering workaround):
+ Login Screen has artifacts that make it hard to see where to enter user data.
+ Indexing seems to run at 80% of CPU on my system - and much faster! With the notification of indexing just before it jumps to 75% And I don't think I noticed the blue bar on the Logos Setup window, extending across the screen as indexing completes. It seems to peak at 1.66Gb RAM. CPU drops at 6% then everything fluctuates wildly with RAM usage between 0.4 and 4Gb. Seems to get stuck at 6% complete It seems to finish at 448,508 Kb with 0% CPU but still only 6% indexed. -> 448,568 Kb
+ closed and opened. Didn't open. rebooted. Opened. Wanted to download 3.5Gb updates. Completed successfully, with various program upgrades.I've not tested it with the most recent wine-staging (5.13)
Thanks, Nick.
The steps here are almost the same, but using the 32bits version (with the AppImage). Then I will start the migration to pure 64bits installation, with wine 5.11 or higher, now. Thanks again.
0 -
A Linux release would be one of the hapiest moments in my life. Sigh.
0 -
Trying it tonight on ElementaryOS 5.1. It has gone well and is downloading resources. I added three upvotes on winehq (now #13).
Many thanks to everyone working on this!0 -
Wine has improved quite bit over the years, a lot of software and even heavy duty games can now run under Linux.
"And you will know the truth, and the truth will set you free", John 8:32.
"你們必定認識真理，真理必定使你們自由", 約翰福音 8:3.0 -
I've finally had time to test the bash install script. I've added it to the guide on winehq. Thanks Daniel - well done for the great work!
I'd like to appeal again for people to vote on the winehq app db for Logos Bible Software. With 33 more votes (that's 11 people donating all 3 of their votes) we could climb the ladder to the next slot. It all helps get dev attention. Which we will need when Logos 9 arrives.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
I'd add votes if I knew where to do so... [hint hint]. Is this on the Wine forum, or Logos? Could you give us a URL so we don't have to go searching? Thanks!John Goodman said:I've finally had time to test the bash install script. I've added it to the guide on winehq. Thanks Daniel - well done for the great work!
I'd like to appeal again for people to vote on the winehq app db for Logos Bible Software. With 33 more votes (that's 11 people donating all 3 of their votes) we could climb the ladder to the next slot. It all helps get dev attention. Which we will need when Logos 9 arrives.
0 -
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
I clicked the link you provided and it took me to the WineHQ page for Logos. I logged in (yes, I have an account there), but I don't see anywhere to "vote" for anything... More help? Many thanks, in advance.John Goodman said:0 -
See right hand side of the page I linked when signed in.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
I checked Logos 8 in the vote box but didn't see how I could vote three times. Also, once I voted, the vote count didn't go up so I can't tell if my votes were successful. Maybe this has to do with casting earlier votes a few months ago.
0 -
Thanks. It was the oddest "vote" page I've seen... Three blank boxes that I can select labelled "No app selected". :-\ I selected the three boxes, clicked OK, and the votes climbed from 110 to 113, so it must have worked!John Goodman said:See right hand side of the page I linked when signed in.
0
