Linux version of Logos Bible Software

Page 53 of 58 (1145 items) « First ... < Previous 51 52 53 54 55 Next > ... Last »
This post has 1,144 Replies | 59 Followers

Posts 60
Daniel Ribeiro da Silva | Forum Activity | Replied: Wed, Oct 7 2020 2:50 AM

Frank Sauer:

...

There was no error message. I have the normal updates available notification. The two libsdl2 files that there are updates for notify me when I select them for update, that Wine will have to be removed to update the libsdl2 files.

Good. In this case, just hold on to the libsdl2 update for a while, someone will eventually fix the issue in the repositories and the conflict will automatically disappear (although it may take a while).

Posts 11
Elliot Swaim | Forum Activity | Replied: Tue, Oct 13 2020 9:29 AM

I'm dual booting Ubuntu and Windows, and I was wondering if there's any possibility of installing Logos on both Windows and Linux.  I'd want it on Linux because that's the operating system I use most often, and I'd want it on Windows as well in case I ever need to do something that doesn't work on either the Linux version or the Web App (like some media). 

I have successfully installed two separate versions of Logos on Linux and Windows, but since they were completely separate, they wouldn't sync any updated data or notes or anything, and they together took up more space than I would like on my hard drive (twice the normal size of the Logos folder). 

I also tried installing Logos through WINE on an external hard drive (ultimately, I would have wanted it on a D drive on my computer accessible in both operating systems, but my D drive was too small at the time) and got it to work on Linux, but when I tried opening it on Windows, it said that the some documents required the latest version of Logos (following some instructions I found on this forum, the Logos installer wasn't the most up-to-date). 

So now my thoughts are that the most ideal way to do it would be to have two Logos folders on a D drive available in both Linux and Windows, but to have it somehow share the same data folder (and any other folders that might be necessary, like the Documents folder).  That way, I could run Logos in either Linux or Windows without having to store all my data twice for each version of Logos.  I just don't know how or even if it's possible to get Logos to use an alternate path to a data folder.  Does anyone have any ideas?  Like some script that could redirect a ./Data query from the main Logos folder to ../LogosData/Data?  Or maybe somehow replace the Data folder in both Logos installations to some other Logos Data folder that would contain the data shared by both versions of Logos?  Does anyone know if this would be possible?  Or does anyone have any better ideas for how to install Logos on both Linux and Windows?

Posts 1112
John Goodman | Forum Activity | Replied: Tue, Oct 13 2020 9:49 AM

I think you'd have a good chance of getting it to work by replacing the data folders in the linux installation with links to the same in the windows installation. Its documents, users and data...

גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה

Posts 18886
Forum MVP
Keep Smiling 4 Jesus :) | Forum Activity | Replied: Tue, Oct 13 2020 6:08 PM

John Goodman:

I think you'd have a good chance of getting it to work by replacing the data folders in the linux installation with links to the same in the windows installation. Its documents, users and data...

Caution: inside some SQLite database files is the path to Resources, ... so dual booting operating systems needs identical Logos installation path.

Thread => Logos 8 Mac System Recommendations (what you'd actually want as a user) includes my 27" iMac dual boot configuration that shares my Logos (purchased library) and Verbum (demonstration account) installations (same path to application files in both operating systems). 

Keep Smiling Smile

Posts 143
Paul Unger | Forum Activity | Replied: Wed, Oct 14 2020 9:00 AM

I'm getting persistent crashes for LogosIndexer.exe for a while now... I've been thinking about updating (I'm still running Logos 8.8 in WINE 4.18 and it won't update on its own), and figure this is as good a time as any, but not quite sure how to go about it. I used Rik's method when I first installed Logos (the instructions on the Google doc page). There are also "beta instructions" for updating Logos. Is that my best bet?

[...later...]

Well, I tried just going for the full "install" rather than an "update". Figured this might be safer since things were acting broken. First time through I was asked if I wanted to delete my current folders and rebuild them. I said yes, since I have a backup of my data folders. In the end, I got an error saying Logos Setup had quit because .NET 4.7.2 wasn't found on my computer. During the install, I got a message saying that .NET 4.8 was being installed--and that it could take 30 minutes (thankfully, it didn't!)--but I didn't see anything about trying to install .NET 4.7.2... After the "Installing .NET 4.8" window, there was one about installing Corefonts. That's when it quit.

It worked second time through. Just trying to install resources (from backup) and then see if indexing will work...

Posts 688
Frank Sauer | Forum Activity | Replied: Wed, Oct 14 2020 9:59 AM

Paul Unger:

I'm getting persistent crashes for LogosIndexer.exe for a while now... I've been thinking about updating (I'm still running Logos 8.8 in WINE 4.18 and it won't update on its own), and figure this is as good a time as any, but not quite sure how to go about it. I used Rik's method when I first installed Logos (the instructions on the Google doc page). There are also "beta instructions" for updating Logos. Is that my best bet?

I would definitely recommend updating Wine, a lot of fixes have been completed that greatly enhance the Logos experience on Linux.

In relation to what's best...

Depends - if your only issue is the indexer crash, you can try the solution I posted previously for those types of issues. Clear out the index folders and library catalog folders if there are more files than a clean install. This usually works for the issue with the indexer it seems you are experiencing. There were issues with indexing in earlier versions of Wine, so that could be the needed solution for your indexer issue as well.

For updating Logos, there is a major bug that needs to be fixed right now. Updating through the application has been deleting all downloaded resources - so the work around has been to download the executable and upgrade by that means. So far no deleting of resource with that method.

Posts 143
Paul Unger | Forum Activity | Replied: Wed, Oct 14 2020 10:16 AM

Frank Sauer:

I would definitely recommend updating Wine, a lot of fixes have been completed that greatly enhance the Logos experience on Linux.

OK. There are instructions in the Google doc for updating Wine (bottom of p. 7), but the preamble ends with a dire warning... Is there another method I should try? Recommended version?

Posts 76
Rik Shaw | Forum Activity | Replied: Wed, Oct 14 2020 10:36 AM

Paul Unger:

Frank Sauer:

I would definitely recommend updating Wine, a lot of fixes have been completed that greatly enhance the Logos experience on Linux.

OK. There are instructions in the Google doc for updating Wine (bottom of p. 7), but the preamble ends with a dire warning... Is there another method I should try? Recommended version?

Paul, I have been in contact with Daniel who is leading the bug stomping effort.... there are a few problems with newer versions of wine as well (some regressions, etc.) The main effort is to try and get 64bit Logos to work with wine since we know Faithlife will drop 32bit support sometime in the somewhat near future.

As you have noted, some updates I made to wasta-logos-setup a few months back moved from .NET 4.7.2 to .NET 4.8 which installs much faster and didn't have negative side effects. But as there are some issues with newer wine I have played it "conservative" not moving wine versions for the wasta process until we are more confident it is an improvement.

So, in summary indeed wine in wasta-logos-setup is an older version, and as you note there are occasional (even frequent) indexer challenges, but eventually it seems to work for most people.

NOTE for updating Logos itself I made some quick edits to the guide you reference. In short, you can re-run wasta-logos-setup (effectively what was recommended by others: updating "outside" of Logos itself) withOUT deleting the current wine install, and it will upgrade you to Logos 8.13. I haven't put a newer version in wasta-logos-setup yet but if you manually download a newer version and place it in your Downloads folder (named Logos-x86.msi), then run wasta-logos-setup it will use it (the one in Downloads) instead of version 8.13. So you can again always run wasta-logos-setup with a newer version of the installer in Downloads to update Logos.

Make sure you backup first if you don't want to re-download everything. However, we have noted that certain Logos upgrades required re-downloading ALL resources again regardless, so be prepared for internet use, but it should work in the end.

Once Daniel feels things have stabilized I can incorporate the newer wine version into the wasta-logos-setup process, will likely move to 64bit Logos, and will clean up the documentation as well, but again I am taking a back seat to Daniel's excellent efforts.

If you want to be more experimental with newer wine versions, etc. then check out Daniel's "AppImage" approach. It may use lower CPU, etc., and if you have the time he may appreciate further testing. The most responsive way to get feedback is through the Telegram channel: https://t.me/linux_logos

Good Luck, keep us posted!

Rik

Posts 18
Al Graham | Forum Activity | Replied: Wed, Oct 14 2020 10:51 AM

Frank Sauer:
Updating through the application has been deleting all downloaded resources - so the work around has been to download the executable and upgrade by that means.

Frank:

          Could you share the link in the forums or how download executable and upgrade.

Thanks Al

Frank Sauer:
Updating through the application has been deleting all downloaded resources - so the work around has been to download the executable and upgrade by that means.

Posts 143
Paul Unger | Forum Activity | Replied: Wed, Oct 14 2020 11:58 AM

Rik Shaw:

So, in summary indeed wine in wasta-logos-setup is an older version, and as you note there are occasional (even frequent) indexer challenges, but eventually it seems to work for most people.

...

Once Daniel feels things have stabilized I can incorporate the newer wine version into the wasta-logos-setup process, will likely move to 64bit Logos, and will clean up the documentation as well, but again I am taking a back seat to Daniel's excellent efforts.

Thanks for the update, Rik. I was just composing a message about having been at this Linux thing for a while, and being really pleased when it works, but once again finding myself up against the wall of "not-really-knowing-what-I'm-doing-but-only-having-instructions-that-assume-I-do"... I was at the point of having a look at Daniel's "script", just so see if I could make that work for me, but got hung up on step 00:

00- Download and execute:

You can download the last release [HERE].

Well, I didn't find anything obvious HERE, but there are four "Assets" at the bottom of the page. I had no idea what to download, but after looking at some of the command line stuff I figured it was "install_AppImageWine_and_Logos.sh". I still had no idea what to do with it...

So it's good to know that a more stable update is in the works. I will continue on with Wine 4.18 and wait for an update to 64bit. And if you're cleaning up the documentation, could you /please/ assume that some of us are starting from "itch" (i.e., one step before starting from "scratch")? E.g., "Download *this* file to *this* directory. Open a terminal and *change directory* (if required) and run *this* command," etc. Your help is enormously appreciated!

As for my install, I have Logos up and running again (had to download 3.9 GB of my 20 GB of resources...), but indexing is still throwing errors. I'll see if any of the workarounds work.

Posts 19
Purist | Forum Activity | Replied: Wed, Oct 14 2020 5:03 PM

My indexing stopped working on Ubuntu 18.04.

I had a working version of Logos, but it recently began crashing more often. I though perhaps an update would fix it, so I followed the instructions in the Google Doc regarding the update with the newest installer in my Downloads folder. After a successful update, the indexing program failed, so I tried deleting the contents of the BibleIndex, etc. folders as has been discussed here. That did not fix the indexing.

I then reinstalled Logos without any .msi file in my Downloads folder,hoping to restore the previous setup. The indexer still crashes. I deleted the BibleIndex, etc. folders again after this installation, but indexing still crashes.

I then tried winetricks arch=32 -q dotnet472 corefonts ddr=gdi fontsmooth=rgb win7, plus winecfg and changing the default setting to XP. Still no luck.

I tried to install via Daniel's script, and got an error saying "Your system does not have the command: ntlm_auth. Please install ntlm_auth package" I haven't been able to find this package in spite of my search online.

I don't have a preference between Daniel's script and wasta-linux, but I do want to get indexing going again. What would you all recommend?

Thanks.

Posts 76
Rik Shaw | Forum Activity | Replied: Wed, Oct 14 2020 11:02 PM

Paul Unger:
As for my install, I have Logos up and running again (had to download 3.9 GB of my 20 GB of resources...), but indexing is still throwing errors. I'll see if any of the workarounds work.

I have been confused by indexing errors..... sometimes it seems that people report there are errors, but still in the end indexing completes. You can check "System Monitor" to see if any process related to indexing is still running (if so, maybe it will complete even though it gave errors?). Sorry I haven't re-installed a clean Logos setup in a while to better understand the indexing issues.

Regarding the AppImage instructions, sorry you got confused using those. For reference, I put a link to the AppImage github home in the main Ubuntu / Wasta-Linux Logos Installation Guide so people can find reference to this alternative / more "cutting edge" process more easily.

Daniel has pretty detailed instructions in the README.md, but I think you are right it isn't completely clear what you download from the "Releases" page. You want to download the "standard" .sh file (sorry I haven't kept up on what the difference is with the "fast" .sh alternative file). Then proceed with step 0.1 (chmod +x on the downloaded .sh file). I am sure he would like help in re-wording anything that is confusing for users, so please create issues at that github site for things that need more clarification.

Posts 143
Paul Unger | Forum Activity | Replied: Thu, Oct 15 2020 10:45 AM

Purist:

My indexing stopped working on Ubuntu 18.04.

...

I tried to install via Daniel's script, and got an error saying "Your system does not have the command: ntlm_auth. Please install ntlm_auth package" I haven't been able to find this package in spite of my search online.

I don't have a preference between Daniel's script and wasta-linux, but I do want to get indexing going again. What would you all recommend?

Thanks.

You're way ahead of me in terms of what you're trying, Purist, but I wonder if "ntlm_auth" is part of Windows's "NT LAN Manager" (see https://en.wikipedia.org/wiki/NT_LAN_Manager, and https://docs.microsoft.com/en-us/windows-server/security/kerberos/ntlm-overview)? Just a shot in the dark, but if it helps you along, maybe it's worth it (as it may help me eventually, too!).

Posts 143
Paul Unger | Forum Activity | Replied: Thu, Oct 15 2020 11:15 AM

Some things I've noticed about Indexing behaviour when it fails:

1. Usually when Logos is "doing" something--updating, syncing, indexing--there's a blue number in the upper right of the menu bar. When indexing, there's also a progress indicator (x%). When I start Logos, my CPU ramps up, the fan starts whirring, and the process "LogosIndexer.ex" starts (NB that's not a typo), but there's no blue number in the Logos menu bar, and no indication of progress--none of the usual indicators, in other words, that Logos is "doing" something.

2. I'm curious about the process name "LogosIndexer.ex". The command line (found with a right click > Properties) is: C:\users\username\Local Settings\Application Data\Logos\System\LogosIndexer.exe, so maybe it's just the name that isn't .exe. But the other Logos processes have the full .exe in their names: LogosCEF.exe and Logos.exe. Like I said, I'm curious...

I don't know if that's helpful for troubleshooting, but there you have it. I have also saved a log from the crash report, if that would be useful to anyone.

Posts 76
Rik Shaw | Forum Activity | Replied: Thu, Oct 15 2020 11:31 AM

Paul, using the wasta-logos-setup install, you can manually start the indexer this way:

WINEPREFIX=$HOME/.wine-logos/ /opt/wasta-wine/bin/wine $HOME/.wine-logos/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/System/LogosIndexer.exe

At this point I am not certain my indexing is complete.... it does seem to end in an error with some "deadbeef" output which is never good :-( I know that Indexing is completing much quicker using the newer wine versions from the AppImage method. It will take some testing and review if it is reliable enough to move wasta-logos-setup users to or not.... I fear it isn't quite ready. But if we can't get indexing to work at all currently that isn't good!

Posts 885
Bill Anderson | Forum Activity | Replied: Thu, Oct 15 2020 12:03 PM

Purist:

I tried to install via Daniel's script, and got an error saying "Your system does not have the command: ntlm_auth. Please install ntlm_auth package" I haven't been able to find this package in spite of my search online.

When I recently installed Logos using Daniel's script, I ran into this. IIRC, I solved the issue by installing the winbind package. There also were a couple of others I had to hunt down and install.

Posts 60
Daniel Ribeiro da Silva | Forum Activity | Replied: Thu, Oct 15 2020 6:46 PM

I'm sorry. Since July 2020 everything started to fall apart. The installer script stopped working, the old portable version didn't worked anymore, and I was never able to update LogosBible again (on every update after this, i'm removing and installing it again). The wine-5.x version was using a lot of CPU, and it was very hard to use here (slow machine). And with wine-5.17, even the WINE AppImage using 32-bit dependencies have stopped working as well.

We made progress too, but like I told John Goodman on telegram, each 32-bit proper build and test takes about 1 hour (if we go fast), and each regression test needs somewhere around 10-15 builds. So something like 1 hour x 12 = 12 hours. And if we need to test the 64-bit version, the proper compilation and testing takes around 2 hours (because the 64bit version needs the 32bit version working at the same time). So something like 2 hour x 12 = 24 hours (again, if we go fast with the test). So it take some time to do even simple things like one regression test. The WINE project kinda implements one entire operating system, which is quite large.

Well, we can only do what God allows us to do. And at the moment I don't feel confident about making recommendations. Maybe just one: try to wait a little longer with the versions that are still working, and use the new ones just for testing, so you will always have a working version.

I separated the Changelog from the release page (making it cleaner), and put the description of the files in it. I also made a short video of 00:02:38 with the installation done with fast_install_AppImageWine_and_Logos.sh, and put the link in the step "00- Download and execute:", right at the beginning. I was unable to post it on youtube (upload stops at 1%), so I hope everyone can download and run it locally.

And may God bless us.

Posts 19
Purist | Forum Activity | Replied: Fri, Oct 16 2020 7:29 AM

Hi Daniel,

This is immensely helpful, and I appreciate all the work you have put in. The video works. I did not know I needed to install those two packages, and now the installer is up and running.

One more question for the "wasta" experts: Assuming Daniel's script installs, how do we remove the wasta-wine version of Logos from the applications? I know how to run "wine uninstaller" but obviously the application isn't listed there.

Grateful for the help.

Posts 143
Paul Unger | Forum Activity | Replied: Fri, Oct 16 2020 7:40 AM

That's a very helpful update, Daniel! It's always good to know that one is not alone. And that the issues one is facing are being faced by others with a chance of sorting them out (I don't have a chance...). ;-) I have a working version (Logos 8.13 on Wine 4.18); I just can't get indexing to complete. That doesn't seem to be affecting anything I'm doing in Logos right now, so I'm not going to get too upset about it. In fact, it sounds like I should be quite thankful about that, and I am.

I'll have a look at the video you posted. It sounds like the "cleaner" website will make more sense to me now. Thanks!

Let me just say that I appreciate the effort and time the developers have put into getting this project as far along as it is--more than I can say. Honestly, God has blessed us through your and the other developers' efforts! I'll say a prayer for His continued blessing, and that He'll show you guys the way forward. ;-)

Posts 19
Purist | Forum Activity | Replied: Fri, Oct 16 2020 10:45 AM

I followed the AppImage video Daniel created and my new Logos install is now (drum roll please...) indexing! I also changed the icon to match the "stock" Logos icon that installs with the wasta-wine version.

A huge thank you to everyone who continues to make this possible.

Page 53 of 58 (1145 items) « First ... < Previous 51 52 53 54 55 Next > ... Last » | RSS