Linux version of Logos Bible Software
Comments
-
Try installing winehq-devel or winehq-staging, will one of them install?
Best
David
0 -
Was feeling pretty good about myself having gotten wine installed on Chromebook (following the Debian instructions), and the wasta-logos-setup repository installed by editing the sources file switching from eoan to disco. Now when I run the wasta-logos-setup, I can't get past the need for user authentication to patch the wine file because there is no password, and it won't run with root permissions. My attempt to run it fails with "Error executing command as another user: Not authorized" Thoughts?
0 -
Got it! Added a password with
sudo passwd [username]
Then ran this command to smooth out the authentication process:
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
0 -
Alan,
Since you are on a chromebook, as I am, perhaps you can help me. Trying to piece together your posts, I am unclear on how you started. Did you start with the standard stretch container, or did you create an Ubuntu container? Then, when you say that you followed the stretch instructions to install wine, how did you do that if you were running an Ubuntu container?
0 -
Bill,
I'm not sure about the container? I activated GPU acceleration in about:flags, then activated the Linux (Beta) option in the settings menu. Then, I added the logos installer repository via the Google doc above. Oh, I had to install software-properties-common first to do that. Then I installed nano to edit files, then I edited /etc/apt/sources.list.d/wasta-linux-ubuntu-logos-eoan.list with nano, changing both instances of eoan to disco, then running another sudo apt update. Then I had to run a command to redownload the key since I changed the repository:
sudo apt update 2>&1 1>/dev/null | sed -ne 's/.*NO_PUBKEY //p' | while read key; do if ! [[ ${keys[*]} =~ "$key" ]]; then sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys "$key"; keys+=("$key"); fi; doneThen I installed wine via the Debian stretch instructions. I also had installed the cybermax-dexter repository mentioned above in an attempt to get the other wine instructions to work, so I don't know whether that step was really needed or not.
After that, I installed the wasta-logos-setup program with apt install. I ran into the issues with the authentication, so I installed policykit-1-gnome, did the sudo passwd [username] and /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
After running that, it seems to sit in space, so hit enter and it'll pull back to the prompt. Then I tried to run wasta-logos-setup, finally got it to run, and it just kinda skipped over the .net installation. So, I installed winetricks via instructions here: https://wiki.winehq.org/Winetricks
I'm currently waiting through the manual installation of .NET 4.7.2 to see if it works now. I did have to install cabextract to get the winetricks .net installation to work, so I wonder if I had installed that first, if the wasta-logos-setup script would have worked properly. I'll let you know if I get anywhere.
0 -
Note: I have a Dell Inspiron 14 Chromebook, which is one of the ones that you can turn GPU acceleration on for. Given how much Logos uses the video card, I'm guessing you wouldn't want to do this on a Chromebook without that ability (i.e. the Pixelbook, Dell Inspiron, some of the newer Chromeboxes, etc.)
0 -
Bill, Alan, others,
As you may be seeing, I only run Ubuntu LTS releases but did at least build wasta-logos-setup for disco as well since John and a few others were using it. So there are some things you are running into that I don't see but would be able to incorporate fixes for if it isn't too hard / too manual and can be integrated in the package. I could add a dependency on polkit, for example (yes the prompt it makes in wasta-logos-setup is IF it determines your wine isn't patched yet, then it re-runs the wasta-logos-setup postinst script which is where the wine patching happens: since this requires root level access it needs to get authenticated).
Alan, regarding getting winehq-devel installed, using "dpkg -i" isn't a great option because dpkg won't automatically download and install dependencies. To have dependencies installed, you need apt or gdebi (if you have a local .deb).
Note that the difference between wine-devel and winehq-devel is that winehq-devel will make sure the symlinks are made between /opt/wine-devel and /usr/bin. Without those links, your system doesn't know where wine is and you need to call the explicit path to /opt/... to execute wine, which wasta-logos-setup doesn't assume.
Anyway, good luck to everyone! Thanks to all for the help so far. The solution of the graphical glitching by setting ddr=gdi was the real key: thanks to John (I think?) for that one!
I will be posting an update to the SIL International Linux User List encouraging them to try it, so we may see some other testers coming on board soon. There is an International Bible Translation Conference this coming week in Dallas so good timing to promote Linux and Logos on Linux! :-)
Rik
0 -
Alan Gerling said:
Bill,
I'm not sure about the container?
If all you did was activate Linux (Beta) on your chromebook, then you would be running Debian Stretch in your Linux container. You can replace the default Debian Stretch container with Ubuntu, but it doesn't sound to me like you did that. I will reset Linux on my Pixelbook and that will get me back to Stretch. I will try to install wine from there.
0 -
So, I am going to give up for the moment trying to install this on my Pixelbook in Crostini. I want to see if I can install it in VM first and then learn from that.
I have a Bionic VM in a Windows host. I got through all of the steps successfully and then ran wasta-logos-setup. Things went OK until I encountered this error:
0 -
Bill,
It seems that the .NET install somehow didn't finish correctly. If you are able can you try wasta-logos-setup again? The .NET install should finish before you are prompted for the Logos installation file, that is why I am a bit confused.
Sorry I haven't seen this failure before, but I think you are getting close!
Rik
0 -
I got through all of the scripts, and it looked like Logos installed, but then I just get a slew of file and path missing errors when I try to launch it.
0 -
A chromebook install is likely to be more complicated. I have problems running common linux apps on a chromebook such as libreoffice, musescore, gimp etc. Many get bundled in in flatpaks with 'hacks' already applied. I'm thinking it can probably be done but will require specific expertise.
Bill your dotnet install has not worked. If you go back to the google doc and find the installing dotnet bit of the build from src guide you should be able to see the appropriate command to install it. Running the command yourself rather than from the script might show the error message. I think it is most likely to be due to having the wrong version of wine installed or some such. Check steps 1 & 2 carefully noting the difference between wine-devel and winehq-devel. Hope that helps.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
The feedback from those trying to get things working is very helpful. Sorry you all are having problems, but thank you for posting them here! This is the only way we will get things smoothed out. Ultimately, I think we're going to get this pretty smooth, but it's still early days.
Until I made a certain change, I never could get Logos running properly on Linux. I always got errors regarding indexing, and searching never worked properly for me. The effect of this was to pretty much make Logos on Linux unusable for me. However, by making the following change, everything is now working close to flawless for me. Here's what I did.
- First, I started with a fresh installation as outlined on the Google Docs page. The important thing to note is that I stopped after completing step 4 and did something different.
- After completing step 4 and successfully installing Logos, I changed the .wine-logos prefix from its default settings of Windows 7 to XP. Here's how to do that.
- Open a terminal in your home directory and run: WINEPREFIX="/home/your-user-name/.wine-logos" winecfg
- Set "Windows Version" to XP (N.B. you cannot change the prefix to XP before the installer is finished, because the installer will not work if it things you are on XP.)
- Now run Logos for the first time by either using the menu entry or running: WINEPREFIX=$HOME/.wine-logos/ wine $HOME/.wine-logos/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/Logos.exe LC_ALL=C
After changing from Windows 7 to XP, I had none of the terminal errors I previously received. Moreover, I did not get the popup that said the Logos indexer failed.
However, none of my searches on the text yielded results until the indexer finished and it took a VERY long time to finish. Either I forgot how long it took on Windows or indexing is slower on Linux. Not sure which, but you might as well try this at night and then wake up the next day and check the results. Maybe I just have a large library or something.
Setting to XP was John's suggestion BTW, and it worked out. Thanks John! He suggested that it might be related to this bug.
Also, I do not know the status of sound before I switched to XP (I didn't even try it), but after changing to XP sound worked just fine.
Rik, if this change proves useful to running Logos under Linux, I think incorporating it into the installer might be useful.
0 -
-
I have not yet tried the method described above with the wine prefix set to 64bit. The default for the wasta installer is 32bit. However, I am going to test setting the prefix to 64bit and will report the results.
0 -
Bill your problem is that the wine Windows Version is set too low for the Logos Installer. Not sure how that happened. I think you'll find it is set to winxp but you need min 7 for Logos to install. It might be you have to set it back to winxp for indexing to complete according to one bug report but we don't have that confirmed. This is something wine devs are likely to iron out soon. You change the windows version using winecfg.
WINEPREFIX=$HOME/.wine-logos/ winecfg
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
John Goodman said:
Bill your problem is that the wine Windows Version is set too low for the Logos Installer. Not sure how that happened. I think you'll find it is set to winxp but you need min 7 for Logos to install. It might be you have to set it back to winxp for indexing to complete according to one bug report but we don't have that confirmed. This is something wine devs are likely to iron out soon. You change the windows version using winecfg.
WINEPREFIX=$HOME/.wine-logos/ winecfg
The winetricks scripts that install .NET change the Windows Version back and forth for various compatibility patches while getting the different parts of .NET installed. At some points it even sets it to Windows 2003 if I recall correctly. Anyway, if the .NET install part didn't succeed, then it could be that it was set to winxp when it failed. Anyway, John is right that using winecfg is the gui way to change the Windows version. Alternatively you can change it with a winetrick like this:
WINEPREFIX=$HOME/.wine-logos/ winetricks win7
(or winxp for setting to XP)
Regarding the need of whether or not we should use win7 or winxp, wasta-logos-setup can set it to whatever we prefer. So far, I don't see much difference. I think my indexing all completed using win7?? So if we want winxp, the wasta-logos-setup script could set to win7 for the Logos install, then set to winxp after the install.
0 -
John Goodman said:
A chromebook install is likely to be more complicated. I have problems running common linux apps on a chromebook such as libreoffice, musescore, gimp etc. Many get bundled in in flatpaks with 'hacks' already applied. I'm thinking it can probably be done but will require specific expertise.
Bill your dotnet install has not worked. If you go back to the google doc and find the installing dotnet bit of the build from src guide you should be able to see the appropriate command to install it. Running the command yourself rather than from the script might show the error message. I think it is most likely to be due to having the wrong version of wine installed or some such. Check steps 1 & 2 carefully noting the difference between wine-devel and winehq-devel. Hope that helps.
John, my Windows version in winecfg was set to Windows 7, not XP, so this is not the reason dotnet didn't install. I will go back and try to install it from source as you suggested, and will report back.
0 -
Bill, try it. I think you’ll find I’m right I’ve had the same error messages.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
To clarify, the Logos installer is incorrectly assessing the presence of .net so far as I can tell. This is because of the windows version setting. You want win7 to run the logos installer and winxp to run logos. The setting should not make a difference except to apps that explicitly check for it. This is not entirely true with .net due to a bug. Which is why although Logos doesn't check the windows version once installed you are less likely to see crashes once set to winxp.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Rik Shaw said:
The winetricks scripts that install .NET change the Windows Version back and forth for various compatibility patches while getting the different parts of .NET installed. At some points it even sets it to Windows 2003 if I recall correctly. Anyway, if the .NET install part didn't succeed, then it could be that it was set to winxp when it failed. Anyway, John is right that using winecfg is the gui way to change the Windows version. Alternatively you can change it with a winetrick like this:
WINEPREFIX=$HOME/.wine-logos/ winetricks win7
(or winxp for setting to XP)
Regarding the need of whether or not we should use win7 or winxp, wasta-logos-setup can set it to whatever we prefer. So far, I don't see much difference. I think my indexing all completed using win7?? So if we want winxp, the wasta-logos-setup script could set to win7 for the Logos install, then set to winxp after the install.
Rik
Might be a good idea to try setting it to 7 in the installer, and then to XP for running Logos.
Adam
0 -
J. Erik said:
Giving it a go on Manjaro with 64 bit wine...
J.Erik, did the Installation work with manjaro? Would be great!
0 -
This thread has really become exciting for me..... Logos is the only reason I haven't wiped my SSD and gone with a straight Linux (likely Mint) build.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
I'm getting the same .NET error when trying to install on a fresh Kubuntu LTS
Update - wound up getting it installed currently on Step 3 of 4 in Logos. There was an error that I forgot to record and once I installed what the error said was missing, everything ran perfectly
Update II - Running pretty well - seems like the Indexer is not working. Stays at 0% and I left it running for more than a few hours already. Still running and did not crash - winecfg is set to XP
Bill Anderson said:So, I am going to give up for the moment trying to install this on my Pixelbook in Crostini. I want to see if I can install it in VM first and then learn from that.
I have a Bionic VM in a Windows host. I got through all of the steps successfully and then ran wasta-logos-setup. Things went OK until I encountered this error:
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Oh happy day! Thanks a lot to Rik, John and all linux-freaks out there. I tried to install logos at LinuxMint 19.2 (ubuntu 18.4 LTS) on a really old Notebook (Sony Vaio NW21) and a quite new desktop. Both worked without any bug! Now both machines are indexing, but I can already work with it. The performance of the Vaio is poor, but I dont mind. With win 10 it would be the same or even worse. Maybe one day you guys could create a package for the AUR and logos will run under manjaro/arch. But so long I will happily switch to Mint/Ubuntu.
0 -
I would have loved to escape from Windows as well, but it's also Software like Logos that are holding me back.
There seems to be no escape from Windows Bloatware even the most powerful machines eventually grind to a halt after the so many updates.
LBS doesn't care much better I must say it's memory and CPU power requirements and management or not the best.
What a combination Windows and LBS, it's just that finding software with the features that LBS has is impossible
0 -
I have found that with a bigger library the indexer can report 0% but in fact is indexing and eventually it will complete. I'm not sure if it is faster or slower than in windows. If you have near 10k resources expect to leave indexing over night. With Logos Basic it takes maybe an hour or two.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
I believe you are indeed correct. Though the indexer stayed at zero, it appeared to have finished. Just in case I ran the Rebuild Index command and the indexer moved up to 11% then stalled, but finished without going beyond 11%.
I really can't comment on the efficiency versus Windows, as it would be an apples to oranges comparison. I run Windows on an SSD and pulled that out and replaced it with a HDD. It's been a long time since I have run a HDD, but indexing and running Layouts with many resources open was brutal in Windows even with a quad core i7. (SSD equated a ridiculous performance enhancement in indexing and performance)
Now that everything is fully downloaded and indexed, this is amazing to use - I never use the Read Aloud function on my laptop, the media rarely - so the printing bug is the one that would hinder me a little.
Very thankful for the team that has gotten this done! Windows may soon be left behind and the Linux system moved to a SSD
John Goodman said:I have found that with a bigger library the indexer can report 0% but in fact is indexing and eventually it will complete. I'm not sure if it is faster or slower than in windows. If you have near 10k resources expect to leave indexing over night. With Logos Basic it takes maybe an hour or two.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
I found a BUG: In the sermon editor I can't create an entry in the reference-box and in the subjet-box. When I type a reference (eg. John 3:16), nothing happens. There should be a choice of some references. I will add this bug to the google doc, ok?
0 -
Dirk Kellner said:
I found a BUG: In the sermon editor I can't create an entry in the reference-box and in the subjet-box. When I type a reference (eg. John 3:16), nothing happens. There should be a choice of some references. I will add this bug to the google doc, ok?
Have you verified that this bug presently occurs only on Linux?
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0
Giving it a go on Manjaro with 64 bit wine...
