Linux version of Logos Bible Software

Page 56 of 58 (1145 items) « First ... < Previous 54 55 56 57 58 Next >
This post has 1,144 Replies | 59 Followers

Posts 76
Rik Shaw | Forum Activity | Replied: Mon, Nov 2 2020 2:32 AM

Rik Shaw:
It may be that we need to roll back to the "safe" wine 4.18 for Ubuntu 18.04 users. Using 4.18 means it will take longer to install, but it may be "stable". I'll report back after further testing.

I have rolled back wasta-wine to version 4.18 for Ubuntu 18.04 'bionic' users. If you already installed wasta-wine version 5.20 then please remove it, and then install wasta-logos-setup again which should bring in wasta-wine version 4.18.

Negatives of version 4.18 of wine include a much longer .NET 4.8 install (with it sometimes "hanging" meaning you may need to force close it and re-run wasta-logos-setup again to hopefully get it installed). It could take around 40 minutes (or more!) to complete the .NET 4.8 installation (compared to about 6-7 minutes for wine 5.20 in Ubuntu 20.04). Additionally, running Logos with wine 4.18 will result in an initial crash the first time you start Logos. Just restart Logos and it should work the second time.

So in summary, Ubuntu 20.04 / 20.10 with wasta-wine 5.20 (staging) is preferred, but for the 18.04 users at least Logos should remain functional using the older 4.18 wasta-wine version.

Posts 3
Jonathan Guyot | Forum Activity | Replied: Mon, Nov 2 2020 4:25 AM

Hello everybody,

Many thanks Rik for your great job. Smile I used yesterday afternoon the wasta install and it was fine for me.

I had to add "sudo apt upgrade" after the update because of broken dependancies, and then all was ok for me, Logos 8 works great now, and also the indexer.

For the hanging issue, I also had it, but hitting Ctrl^C allowed the install procedure to continue.

Hoping this could help for someone. 

Jon

Posts 19
Purist | Forum Activity | Replied: Mon, Nov 2 2020 5:13 AM

Rik,

I'm running Ubuntu 20.10, with update and dist-upgrade complete. The process hangs permanently after agreeing to install corefonts.

Update: This issue is resolved. Further issues with my installation on 20.10 are being worked out in the Google Doc comment section.

Posts 76
Rik Shaw | Forum Activity | Replied: Mon, Nov 2 2020 5:39 AM

@purist, I think I just replied to you on the Google Doc. But it may be getting stuck in either setting "ddr=gdi" or in "font smoothing", both of which are done after corefonts before installing Logos. As Jonathan reported, possibly a "ctrl + c" would work to cancel the hung process and it may continue with the install.

In my reply I left a hint on piping your output to a text file so we can examine the problem further. Please keep us posted!

Rik

Posts 19
Purist | Forum Activity | Replied: Mon, Nov 2 2020 8:06 AM

Again, just a reminder that if you haven't upvoted the project on WineHQ, you can help by logging in and voting on the Top 25 list. You can cast up to three votes with your account.

For those of us with limited technical ability, this is one thing we can do to attract skilled attention to the project.

Posts 76
Rik Shaw | Forum Activity | Replied: Tue, Nov 3 2020 3:20 AM

Update on 32-bit wasta-logos-setup with Logos 8.17.0.0014 and wine 5.20-staging for Ubuntu 18.04, 20.04, and 20.10:

I found that libjpeg62:i386 needed to be added as a dependency, and after adding it I am no longer seeing crashes on 18.04 like previously. My 20.04 test machine had that package installed, which is why I didn't originally see the crash but others did. I have pushed updates to wasta-wine (version 5.20.1) for 18.04, 20.04, and 20.10 to the "Wasta-Wine PPA."

So, if you are willing to test, you can follow the Google Doc guide and hopefully you won't experience crashes. Please let us know your experience, either here or directly on the Google Doc (preferable).

As a reminder, this wasta-logos-setup process will not be able to be updated to Logos 9 since the Wasta process is only 32-bit. But hopefully it will stand as a "best possible 32-bit install" while we finalize testing, etc. with 64-bit Logos 9 installs.

Posts 4
Walter D. Huyck Jr. | Forum Activity | Replied: Tue, Nov 3 2020 8:12 AM

I'm running Linux Mint 20

I'm very new to this

I'm trying to figure out how to install the .net packages from a comand line.

Could please give specific instructions.

Thanks

Walter

Posts 4
Walter D. Huyck Jr. | Forum Activity | Replied: Tue, Nov 3 2020 8:15 AM

Loye Young:

I have been able to get Logos 8 (Windows) running on Fedora Linux, using Wine, in 64 bit.

<rant>
The developers of Logos 8 need not be afraid of supporting Linux users on Wine, or even distributing Logos 8 packaged to run on Linux natively. (.NET code can run on Mono natively, with full Microsoft support.)

There is nothing about Linux that prevents installation and use of proprietary software. There is absolutely no requirement for source code to be available for every program on a Linux machine. The owner of the machine can, if desired, install a proprietary binary blob of code, without any technical or legal prohibition or impediment. It is up to the owner of the machine to decide. (That's called "freedom.")
</rant>

The following is merely the bare outline of what I did. I'm not attempting to give a detailed "How To" article. (Also, I probably will not answer  questions or help with your installation.)

System:
Fedora release 32 (Thirty Two)
wine-5.17 (Staging)
winetricks-20200412-1
Processor Information
    Socket Designation: SOCKET 0
    Type: Central Processor
    Family: Core i5
    Manufacturer: Intel
    Version: Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz
    Voltage: 1.2 V
    External Clock: 100 MHz
    Max Speed: 2500 MHz
    Current Speed: 2500 MHz
    Core Count: 2
    Core Enabled: 2
    Thread Count: 4
    Characteristics:
        64-bit capable

Comments:

1.  I used Winetricks to install Microsoft's .NET 4.7.2 and 4.8, after a failed attempt to install. (I had set the wineprefix to Windows 10, using the graphical "Wine Configuration" tool.)

    1. Run Winetricks from the command line, which will give you great visibility into what's going on under the hood. There are a lot of "fixme" and similar comments, but almost all of them are not going to get in the way of running Logos (even if they sound scary).
    2. Ignore the pop-ups and warnings that complain about 64 bit and Mono not being present. If it says "Mono is not present", that is a Good Thing, because it's trying to remove Mono, which is for running .NET natively on Linux and conflicts with the Wine installation of MS .NET (even though MS is the sponsor of Mono).
    3. Winetricks will install earlier versions of .NET. I'm not sure if they are required, but I figure the developer had some reason to install them, so let it do what it did.
    4. .NET graphical installers will open from time to time. They will complain about not finding an installer program and warn you of mysterious and unstated problems in the future. Ignore and click "Continue". (The Wine peeps fixed that problem a few years ago.)
    5. After installing each .NET package, .NET will say you need to reboot. In this situation, that does not mean reboot your machine. it just needs to restart the wineserver. Click the reboot button in the .NET graphical. (I think "Reboot Now" is what it's called, but my memory might be wrong.)
    6. After the .NET graphical finishes, the command line will say something like "Running wineserver -w, which will hang until . . . . " Open another command line session and run "wineserver -k", which will kill the extraneous processes and Winetricks will move on.
    7. Have patience.

2. Likewise, I installed Logos from the command line: "wine [path\to\LogosSetup.exe]"

  1. As mentioned above, I had previously configured the wineprefix to run as Windows 10 (which Faithlife says is a minimum), but somewhere along the way, Winetricks seems to have changed the setting to Windows 7. Logos doesn't complain. (I wonder if the attempted installation of Logos before installing .NET might work better, but since my installation is working, I'm not going to try to figure it out.)
  2. My implementation of Wine requires the use of back-slashes, in the style of Microsoft. [shrug]
  3. Wine installed the program at ".\.wine\drive_c\users\[username]\Local Settings\Application Data\Logos\Logos.exe" Such location seems odd to me, but perhaps Windows these days installs programs there. Or perhaps the Faithlife peeps put it there to prevent others on the machine or network from running Logos without paying for another license. They gotta make a living, and as the Apostle said, "Don't muzzle an ox when he is treading."

3.  If Logos fails to start from the desktop or your Wine menu, or starts and then immediately closes, run Logos from the command line and look at the command line output for debugging information. If that doesn't work for you, try running in a Virtual Machine, or maybe consider whether your kung-fu level is ready for Logos-on-Linux. (I watched Kung Fu Panda last night. Great flick.)

4.  When running a program designed for Windows, the program may in fact perform like it does on a Windows machine, to wit: needless CPU activity, bloated RAM, and lots of disc activity, all of which make for poor performance. YMMV, depending on how fast your machine is. Mine is old (circa 2014) and slow, so I get what I get. I need to buy a new rig anyway, so that will probably help.

    1. The first time you fire up Logos, it will need to download and index the data files. The download is not horrible, but the indexing is very painful. The indexing is greedy for CPU (every CPU core and thread was at 100%) and disc IO. Just be patient and let it run overnight. Fortunately, I have an SSD, which makes the disk I/O much faster.
    2. 8GB of RAM is not enough, even without indexing going on. When running Linux natively, 8GB is plenty, so I didn't even have a swap partition. But performance tanked when running Logos 8, so I added a swap partition of 8GB, which made a big difference. I set system swappiness at 20. (Google "linux swappiness"). Probably would have been better to do that before installing.

Good luck.

Happy Trails,

Loye W. Young, OP, JD

I'm running Linux Mint 20

I'm very new to this

I'm trying to figure out how to install the .net packages from a comand line.

Could please give specific instructions.

Thanks

Walter

Posts 143
Paul Unger | Forum Activity | Replied: Tue, Nov 3 2020 9:51 AM

@ Rik Shaw: Thanks for your ongoing work with this!

I confess I got a bit confused following the directions in the Google doc... I ran sudo add-apt-repository ppa:wasta-linux/wasta-wine and got a bunch of "Get" and "Hit" lines with a final line of "Reading package lists... Done." That seemed normal, so I then ran sudo apt update and got a bunch more "Get" and "Hit" lines; but this time, after the line "Reading package lists... Done", there's the line "18 packages can be upgraded. Run 'apt list --upgradable' to see them." I went ahead and ran apt list --upgradable and found 4 wasta-logos / -wine / -winetricks packages in the list. Since sudo apt update didn't install them, I was at a bit of a loss. Back in the Google doc, though, I re-read the next "Optional" line and saw it was sudo apt upgrade rather than update! Running that installed the packages I needed to continue. It might be good to highlight that difference for us noobs...

[...later...] No hangup on installing Core fonts here. I was asked to affirm installation of .NET 4.0 and 4.8, and then request to restart. I went ahead with [Restart now] and was then requested to install Core fonts--but there was no restart! The terminal churned away for a good while until I got the Welcome to Logos Bible Software Setup window. I selected [Next] [Typical] [Install] and waited until I could click [Finish]. A bit more terminal and I got a "Logos setup complete!" window, with instructions for copying Data, Documents, and User folders back to my new Logos profile folder, which I did. When I started Logos there were 1.9 GBs to download, but that's now done (ten minutes later?). When I opened a Layout (which were saved), all my resources say, "This resource is not currently available on this device, but here's a preview..." [Download now] [Open in Web App]. So it looks like I'm going to have to figure out how to re-download all my resources. :-( I'm hoping there's an easy way to do that, since I skipped that step when I first opened Logos.

Paul

Posts 18
Al Graham | Forum Activity | Replied: Tue, Nov 3 2020 12:15 PM

4010.winelogosTerminalOutput.txt

Rik Shaw:

Update on 32-bit wasta-logos-setup with Logos 8.17.0.0014 and wine 5.20-staging for Ubuntu 18.04, 20.04, and 20.10:

I found that libjpeg62:i386 needed to be added as a dependency, and after adding it I am no longer seeing crashes on 18.04 like previously. My 20.04 test machine had that package installed, which is why I didn't originally see the crash but others did. I have pushed updates to wasta-wine (version 5.20.1) for 18.04, 20.04, and 20.10 to the "Wasta-Wine PPA."

So, if you are willing to test, you can follow the Google Doc guide and hopefully you won't experience crashes. Please let us know your experience, either here or directly on the Google Doc (preferable).

As a reminder, this wasta-logos-setup process will not be able to be updated to Logos 9 since the Wasta process is only 32-bit. But hopefully it will stand as a "best possible 32-bit install" while we finalize testing, etc. with 64-bit Logos 9 installs.

Thanks for all the work done on Logos for Linux.

I have been able to install Logos on Lubuntu 20.04.

Logos will start and run a short time.

Attached is the terminal output and the wine backtrace.

Any help would be appreciated.

Posts 76
Rik Shaw | Forum Activity | Replied: Tue, Nov 3 2020 4:27 PM

Walter D. Huyck Jr.:

I'm running Linux Mint 20

I'm very new to this

I'm trying to figure out how to install the .net packages from a comand line.

Could please give specific instructions.

Thanks

Walter

Walter, since Linux Mint 20 is based on Ubuntu, you can follow the guide for wasta-logos-setup here

The wasta-logos-setup process will take care of installing .NET, etc. so you do not need to manually do it.

Rik

Posts 76
Rik Shaw | Forum Activity | Replied: Tue, Nov 3 2020 4:30 PM

Al Graham:

Thanks for all the work done on Logos for Linux.

I have been able to install Logos on Lubuntu 20.04.

Logos will start and run a short time.

Attached is the terminal output and the wine backtrace.

Any help would be appreciated.

Al, could you confirm what version of wasta-wine you have installed?

Rik

Posts 18
Al Graham | Forum Activity | Replied: Tue, Nov 3 2020 6:00 PM

Rik Shaw:

Al, could you confirm what version of wasta-wine you have installed?

Rik

Rik:

       Wine 5.20 is the version being used.

       Thanks again for your help.

                                             Al

Posts 4
Walter D. Huyck Jr. | Forum Activity | Replied: Tue, Nov 3 2020 6:15 PM

Great Thank You Rik.  It looks like its running now and downloading resources. 

Walter

Posts 76
Rik Shaw | Forum Activity | Replied: Tue, Nov 3 2020 8:41 PM

Al Graham:

       Wine 5.20 is the version being used.

       Thanks again for your help.

Al, wasta-wine 5.20.0 has the missing dependency which leads to the crashing. So you need to upgrade to wasta-wine 5.20.1. Please let us know if you have upgraded to that new(est) version.

Posts 143
Paul Unger | Forum Activity | Replied: Wed, Nov 4 2020 11:08 AM

Rik Shaw:
Al, wasta-wine 5.20.0 has the missing dependency which leads to the crashing. So you need to upgrade to wasta-wine 5.20.1. Please let us know if you have upgraded to that new(est) version.
I've been having some crashes since upgrading yesterday; indexing was also a struggle--I think it's done after multiple attempts, but I'm starting to wonder what effect that's going to have on my SSD... :-\ Anyway, I saved a 'backtrace' from my latest crash and noticed that, in the System information at the bottom, my Wine build is wine-5.20 (Staging). I ran sudo apt install wasta-wine thinking that I might need 5.20.1, but was told that "wasta-wine is already the newest version (5.20.1~ubuntu18.04.1)". So I'm not sure what's causing my crashes, but I can submit my saved 'backtrace' if that would be of any interest.

Posts 76
Rik Shaw | Forum Activity | Replied: Wed, Nov 4 2020 8:56 PM

Paul Unger:
I ran sudo apt install wasta-wine thinking that I might need 5.20.1, but was told that "wasta-wine is already the newest version (5.20.1~ubuntu18.04.1)". So I'm not sure what's causing my crashes, but I can submit my saved 'backtrace' if that would be of any interest.

Paul, you have everything updated. Wine itself is version 5.20-staging. But the packaging of wasta-wine is what is 5.20.1 (I control the wasta-wine version number: the first 2 digits correspond to the wine version, the last digit, the original ".0" or the current ".1" correspond to the packaging version. So if there is a missing dependency or other packaging change needed, it would go to 5.20.2, even though it would still be wine 5.20-staging).

Please do post the backtrace somewhere as a downloadable file so we can inspect it. Also, please report if the crashes were related to any activity or what you were doing at the time or if it was just random.

Rik

Posts 14
Taylor | Forum Activity | Replied: Thu, Nov 5 2020 5:15 AM

Any thoughts on how to resolve the kerning issue? Note the spacing between "F" and "r".

Posts 143
Paul Unger | Forum Activity | Replied: Thu, Nov 5 2020 7:27 AM

Taylor:
<snip>Any thoughts on how to resolve the kerning issue? Note the spacing between "F" and "r".

I've got that issue as well. A solution would be marv!

Posts 143
Paul Unger | Forum Activity | Replied: Thu, Nov 5 2020 7:33 AM

Rik Shaw:

Please do post the backtrace somewhere as a downloadable file so we can inspect it. Also, please report if the crashes were related to any activity or what you were doing at the time or if it was just random.

Rik

My backtrace is here: https://www.dropbox.com/s/jy3mlmwv5pcwz9w/Logos%20crash%2001.txt?dl=0

The crashes were happening when I had the Notes tool open and I was clicking the note to try to view it in the corresponding resource. Though it may be something wonky with the specific resource I had open--I can scroll about a page or two before Logos crashes. I can scroll other resources.

Page 56 of 58 (1145 items) « First ... < Previous 54 55 56 57 58 Next > | RSS