Linux version of Logos Bible Software
Comments
-
Hi!
If there is more people like me that have a linux pure 64bits (no-multilib) and want to run Logos 32bits, there is a good solution. I don't like to install all multilib things just for the sake of one application (wine), then I created a AppImage that have almost all 32bits libs that wine need to work on all 64bits linux distributions. I also created instructions for the Logos Bible instalation: https://github.com/ferion11/Wine_Appimage/wiki/Logos-Bible
* The last "8.10.0.0032" version fixed the "outofmemoryexception" for me. And it's working now
0 -
Tried voting (twice actually). It was at 19 when I voted, and remained 19 afterward even after refreshing the browser. Maybe it takes a while for the votes to be counted? Hope we can keep getting votes. For others interested in voting, you must register an account first.
John Goodman said:Folks can I request that you log on to winehq appdb and go to the page for Logos 8 https://appdb.winehq.org/objectManager.php?sClass=version&iId=38306
Once there please vote for it! This may help encourage developer attention etc.
Many thanks
0 -
Very interesting! Is it possible to wrap everything up into one AppImage file? Possibly with the installation step already done so that the user would just have to login to their account and then their files would be downloaded and indexed?
Daniel Ribeiro da Silva said:
Hi!
If there is more people like me that have a linux pure 64bits (no-multilib) and want to run Logos 32bits, there is a good solution. I don't like to install all multilib things just for the sake of one application (wine), then I created a AppImage that have almost all 32bits libs that wine need to work on all 64bits linux distributions. I also created instructions for the Logos Bible instalation: https://github.com/ferion11/Wine_Appimage/wiki/Logos-Bible
* The last "8.10.0.0032" version fixed the "outofmemoryexception" for me. And it's working now0 -
It's possible, but the version of Logos Bible would be fixed (not good for updates), because the inside of AppImage is read-only.
0 -
When you vote, make sure you tick one of the three check boxes when it asks what application you want to replace. I tried just submitting first, because I had no applications chosen, but the vote did not take. I clicked vote again and clicked one of the check boxes and then submit - the vote immediately registered.
I did it twice more, for a total of three new votes - we are at 22 now
aaylnx said:Tried voting (twice actually). It was at 19 when I voted, and remained 19 afterward even after refreshing the browser. Maybe it takes a while for the votes to be counted? Hope we can keep getting votes. For others interested in voting, you must register an account first.
John Goodman said:Folks can I request that you log on to winehq appdb and go to the page for Logos 8 https://appdb.winehq.org/objectManager.php?sClass=version&iId=38306
Once there please vote for it! This may help encourage developer attention etc.
Many thanks
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Got it. That worked. Thanks! We're up to 23 now.
Frank Sauer said:When you vote, make sure you tick one of the three check boxes when it asks what application you want to replace. I tried just submitting first, because I had no applications chosen, but the vote did not take. I clicked vote again and clicked one of the check boxes and then submit - the vote immediately registered.
I did it twice more, for a total of three new votes - we are at 22 now
aaylnx said:Tried voting (twice actually). It was at 19 when I voted, and remained 19 afterward even after refreshing the browser. Maybe it takes a while for the votes to be counted? Hope we can keep getting votes. For others interested in voting, you must register an account first.
John Goodman said:Folks can I request that you log on to winehq appdb and go to the page for Logos 8 https://appdb.winehq.org/objectManager.php?sClass=version&iId=38306
Once there please vote for it! This may help encourage developer attention etc.
Many thanks
0 -
Interesting. Yes, I had forgotten about AppImages being read-only. It totally makes sense that they are read-only from a security perspective, but not helpful to us in this instance. I don't know how the app would be able to download all of the files from the website either.
BTW, I have been able to successfully spin up this whole mess on a LXC/LXD container on Ubuntu. The LXC container should work on other distros too, I just like the way LXD provides a very nice rest api for working with LXC containers. I keep meaning to provide instructions on how to do this on the Google Doc. I will get around to it one day. Also, I see no reason why the base container could not be shared. By base container I mean everything installed but not yet logged into. You'd have to have your own Logos account to log into it and run it. This kind of approach would not be as newbie friendly as having an Appimage (or Snap or Flatpak), but it does solve the portability issue as well as the library issue.
Daniel Ribeiro da Silva said:It's possible, but the version of Logos Bible would be fixed (not good for updates), because the inside of AppImage is read-only.
0 -
I don't have tested. But for the video play, you will need on linux all gstreamer codecs installed (if using wine 32bits, you need all the 32bits versions), include gst-libav and the ffmpeg (or libav). On wine side (with winetricks) you will need win7 profile, directmusic, directplay, directshow, xvid and ogg. It's a lot of work just to see videos. I'm happy with only the audio/video don't working for now. You can see on wine database site that almost all audio/video apps players also don't work, it isn't just a Logos Bible Software problem. When the wine devs solve for the others apps, then the Logos Bible will start to play videos too.
0 -
@Bill: Whoops, I dint read the ubuntu guide fully. It seems that I have to update wine 4.0.3 manually to Wine 4.21...
According to @John, Wine-staging (now Wine 5.0 rc2) should work too:
John Goodman said:Yeah - wine 5.0 rc 2 does not have ReOpenFile() implementation. You need to install the wine-staging version of wine if you want it to work. Most of what the wasta package does apart from install a patched version of wine is configuring your wine prefix. Installing .net etc. If that was all done already you can use wine-staging without wasta. But if you went with wine-stable or wine-devel you won't find it can work.
0 -
Only the "Staging version" of wine from 4.21. The Wine 5.0 rc2 normal version (Stable or Development) don't work, have to be the "Staging version". Or you will have to apply the patch yourself.
0 -
John Goodman said:
Folks can I request that you log on to winehq appdb and go to the page for Logos 8 https://appdb.winehq.org/objectManager.php?sClass=version&iId=38306
Once there please vote for it! This may help encourage developer attention etc.
Many thanks
Ok we are on the top 100 list. I want us to be in the top 25, ideally ahead of the watchtower library app;) Can we have 100 votes people?! It will only take you a few minutes and we really need dev attention to get the indexing fixed for 64bit and win 10 support!
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
So, Logos works with Wine-staging 4.21 works, but does anybody know if Logos works with Wine-staging 5.0 rc2 too? Is it safe to go further with step 2b on an Mint 19.3-64b with Kernel 5.0.0.37.40 and wine-staging 5.0rc2?
Or is it better 1) to uninstall Wine-staging 5.0 rc2 completely and 2) redo everything by the Ubuntu guide and (finally) start following the 'How to - Building from source'?
BTW, is it possible to update / to 'clean up' the Ubuntu guide? Because right now (24/12) it uses several different versions of Logos, Wine and etc. Maybe add an clearer 'How to' for installing Wine 4.21...
0 -
Ollie Pindakaas: The Wine-staging 5.0 rc2 work, but the Wine-developer 5.0 rc2 don't. The "Staging" in the name is used for patchs that wine devs can't accept (at least for now, or for ever in some cases). I feel your pain, and because of this that I put the option of AppImage of wine LINK HERE. Is so more clean, that is made to use on a no-multilib installation (without 32bits libs), and it run wine 32bits very well.
0 -
Daniel Ribeiro da Silva said:
The Wine-staging 5.0 rc2 work, but the Wine-developer 5.0 rc2 don't.
So, I can safely go further with step 2b of the 'How to - Install Logos on Linux' on an Mint 19.3-64b with Kernel 5.0.0.37.40 and wine-staging 5.0rc2?
Thanks again for your Git, but because you write about Arch Linux and I just started to understand Linux and Mint 19.3 (came from W10-64b), I dont feel confident enough to tweak around/translate everything 'back' to Mint 19.3.
"HU, what about your posts about Wine 5.0 rc2?" Jeb, I just tried to update Wine 4.0.3 to Wine 4.21...
Confused? Me too...0 -
Ollie Pindakaas: The "Arch Linux" is because the AppImage have a installation of "Arch Linux" inside, but can be used in any distribution (you will be fine when you start to use more AppImages).
The wine devs have a separated fork just for test patchs. Then the "Wine 5.0 rc2" (don't have the patch) is one, and the "Wine-staging 5.0 rc2" (have the patch) is other fork. The same for the "Wine 4.21" (don't have the patch) that is one, and "Wine-staging 4.21" (have the patch) is other.
If you run the "winecfg", the "staging" version will have a extra tab. More info HERE.
The main steps are:
1- Install the Wine-staging version 4.21 or higher.
2- Install the winetricks packages (fonts, dotnet, ddr=gdi ...)
3- Install The Logos
0 -
For none ubuntu systems. Follow the winehq installation guide. Avoid 64bit wine. You can use 32bit wine on a 64bit system. 64bit wine is not compatible enough for indexing to complete. For a usable system you need to choose 32bit. If folks install the 32bit version of wine-staging 4.21 or above best to go for 5.0rc2 and have the latest winetricks setting up a wine prefix is as easy as:
winetricks arch=32 prefix=$HOME/ .wine-logos -q dotnet472 corefonts ddr=gdi fontsmooth=rgb win7
Some older versions of winetricks don't respect the prefix setting so you can delete that. It will build it under $HOME/.wine and you can rename it afterwards.
winetricks arch=32 -q dotnet472 corefonts ddr=gdi fontsmooth=rgb win7
After installing the msi before you run Logos and sign in, you should also run winecfg which can set a different win version for each executable. Go ahead and set winxp for LogosIndexer.exe only win7 for Logos.exe
The path to the LogosIndexer is: (or .wine or .wine-logos depending on what you chose)
$HOME/.wine-logos/drive_c/users/$USER/Local Settings/Application Data/Logos/System/LogosIndexer.exe
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
I voted! Thanks a lot for doing this.
0 -
For some reason, the forum won't let me make any long explanations (it's send to moderation). So just for the info: I have created one script to install Logos that go from the start to the end of the installation: HERE
0 -
Hopefully this is some good news....
I am running:
Kubuntu 19.10
Wine Staging 5.0 RC2 64 Bit
Logos 64 Bit
The indexer as has been noted was almost instantly crashing and changing the winecfg to Win XP as default nor as Win XP just for LogosIndexer.exe changed nothing - consistent crashes.
I decided to dig into the file system of Logos to see if I noticed any of the funky file issues we had way back in the beginning of the Beta testing days, when the indexer was first being introduced and quite volatile in behavior.
The Bible Index and Library index folders looked fine - the Personal Book index folder has a mess in it - a sign that there was possibly some corrupt files in there.
So I decided to clean out those directories after making sure that Logos.exe and Logoeindexer.exe were not running.
After this, I double-checked that Logos.exe was set to Win10 and Logosindexer.exe was set to WinXP in winecfg and launched Logos.
The indexer immediately started, the laptop went into full overdrive as the indexer is known to do and some time later - no crashes and a completed index running Logos 64 bit under Wine 64 bit. (this is Wine Staging 5.0 RC2 64 Bit)
The three folders should have 9 files in them - any more or any less and something is incomplete or corrupt.
The folders are located in:
/home/username/wineprefixfolder/drive_c/users/username/Local Settings/Application Data/Logos/Data/randomLogosnamedfolder
Replace the italicized portions of the path with you personal setup to get to the correct folder.
In the folder the three folders you want to check are:
BibleIndex
LibraryIndex
PersonalBookIndex
Each should have 9 files and the size all depends on the number of resources you have in your library (it can be many Gigs) - again any more or any less than 9 and that could be the issue. **(The 9 files is based upon my experience with successful installs and from my fully indexed Windows and Linux installs - Logos developers may know otherwise - purely a user experience observance)
To try out what worked for me you can delete the contents of each of those three folders or mock delete them by creating a folder in each and moving each folder's contents to the new folder.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
John Goodman said:John Goodman said:
Folks can I request that you log on to winehq appdb and go to the page for Logos 8 https://appdb.winehq.org/objectManager.php?sClass=version&iId=38306
Once there please vote for it! This may help encourage developer attention etc.
Many thanks
Ok we are on the top 100 list. I want us to be in the top 25, ideally ahead of the watchtower library app;) Can we have 100 votes people?! It will only take you a few minutes and we really need dev attention to get the indexing fixed for 64bit and win 10 support!
We are now tied at 42 votes and sitting at 47 - everyone who registers and logs in has the ability to vote three times for Logos - if we can get 40 more to register, login and vote three times for Logos - we will be in the Top 10 right around Number 8.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Please don't vote using more than one email address. It is likely that the system will detect that based on ip addresses and we could get our legit votes cancelled!
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Gave three votes!
0 -
Thanks!
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Hi everybody! I have finished the version 1.0 of the script to install Logos Bible 8 32bits on any Linux 64bits (even no-multilib), and one script to uninstall to remove the installation. It uses its own mini-Linux 32bits to run wine (all in one file with less than 300MB) to make a ~/.wine32 installation and run it without system alteration on any 64bit Linux distribution. I already tested it, but I need more people to test it (You don't need to type any command line), and report issues on github. Again, link HERE
0 -
Daniel,
This looks very interesting. Unfortunately, I won't have time to set aside to work with this until Monday at the very least. I hope others can give you some feedback soon. Hopefully, I will be able to try it out next week.
0 -
Hi everyone
Thank you all for your great work. I'm enjoying Mint XFCE 19.2 and Mint Cinnamon 19.3 with Logos (via wasta installer) now. Can anyone explain me in a few words the difference between Daniels script and the wasta-linux way? Is there any advantage? Is it worth to delete the wasta-logos and reinstall it with Daniels script? I don't want to mess up my installation without need.
Another question: I still have this issue with the look of the fonts (in my prehistoric notebook as well as in a quite new PC with a big screen (1920x1200). It's not dramatic, but the look is not as smooth as in windows. They look like washed out. Changing the dpi to 120 in the winecfg helped a bit. But still there is a difference. Some wine users have the same problem with office. They changed the rendering with winetricks. Can I do the same for logos?
Have a good time and a blessed New Year 2020!
Dirk
0 -
aaylnx said:
Daniel,
This looks very interesting. Unfortunately, I won't have time to set aside to work with this until Monday at the very least. I hope others can give you some feedback soon. Hopefully, I will be able to try it out next week.
Thanks. This will help a lot.
Dirk Kellner said:Hi everyone
Thank you all for your great work. I'm enjoying Mint XFCE 19.2 and Mint Cinnamon 19.3 with Logos (via wasta installer) now. Can anyone explain me in a few words the difference between Daniels script and the wasta-linux way? Is there any advantage? Is it worth to delete the wasta-logos and reinstall it with Daniels script? I don't want to mess up my installation without need.
Another question: I still have this issue with the look of the fonts (in my prehistoric notebook as well as in a quite new PC with a big screen (1920x1200). It's not dramatic, but the look is not as smooth as in windows. They look like washed out. Changing the dpi to 120 in the winecfg helped a bit. But still there is a difference. Some wine users have the same problem with office. They changed the rendering with winetricks. Can I do the same for logos?
Have a good time and a blessed New Year 2020!
Dirk
If it's working, you don't need to change. The wasta-linux version is a good one (just not very easy to install). The script that I made is just to make the installation far more easy (you don't need to know any linux command to install and use Logos), the removal (you have a easy uninstall script too), and it avoid using your System (it's like a standalone version, or like one "Windows Portable app" for wine). Because of it, you can install using my script, test and uninstall, without having to remove wasta-linux or change anything in your System.
For the fonts try:
1- WINEPREFIX=$HOME/.wine-logos/ WINESERVER=/opt/wasta-wine/bin/wineserver WINE=/opt/wasta-wine/bin/wine /opt/wasta-winetricks/winetricks settings fontsmooth=rgb
And test! If don't work, try:
2- WINEPREFIX=$HOME/.wine-logos/ WINESERVER=/opt/wasta-wine/bin/wineserver WINE=/opt/wasta-wine/bin/wine /opt/wasta-winetricks/winetricks settings fontsmooth=brg
And test! If don't work, try:
3- WINEPREFIX=$HOME/.wine-logos/ WINESERVER=/opt/wasta-wine/bin/wineserver WINE=/opt/wasta-wine/bin/wine /opt/wasta-winetricks/winetricks settings fontsmooth=gray
And test! If don't work, try:
4- WINEPREFIX=$HOME/.wine-logos/ WINESERVER=/opt/wasta-wine/bin/wineserver WINE=/opt/wasta-wine/bin/wine /opt/wasta-winetricks/winetricks allfonts fontfix
And test the pass 1 to 2 again! If don't work, then you have a installation bug (you can run 1 again to go back to the wasta-linux recommendation).0 -
I'm grateful to everyone who has voted here: https://appdb.winehq.org/votestats.php
Please note it costs nothing to vote but can attract developer interest. We are now 35th. I would love to see us in the top 25..!
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Voted -- we're now at #32!
0 -
Voted!
We're now at #32
0
