Linux version of Logos Bible Software
Comments
-
Once Logos is open I can choose from any of the layouts available, and it will open them no problem. However, whether I set it to open the last used layout, or even designate a particular layout for it to open to, it will not open to that layout. Still needs to be manually chosen after the program opens. Creating a brand new layout makes no difference unfortunately.
0 -
Greetings to all. I'm very excited with Logos 8 in my linux laptop. I have one issue that started a few days ago. Every time I open the library, the system crashes. Everything seems to work well except for the library. Any help would be greatly appreciated.
This is the file that I saved after it crashes. If I need to load any other log files, please let me know. I'm running Ubuntu 19.10. Many thanks!
Benjamin
0 -
The general belief is that the library database becomes corrupted sometime during the setup process and thus needs to be recreated. The simple solution is to rerun wasta-logos-setup after moving the library downloads out of the .wine-logos directory, then moving them back in after Logos is ready to be run from the application menu.
When I faced this issue, I was on Kubuntu 18.04; I attempted a reinstall but it failed. I upgraded to 19.10 and reinstalled and it worked flawlessly.
The directory you want is found at
~/.wine-logos/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/Data/
You can also move the Documents and User directories aside as well (also in the Logos directory) and move them back into place after the reinstall to save on additional downloads.
0 -
OK. Thanks for that. I'll give it a go tonight and let you know if it worked. Thank you!
Benjamin
0 -
Benjamin, you can also navigate to the directory that Taylor referenced. Rename the files located there to .bak and then try to run Logos. If it Logos reloads correctly it should rebuild the library files.
I had to manipulate a few of the directories like this during the download of my library. It is an old trick learned from Beta testing days
This could save you some work if the Library files are the problem
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
I thought that I'd give an update on the experience of using Logos on my Chromebook Pixelbook. I installed it within an Ubuntu Bionic container using the Chromebook's Linux feature and in crouton, which is an Ubuntu Bionic chroot environment running side by side ChromeOS. Previously posts in this thread have Google Docs explaining how to set up these installations.
Of the two, crouton is faster and I was able to get the launcher icons working. The installation also did not require me to add the i386 architecture before installing wasta-logos-setup like I had to for the container installation.
I had fits and starts with the container method simply because indexing would not finish no matter how long I left the computer running. In order for me to get around this, I used method 2 of installing Logos on multiple computers that you can access from the wiki. This took care of the indexing. The container method runs a little slower, but still works really well. I could not get the launcher icons to work though, and had to create a script to run Logos from the command line.
With both installations Logos will open up to a blank slate and I must select a layout to use.
I prefer the container method since it does not require me to put the Pixelbook in developer mode and bypass ChromeOS's built in security.
0 -
Useful update: LC_ALL=C can now be dropped from the launch command.
What it did was to address an issue where Logos got stuck in a loop endlessly generating a terminal message like '
0009:fixme:path:parse_url failed to parse...'This was an issue affecting many .NET applications not just Logos but appears to have been fixed in wine 4.18 (though it slipped under my radar). It would be helpful if others could try dropping it and let me know if you see any problems emerge.
A key benefit of dropping it is that you will no longer load to a blank layout but can select the layout of your choice! Enjoy.
Special thanks to Nick Andrewes who noticed the change;)
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
John, I dropped it from my launcher and so far so good! Opens to the correct layout instead of a blank layout. Haven't noticed anything out of place.
Having the layout load fixes one of the two things I was missing from Windows. Now if we could only get the Print function to recognize the printer and print.
Thankful for all of you who have puzzled this all together - I'm over a month without Windows, as Logos was the only program keeping it on my system - love it!
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
I dropped it from my shell script and it loads my layout! That's progress! I would love for the launcher to work, though.
Another question: What is involved in trying to get Logos installed within a Debian Stretch or Buster container as compared with the Ubuntu Bionic container I am running now? On Chromebooks, a Debian Stretch container is the default, but you can modify the sources.list file to switch it to Buster. I'm wondering if I would see improvement running this from Debian.
0 -
Bill,
IMHO, upstreaming to Debian would be ideal, however, as I'm sure you know, the current setup depends upon the Ubuntu PPA system. I am not a Debian packager, but if there are any here who are (or any who would like to learn to be one), I am sure that Rik would appreciate any effort to port. As it is, I think he probably has his hands full.
As wonderful of a target as Debian is, I think targeting Flatpak or an Appimage would also be wonderful. Personally, I use a lot of Snaps, but, again, that is a bit Ubuntu centric. If anyone has an interest in working on a Flatpak or Appimage, I'm sure that would also be greatly appreciated.
Adam
0 -
Adam,
Thanks for your comments. I'd help if I had packaging skills, but sadly I do not. I am a willing tester, though.
The reason I asked about Debian is that Chromebooks by default use Debian containers. You can use other distributions like Ubuntu, but I think the average, non-technical user wouldn't want to go through all of the extra steps to set it up. On the other hand, I am sure you could argue that anyone who uses the Linux containers on a Chromebook has a certain familiarity with using Linux.
I tried some hacks I googled to try to get the PPA working in a Debian container without success. I noticed on the Google Doc for wasta-logos that someone got this running on Arch and Manjaro. That's what got me wondering about Debian.
I have used Flatpaks in both my Debian and Ubuntu containers, so I know those would work. Unfortunately, Snaps do not work because the containers rely on Wayland.
0 -
You can use debian fairly easily now. Since Louis' patch made it into winehq-staging 4.21. If you install that package, you should be good to go. Just follow the guide as if building from src but don't build from src use the winehq package.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Frank Sauer said:
Having the layout load fixes one of the two things I was missing from Windows. Now if we could only get the Print function to recognize the printer and print.
I'm hopeful about getting print to work but I'm focusing on videos and speech at the moment. The print system in use seems to be using gdi plus which can be installed by winetricks (might work with a native dll override?). As a work around you can copy and paste or save word docs etc from the print/export dialogue and then print from libreoffice.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
This is my Debian "how to". My running Logos has not yet been tested as to what works and doesn't. But a lot certainly seems to. What follows may need filling out, so feel free to ask any questions.
Many thanks for everyone's hard work.
======================================
I had previously enabled multi-arch on an amd64 system:
# dpkg --add-architecture i386
# aptitude updateDownload and install the winehq repository key:
$ wget -nc https://dl.winehq.org/wine-builds/winehq.key
$ sudo apt-key add winehq.key/etc/apt/sources.list:
deb [arch=amd64,i386] http://ftp.uk.debian.org/debian/ buster main non-free contrib
deb-src [arch=amd64,i386] http://ftp.uk.debian.org/debian/ buster main non-free contribdeb [arch=amd64,i386] http://security.debian.org/ buster/updates main contrib non-free
deb-src [arch=amd64,i386] http://security.debian.org/ buster/updates main contrib non-freedeb [arch=amd64,i386] http://ftp.uk.debian.org/debian/ bullseye main contrib non-free
deb-src [arch=amd64,i386] http://ftp.uk.debian.org/debian/ bullseye main contrib non-free#Wine
deb [arch=amd64,i386] http://dl.winehq.org/wine-builds/debian/ bullseye main# aptitude update
wine-staging installed at version 4.21~bullseye
winetricks installed at version 0.0+20190912-1
winbind installed at version 2:4.11.1+dfsg-3 (relates to an error on a previous installation attempt, and this was a possible solution)
cabextract installed at version 1.9-2+b1Set up 64 bit wine bottle:
$ WINEPREFIX=$HOME/wine-logos8/ WINEARCH=win64 wineboot
click "Cancel" to avoid installation of Mono (don't recall it asking about Gecko)
install dotNet:
$ WINEPREFIX=$HOME/wine-logos8/ winetricks -q dotnet472
install Core Fonts:
$ WINEPREFIX=$HOME/wine-logos8/ winetricks -q corefonts
enable font smoothing:
$ WINEPREFIX=$HOME/wine-logos8/ winetricks settings fontsmooth=rgb
enable gdi fix:
WINEPREFIX=$HOME/wine-logos8/winetricks ddr=gdi
run Logos x64:
$ WINEPREFIX=$HOME/wine-logos8/ msiexec /i /path/to/Logos/Installer/Logos-x64.msi
run Logos
$ WINEPREFIX=$HOME/wine-logos8/ wine64 $HOME/wine-logos8/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/Logos.exe LC_ALL=C
crash. Then goes to a blank sign in screen, but just enough visible to sign in.
"Download your Logos 8 Library"
"Downloading resources". 100% of 12Gb download
"Preparing Library"
"Indexing"
(Edited 5/12/2019 to include gdi fix from John Goodman, instructions for winehq repository key, multi-arch)======================================
0 -
Insert this step after fonstmooth one.
Possibly you can just run
WINEPREFIX=$HOME/wine-logos8/winetricks ddr=gdi
otherwise
WINEPREFIX=$HOME/wine-logos8/ winetricks settings
tick drr=gdi
ok
will fix black boxes.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
John Goodman said:
You can use debian fairly easily now. Since Louis' patch made it into winehq-staging 4.21. If you install that package, you should be good to go. Just follow the guide as if building from src but don't build from src use the winehq package.
John, can you provide a little more specific detail on your suggestion? Where do I get winehq-staging? And what steps of the guide as if building from source do I follow? Sorry that I am not more proficient in Linux.
0 -
Bill Anderson said:John Goodman said:
You can use debian fairly easily now. Since Louis' patch made it into winehq-staging 4.21. If you install that package, you should be good to go. Just follow the guide as if building from src but don't build from src use the winehq package.
John, can you provide a little more specific detail on your suggestion? Where do I get winehq-staging? And what steps of the guide as if building from source do I follow? Sorry that I am not more proficient in Linux.
So I modified my sources.list to include Nick's sources (sans UK mirrors) and installed the wine key. After that, I could install winehq-staging. After that, I downloaded wasta-logos-setup and than ran it, and now Logos is installing as we speak.
0 -
Bill Anderson said:
After that, I could install winehq-staging. After that, I downloaded wasta-logos-setup and than ran it, and now Logos is installing as we speak.
Just a quick question, Bill:
Did you need to install wasta-logos-setup? If so, why?
I DIDN'T do so under debian in the instructions above, and results that are not at all bad . . .My suspicion (which may be wrong) is that you might have a problem with an incorrect libjpeg using wasta-* (I did, but other things have changed in my system since then)
0 -
Nick said:
Did you need to install wasta-logos-setup? If so, why?
No you don't, your instructions do everything that it does except setting drr=gdi with winetricks.
It's a bad idea because wasta-logos-setup is designed for ubuntu, can't be sure if it will work.
I recommend to use Nick's instructions but do set drr=gdi otherwise you will most likely get graphical glitching. (Possibly some graphics cards / drivers will not need this)
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Thanks. Instructions updated!
0 -
Following Nick's instructions went OK until I installed dot.net. It looked like it didn't complete after a very long time but when I exited out and reran the command to install it, it said it was installed.
Then, when I tried to install the Logos msi it didn't seem to do anything. It was very quick. Here's what I got:
WINEPREFIX=$HOME/wine-logos8/ msiexec /i /path/to/Logos/Installer/Logos-x64.msi
000b:fixme:winediag:start_process Wine Staging 4.21 is a testing version containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.Then, when I issued the run Logos command, I received back this:
WINEPREFIX=$HOME/wine-logos8/ wine64 $HOME/wine-logos8/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/Logos.exe LC_ALL=C
wine: cannot find '/home/wmadan/wine-logos8/drive_c/users/wmadan/Local Settings/Application Data/Logos/Logos.exe'0 -
Bill, stupid question, in the first instance, but you did make the path in bold below local to your own system (sorry if my notes were confusing):
WINEPREFIX=$HOME/wine-logos8/ msiexec /i /path/to/Logos/Installer/Logos-x64.msiAll the best.
Nick
PS My dotnet install took a long time - it must have installed a few versions including the final one. Going from memory, there were a couple of points where I could see a script hadn't finished, but when I pressed "Enter" the script seemed to return me to the prompt. I can't quite remember at what point that happened - it may have been a previous install.
0 -
Nick,
Duh! Thank you. But, where is the .msi stored? I can't find it. Was it installed with dot.net or winehq-staging? Do I have to manually get it from the Faithlife website?
0 -
The most up to date links to the msi are in the build from src section of the google doc. I updated them yesterday.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Bill, yes, you have to download the .msi file from the Logos website. And then replace the bit of the path in bold above to that link.
wget https://downloads.logoscdn.com/LBS8/Installer/8.8.0.0046/Logos-x64.msi
I don't seem able to update my "how to" any more.
Many Thanks
Nick
0 -
I got it running, finally. Thanks for everyone's patience with me.
But, the Debian container runs slower than the Ubuntu container, so it's back to that one for me.
0 -
How hard can it be? No, seriously! If we can get an Android and Mac version then why not Linux? Logos is the only reason I have to keep any one of my computers booting into Windoze. Now there is a workable online version I might ditch that as it's Windoze 7 and Logos say they will no longer support this. Well, I'm not wasting money on getting another version of Windoze but I would rather have the full functionality of an installed version.
0 -
Bill
Bill Anderson said:But, the Debian container runs slower than the Ubuntu container, so it's back to that one for me.
I don't believe my "how to" involves a container.
I've not yet got to grips with the indexing. That lengthy process might be slowing it down.
There's also a possible question over the whether the "path:parse_url failed to parse L" errors in the terminal slow things down, which I think John has mentioned: i.e. whether running Logos without LC_ALL=C at the end slows things down. I don't know too much about this aspect of things. He might have an opinion.
0 -
Andrew J. Allcock said:
How hard can it be? No, seriously! If we can get an Android and Mac version then why not Linux? Logos is the only reason I have to keep any one of my computers booting into Windoze. Now there is a workable online version I might ditch that as it's Windoze 7 and Logos say they will no longer support this. Well, I'm not wasting money on getting another version of Windoze but I would rather have the full functionality of an installed version.
Great question! Part of the answer is very hard and very time consuming. A 'native' linux version would require a massive effort based on what we know of the way Logos is coded and what we've been told. It was coded for Windows using .net and wpf. Wpf is not very portable at all. The mac version was therefore a substantial and costly effort for faithlife. Bob has talked about this and in fact indicated that with hindsight wpf turned out to be an unfortunate choice. That I think shows a real strength of character and in fairness, how could he have known at the time? With it, they have created a Bible package that is IMHO vastly superior to every other!
Faithlife have been helpful and permissive in letting us work as a community towards the wine solution. Bob encouraged it in a forum post. They have answered questions that have helped us solve some significant problems. E.g. which frameworks are used for which feature and indeed given permission for packaging the msi installer with the wasta package.
A lot of the discussion here is from people who are trying to push the boundaries even further. E.g. other distributions, linux containers on chromebooks etc. Which is brilliant! If you want to run Logos on ubuntu with the wasta package then I can confirm it works almost flawlessly for weeks without crashing etc. There are few limitations, no in app playback of video or audiobooks. Pronunciation audio works. You can't print directly but you can save a word doc and print from libreoffice. System Narrator reading also doesn't work but again you could work around that using a web browser or exported. I have used it extensively to study for my last and next sermon series.
There have been some interesting comments on the forum about it being relatively easy with wine... it was not! Several of us spent a lot of time over a few years testing, submitting bug reports and gathering information to get us here. Loius Lenders has written 3 patches etc. At times, a seemingly simple option or config choice required many experiments with solutions that didn't work to get us there. Rik put a lot of work into packaging etc. There is much ongoing work - regressions happen, one has been corrected and we have others upstream that need fixing. When Logos 32bit is no longer available we will need 64bit to be stable (it isn't yet). If Logos drops .net 4.7.2 and jumps to 5 etc again we may be stuck for a while.
All that said, another take on the question is that now, it could be very easy. The windows version is so close to perfect on Linux already that we may well get there very soon. In day to day use it seems to perform better on my older hardware than the mac version does on my newer hardware. That's subjective but certainly my impression.
Looking ahead, .NET 5 is open source and intended to be more portable. Cross platform wpf alternatives already exist with high compatibility. Microsoft are encouraging and making it easier to port wpf code to work with .NET core. Work on media foundation for wine and .NET is well resourced and ongoing. These things may converge in a way that helps us continue to enjoy the benefits of Logos on Linux. They may even get to the point where it is possible for faithlife to build the src against wine libs and go fully native. Genuinely we might be just a couple of registry keys away from fixing the biggest remaining bugs. We will need to be vigilant in testing for and reporting regressions.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Nick said:
Bill
Bill Anderson said:But, the Debian container runs slower than the Ubuntu container, so it's back to that one for me.
I don't believe my "how to" involves a container.
My use case is running Logos on a Pixelbook (Chromebook). Google introduced the beta feature "Crostini" in the last year that runs Linux in an LXD container. The default is a Debian container. I got Logos running acceptably within an Ubuntu bionic container because that's what this solution was targeted to originally. I wanted to see if I could get it running under the default Debian container, thinking that most users of Chromebooks who wanted to do this might not want to go through the extra steps to replace the Debian container with an Ubuntu one.
0
