Linux version of Logos Bible Software

Page 34 of 37 (724 items) « First ... < Previous 32 33 34 35 36 Next > ... Last »
This post has 722 Replies | 47 Followers

Posts 646
Frank Sauer | Forum Activity | Replied: Sun, Oct 20 2019 8:47 AM

Yes. That's was how I did the fresh install and it was running fine. Then at some point during the overnight download that error popped up and crashes every time I start Logos. I even tried to go back and rerun the postinst.sh command you suggested on the side comments to no avail

John Goodman:

Frank Sauer:

Well - All of a Sudden a Serious Bug has appeared. I had it running perfectly on Kubuntu 18.04, then 19.04 via upgrade and finally 19.10 via upgrade. 

I wanted to try it out on a SSD. I have done a fresh install of Kubuntu 19.10, then followed the exact installation instructions and everything was running well when I went to sleep.

I allowed Logos to download all resources over night and woke up to the following crash. Rebooted and get the same crash every time I open Logos.

7658.backtrace.txt

Did you try the new instructions step 4.5?

Posts 39
Rik Shaw | Forum Activity | Replied: Sun, Oct 20 2019 10:46 AM

I have uploaded wasta-logos-setup version 0.2.0 which adds the cabextract dependency, and also adds the wine 4.18 patch. So, at least for me on Ubuntu 18.04, with wine 4.18, everything appears to be working again. So, step 4.5 should be unnecessary, but let us know if otherwise!

In the future, if/when wine updates it will break again. So I recommend you disable the winehq repository (Software Settings > Other Software > UN-Tick the winehq source) until we can get the patch accepted into the mainstream wine repository. To prevent wine from updating and causing crashing, I could make it so that in the wasta-logos-setup install process it would disable the winehq repository. A user could manually re-enable it. But I am not sure if this would be too "heavy handed" or not. Let me know what you think of this option.

Rik

PS: @frank can you choose to "Show Details" of your crash and then look at the error? If you are getting something along the lines of a "System.AccessViolationException" then this is our original error and it means that your wine version isn't patched. I made a bit of an update to wasta-logos-setup that may address this problem by better detecting if wine needs patched and prompting for it. This is also in version 0.2.0, so let us know!

Posts 646
Frank Sauer | Forum Activity | Replied: Sun, Oct 20 2019 12:19 PM

Rik Shaw:

PS: @frank can you choose to "Show Details" of your crash and then look at the error? If you are getting something along the lines of a "System.AccessViolationException" then this is our original error and it means that your wine version isn't patched. I made a bit of an update to wasta-logos-setup that may address this problem by better detecting if wine needs patched and prompting for it. This is also in version 0.2.0, so let us know!

I didn't see that - I copied the details and posted it in my post above.

Update - I was just doing a complete fresh install of Kubuntu 18.04 and Logos got to about 90% of resources downloaded and dropped this error on me. Figured I would try going back to 18.04 and the install went smooth, log-in went smooth and then download crashed. Similar to my fresh install on 19.10 last night and it crashed during resource download and never would work again.2703.backtrace.txt

Posts 997
John Goodman | Forum Activity | Replied: Sun, Oct 20 2019 2:04 PM

Frank, I think I've seen this bug... Can you run it from the terminal and share the output? For a workaround I think you need to choose to do a minimal install and then when it has successfully indexed the first time you can add the rest of your books. The terminal output would be really helpful. The backtrace less so. It would also be helpful to know roughly how big your library is by resource count?

Thanks

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

Posts 646
Frank Sauer | Forum Activity | Replied: Sun, Oct 20 2019 2:15 PM

0743.crash.txt

Here's the output and maybe it is tied to trying a full install of the resources in one shot.... The first install I did that survived the upgrade all the way through 19.10 was minimal to begin, then once everything finished - I downloaded the rest of the resources and update to 19.04 afterward, then to 19.10.

Resources are a little over 4k

John Goodman:

Frank, I think I've seen this bug... Can you run it from the terminal and share the output? For a workaround I think you need to choose to do a minimal install and then when it has successfully indexed the first time you can add the rest of your books. The terminal output would be really helpful. The backtrace less so. It would also be helpful to know roughly how big your library is by resource count?

Thanks

Posts 799
Bill Anderson | Forum Activity | Replied: Sun, Oct 20 2019 3:15 PM

John Goodman:

Bill if you get it going on a chromebook then please document your steps and share... I'm sure there will be others who own chromebooks that would be interested.

I will do that, John. I will report back when I attempt this.

Posts 799
Bill Anderson | Forum Activity | Replied: Sun, Oct 20 2019 3:21 PM

Now that we have Logos working on Linux, it would be great to have our own sub where users can post requests for assistance instead of continuing this very long thread which now is misnamed (we aren't going to get a Linux version of Logos -- at least based on Faithlife's public statements here and elsewhere). But, I figure Faithlife won't create a sub for us because it will imply that they will support what we are all doing. It would be natural for the development effort to continue in its own space, though.

Posts 646
Frank Sauer | Forum Activity | Replied: Sun, Oct 20 2019 4:56 PM

So... I went through the whole process again...

The first download and install of the minimal resources went fine and indexed quite well. The indexing finished in comparable time to Windows. The second download of a little over 1 gig off resources did the same. A third download the program started downloading 15 gigs and it reached about 50% and crashed.

The program now opens and crashes within seconds of opening with the same error as above

Frank Sauer:

0743.crash.txt

Here's the output and maybe it is tied to trying a full install of the resources in one shot.... The first install I did that survived the upgrade all the way through 19.10 was minimal to begin, then once everything finished - I downloaded the rest of the resources and update to 19.04 afterward, then to 19.10.

Resources are a little over 4k

John Goodman:

Frank, I think I've seen this bug... Can you run it from the terminal and share the output? For a workaround I think you need to choose to do a minimal install and then when it has successfully indexed the first time you can add the rest of your books. The terminal output would be really helpful. The backtrace less so. It would also be helpful to know roughly how big your library is by resource count?

Thanks

Posts 646
Frank Sauer | Forum Activity | Replied: Sun, Oct 20 2019 8:21 PM

I may have found the cause of the error.... Having been through a couple Beta cycles in the past, I remembered similar behaviors when the old Libronix engine was left behind and all the indexing began.

One of the issues that would cause this typs of behavior was corrupt databases. I tried deleting everything out of the folding that holds the index files - didn't fix the problem.

I then tried cleaning out the Library Catalog folder - Sure enough that allowed the program to start and it did crash twice more, but each time clearing that folder allowed it to download more resources and index fine.

Right now, I have just two stubborn resources that say downloading, but do not seem to actually ever download. The index is rebuilding now.

Frank Sauer:

So... I went through the whole process again...

The first download and install of the minimal resources went fine and indexed quite well. The indexing finished in comparable time to Windows. The second download of a little over 1 gig off resources did the same. A third download the program started downloading 15 gigs and it reached about 50% and crashed.

The program now opens and crashes within seconds of opening with the same error as above

Frank Sauer:

0743.crash.txt

Here's the output and maybe it is tied to trying a full install of the resources in one shot.... The first install I did that survived the upgrade all the way through 19.10 was minimal to begin, then once everything finished - I downloaded the rest of the resources and update to 19.04 afterward, then to 19.10.

Resources are a little over 4k

John Goodman:

Frank, I think I've seen this bug... Can you run it from the terminal and share the output? For a workaround I think you need to choose to do a minimal install and then when it has successfully indexed the first time you can add the rest of your books. The terminal output would be really helpful. The backtrace less so. It would also be helpful to know roughly how big your library is by resource count?

Thanks

Posts 9
Al Graham | Forum Activity | Replied: Mon, Oct 21 2019 4:52 AM

It would be great to have a forum area for Linux!

Posts 14
Gene W. | Forum Activity | Replied: Wed, Oct 23 2019 6:04 AM

@J. Erik

How did your attempt with Manjaro go? I've recently made the switch from Mint to Manjaro (Gnome) and will give it a good shot once I get my head around where to begin. Yes

Husband, Dad, Expat to Northern Europe. I serve people, share hope, & write about simple theology for a messy life at genewhitehead.com.

Posts 82
Dirk Kellner | Forum Activity | Replied: Wed, Oct 23 2019 6:11 AM

Gene W.:

How did your attempt with Manjaro go? I've recently made the switch from Mint to Manjaro and will give it a good shot once I get my head around where to begin. Yes

Hi Gene

I failed to install winehq-devel. There is no such package in the Repositories or in the AUR. I tried to compile it but without success. So I installed mint 19.2 (=ubuntu 18.4). But I have some issues with installing .net 4.7.2. The installation quits with failure (winehq 4.18 and wasta 0.2). I decided to wait some month until our experts got run a new version of the wasta-setup. Btw. manjaro is really the faster and nicer linux. 

Greetings

Dirk

Posts 14
Gene W. | Forum Activity | Replied: Wed, Oct 23 2019 6:19 AM

Hi Dirk,

Thanks for that information. I'll also wait at this point too. Agreed, Manjaro has been great so far. So much that I'm not willing to step out of it just yet and will run Logos in a VM for now. Appreciate your attempts and sharing your insight from it.

Husband, Dad, Expat to Northern Europe. I serve people, share hope, & write about simple theology for a messy life at genewhitehead.com.

Posts 39
Rik Shaw | Forum Activity | Replied: Thu, Oct 24 2019 11:34 AM

Due to wine versions changing and overwriting the necessary patch, it was discussed to bundle wine with the patch as part of wasta-logos-setup.

I have experimented with this and can make it work, BUT it adds 853MB of size to the package! I don't know of a smart way to bundle wine except for manually taking the entire /opt/wine-devel/ folder. I can't seem to split apart the amd64 pieces of it automatically, maybe I can manually remove them.

Regardless, even if I could remove all amd64 pieces, it would still be possibly 450MB of size to bundle wine. Opinions?

Posts 997
John Goodman | Forum Activity | Replied: Thu, Oct 24 2019 12:36 PM

I've built debs for 4.18 both architectures and it comes to 191mb. I'll ping them across to you in an email.

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

Posts 3
Jim Rutledge | Forum Activity | Replied: Thu, Oct 24 2019 12:54 PM

So, I finally had the time to sit down and go through the instructions provided here.

All I can do is parrot Anakin Skywalker from The Phantom Menace when he was testing his podracer: "It's working! IT'S WORKING!!!"

I want to send a personal "Thank you!" and "God bless you!" to each and every person who has worked tirelessly to bring Logos to Linux. You all have my deepest appreciation. I know things aren't perfect, but it is working and I am over the moon because of it!

For what it's worth, I am on LinuxMint 19.1 "Tessa," Linux kernel 4.15.0-66-generic, on a Dell laptop with AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx × 4.

Also, to get Logos to open initially, I had to switch Wine to Windows 7. After that, it opened and began downloading all my resources perfectly fine and is now indexing my library... though it seems to have hung up around 25 or 27% (in-program is says 25% but the icon in the tray says 27%). But that doesn't bother me much. So long as my resources are there and I can now actually use Logos on Linux, I am ecstatic! Party!!!

Posts 646
Frank Sauer | Forum Activity | Replied: Thu, Oct 24 2019 5:56 PM

Anyone else have ClamAV flag just about the entire Logos wine install as malware? Just ran a scan and had over 300 malware hits in the Logos directory

Posts 39
Rik Shaw | Forum Activity | Replied: Thu, Oct 24 2019 9:44 PM

John Goodman:

I've built debs for 4.18 both architectures and it comes to 191mb. I'll ping them across to you in an email.

Thanks for doing this, it proves that it does compress down to a lot smaller size, which I had been neglecting to consider. I just did a test build with wine bundled and it comes to 442MB, but we were already at something like 383MB, so the bundling of wine is "only" adding about 60MB.

With this growing size, plus the possibility of bundling the Logos.msi installer as well, my newer thought is to split off the various "big files" into multiple .deb packages, like this:

  • wasta-logos-setup: the scripts to get it installed (would be relatively small... maybe a few MB max). It would list as dependencies wasta-wine, wasta-dotnet, and wasta-logos-installer.

  • wasta-wine: bundled wine (32bit only) - again maybe 60-80MB

  • wasta-dotnet: winetricks .NET installers - about 350MB

  • wasta-logos-installer: Logos msi installer - about 185MB

This way users won't need to download a HUGE monolic .deb each time even a minor change occurs. They would only need to download the one that had the changes. The negative is for people not on Ubuntu / .deb based systems they need to manually be taking the files from 4 different packages (or maybe they would be able to be converted using the deb2arch utility or deb2rpm process).

Additionally, there are other .NET apps that we may need to take a similar approach for. By having wasta-dotnet separate, each other package could list it as a depends, following the spirit of .deb packaging. Of course we want to avoid a dependency nightmare so don't want it to get too complicated!

Thoughts with this proposal?

Posts 82
Dirk Kellner | Forum Activity | Replied: Fri, Oct 25 2019 12:10 AM

@Rik: Great Idea to split the packages. Future updates only will affect the new packages. Bug-finding will be easier as everyone can start each step by step. I'll try it with my older acer-notebook, where I had no success so far. As soon as the packages are in the repo. Thank you!

Btw. I still hope the enthusiastic posts of so many users will move faithlife to creatve a native soluition for linux. I have this dream...

Posts 997
John Goodman | Forum Activity | Replied: Fri, Oct 25 2019 2:02 AM

Frank Sauer:

Anyone else have ClamAV flag just about the entire Logos wine install as malware? Just ran a scan and had over 300 malware hits in the Logos directory

I imagine it would because it would expect the windows dlls to have certain fingerprints but since wine is not windows it will look spurious. That's a guess but winehq is a trusted source and so is faithlife.

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

Page 34 of 37 (724 items) « First ... < Previous 32 33 34 35 36 Next > ... Last » | RSS