Linux version of Logos Bible Software

Page 35 of 40 (783 items) « First ... < Previous 33 34 35 36 37 Next > ... Last »
This post has 782 Replies | 44 Followers

Posts 77
aaylnx | Forum Activity | Replied: Fri, Oct 25 2019 2:12 PM

Rik,

Your idea of breaking up the installer into different parts, many of which do not need to be frequently updated, is an excellent one!  Actually, I was going to propose the same thing.  That pretty much gets us past the problem of having huge downloads since all of these components will have to be downloaded at least once anyway.  If you are able to do this, it will move things much close to a "just works" kind of situation.  I think the install process is REALLY improving.  If you proceed down this track, we'll get a lot closer to ironing out the install bugs.

Then we can simply turn our attention to functionality and performance bugs.

Thank you so much for your hard work!

Adam

Posts 43
Rik Shaw | Forum Activity | Replied: Sun, Oct 27 2019 4:12 AM

I have now uploaded version 0.3.0 of wasta-logos-setup. It has as dependencies the following:

  • wasta-wine: patched version of wine 4.18 that will install to /opt/wasta-wine

  • wasta-winetricks: all the .net installers, etc., plus winetricks itself that will install to /opt/wasta-winetricks

It also has as a "recommends":

  • wasta-logos-installer: the Logos-x86.msi that will install to /opt/wasta-logos-installer.

The reason it is a "recommends" is because a user can put a Logos-x86.msi in their ~/Downloads folder if they have their own installer and want to use it instead. If the installer isn't found in ~/Downloads/Logos-x86.msi then it looks for /opt/wasta-logos-installer/Logos-x86.msi. If that also isn't found, then an error is thrown (I took out the logic for the installer to do the download: it was a bit complicated and I think at this point unnecessary).

Since we are now using our own version of wine, there may be some missing 386 library pieces that are needed for full functionality. IF you find errors such as this:

00fa:err:module:load_so_dll failed to load .so lib "/opt/wasta-wine/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directory

It most likely means that a needed library is missing, and we need to track it down and add as a dependency of wasta-wine to make sure others get it. Note that in the above example, the solution was to install libpulse0:i386 so that has been added to wasta-wine as a dependency.

If users of distros other than Ubuntu have trouble with some dependencies and can't get wasta-wine installed, then you can manually build (a patched) wine to /opt/wasta-wine and then wasta-logos-setup would be happy (but you will need to remove wasta-wine as a dependency from wasta-logos-setup also). Let us know how non-Ubuntu users get along.

Also due to the size I have limited the Ubuntu builds to 18.04 and 19.10 right now. I am assuming most 19.04 users will be upgrading pretty soon (if not already) to 19.10.

Posts 43
Rik Shaw | Forum Activity | Replied: Sun, Oct 27 2019 4:26 AM

I have just posted version 0.3.0 of wasta-logos-setup. It is a pretty big change in that various bits have been moved to other packages as previously discussed. So please test and report back, but note that it may introduce some bugs. Since it now uses our own patched version of wine, it does NOT assume any wine version is installed on your system. So there should be no conflicts with differing versions of wine for different distros, etc.

Here is a summary of the packages as they stand now:

  • wasta-wine: patched 32-bit version of wine 4.18 that will install to /opt/wasta-wine. NOTE: there may be missing dependencies for some 32bit libraries, so if you get an error like this:

00fa:err:module:load_so_dll failed to load .so lib "/opt/wasta-wine/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directory

Then it means a library is missing. Please report the error so we can add the dependency. In the above example, the solution is to install libpulse0:i386 which is now included as a dependency for wasta-wine

  • wasta-winetricks: bundled .NET and other winetricks items that will install to /opt/wasta-winetricks

  • wasta-logos-installer: bundled Logos-x86.msi that will install to /opt/wasta-logos-installer.

  • wasta-logos-setup: small size, has a "depends" wasta-wine and wasta-winetricks. Has as "recommends" wasta-logos-installer, which means it will be installed unless you install like this "sudo apt install --no-install-recommends wasta-logos-setup". The reason a user may NOT want wasta-logos-installer is because if they have a newer installer then wasta-logos-setup will FIRST look in ~/Downloads for Logos-x86.msi. If not found there, then it looks for the wasta-logos-installer version, and if that also isn't found, it returns an error.

Users of other distros besides Ubuntu-based distros may possibly have trouble with the wasta-wine dependencies since the package names may differ per distro. So if this is true, you can manually install a "patched" version of wine to /opt/wasta-wine and then remove the dependency of wasta-wine from wasta-logos-setup. Then hopefully you can get it installed. Let us know how it works if you are on a non-Ubuntu based distro.

Again there may be some missing 32-bit libraries so let me know if the experience of using this 0.3.0 version gives any regressions compared to previous version of wasta-logos-setup. Going forward it should be more stable since we don't have to worry about wine versions changing and breaking the ability to run Logos.

Posts 43
Rik Shaw | Forum Activity | Replied: Sun, Oct 27 2019 8:18 AM

I have just posted version 0.3.0 of wasta-logos-setup. It is a pretty big change in that various bits have been moved to other packages as previously discussed. So please test and report back, but note that it may introduce some bugs. Since it now uses our own patched version of wine, it does NOT assume any wine version is installed on your system. So there should be no conflicts with differing versions of wine for different distros, etc.

Here is a summary of the packages as they stand now:

  • wasta-wine: patched 32-bit version of wine 4.18 that will install to /opt/wasta-wine. NOTE: there may be missing dependencies for some 32bit libraries, so if you get an error like this:

00fa:err:module:load_so_dll failed to load .so lib "/opt/wasta-wine/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directory

Then it means a library is missing. Please report the error so we can add the dependency. In the above example, the solution is to install libpulse0:i386 which is now included as a dependency for wasta-wine

  • wasta-winetricks: bundled .NET and other winetricks items that will install to /opt/wasta-winetricks

  • wasta-logos-installer: bundled Logos-x86.msi that will install to /opt/wasta-logos-installer.

  • wasta-logos-setup: small size, has a "depends" wasta-wine and wasta-winetricks. Has as "recommends" wasta-logos-installer, which means it will be installed unless you install like this "sudo apt install --no-install-recommends wasta-logos-setup". The reason a user may NOT want wasta-logos-installer is because if they have a newer installer then wasta-logos-setup will FIRST look in ~/Downloads for Logos-x86.msi. If not found there, then it looks for the wasta-logos-installer version, and if that also isn't found, it returns an error.

Users of other distros besides Ubuntu-based distros may possibly have trouble with the wasta-wine dependencies since the package names may differ per distro. So if this is true, you can manually install a "patched" version of wine to /opt/wasta-wine and then remove the dependency of wasta-wine from wasta-logos-setup. Then hopefully you can get it installed. Let us know how it works if you are on a non-Ubuntu based distro.

Again there may be some missing 32-bit libraries so let me know if the experience of using this 0.3.0 version gives any regressions compared to previous version of wasta-logos-setup. Going forward it should be more stable since we don't have to worry about wine versions changing and breaking the ability to run Logos.

Posts 9
Al Graham | Forum Activity | Replied: Sun, Oct 27 2019 3:41 PM

The following messages when running wasta-logos-setup version (0.3.0~ubuntu18.04.1):

user@user:~$ wasta-logos-setup
Gtk-Message: 17:32:47.910: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: 17:32:52.094: GtkDialog mapped without a transient parent. This is discouraged.
sending incremental file list

sent 673 bytes  received 19 bytes  1,384.00 bytes/sec
total size is 383,813,768  speedup is 554,644.17

Watching zenity process. If it is canceled then kill PID_PROCESS: 14620

wine: failed to initialize: /opt/wasta-wine/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

Posts 648
Frank Sauer | Forum Activity | Replied: Sun, Oct 27 2019 5:50 PM

How would this impact a user who has already installed Logos? I remember seeing something about updates potentially breaking the install. Would this mean if the install is ever broken, that we would have to redo everything including downloading our entire libraries again? Or is there a way to just update the wine install with this package to prevent the issue going forward - without losing our current install and library?

Rik Shaw:

I have just posted version 0.3.0 of wasta-logos-setup. It is a pretty big change in that various bits have been moved to other packages as previously discussed. So please test and report back, but note that it may introduce some bugs. Since it now uses our own patched version of wine, it does NOT assume any wine version is installed on your system. So there should be no conflicts with differing versions of wine for different distros, etc.

Here is a summary of the packages as they stand now:

  • wasta-wine: patched 32-bit version of wine 4.18 that will install to /opt/wasta-wine. NOTE: there may be missing dependencies for some 32bit libraries, so if you get an error like this:

00fa:err:module:load_so_dll failed to load .so lib "/opt/wasta-wine/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directory

Then it means a library is missing. Please report the error so we can add the dependency. In the above example, the solution is to install libpulse0:i386 which is now included as a dependency for wasta-wine

  • wasta-winetricks: bundled .NET and other winetricks items that will install to /opt/wasta-winetricks

  • wasta-logos-installer: bundled Logos-x86.msi that will install to /opt/wasta-logos-installer.

  • wasta-logos-setup: small size, has a "depends" wasta-wine and wasta-winetricks. Has as "recommends" wasta-logos-installer, which means it will be installed unless you install like this "sudo apt install --no-install-recommends wasta-logos-setup". The reason a user may NOT want wasta-logos-installer is because if they have a newer installer then wasta-logos-setup will FIRST look in ~/Downloads for Logos-x86.msi. If not found there, then it looks for the wasta-logos-installer version, and if that also isn't found, it returns an error.

Users of other distros besides Ubuntu-based distros may possibly have trouble with the wasta-wine dependencies since the package names may differ per distro. So if this is true, you can manually install a "patched" version of wine to /opt/wasta-wine and then remove the dependency of wasta-wine from wasta-logos-setup. Then hopefully you can get it installed. Let us know how it works if you are on a non-Ubuntu based distro.

Again there may be some missing 32-bit libraries so let me know if the experience of using this 0.3.0 version gives any regressions compared to previous version of wasta-logos-setup. Going forward it should be more stable since we don't have to worry about wine versions changing and breaking the ability to run Logos.

Posts 43
Rik Shaw | Forum Activity | Replied: Sun, Oct 27 2019 9:16 PM

Al Graham:

The following messages when running wasta-logos-setup version (0.3.0~ubuntu18.04.1):

...


wine: failed to initialize: /opt/wasta-wine/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

Al, can you manually check to see if that file (/opt/wasta-wine/lib/wine/ntdll.dll.so) exists on your system? It should be part of wasta-wine. If it is there, then the message is referring to something else that this file needs, so we need to track it down.

Rik

Posts 85
Dirk Kellner | Forum Activity | Replied: Mon, Oct 28 2019 1:01 AM

Running wasta-logos-setup brought following error:

dirk@roterblitz:~$ wasta-logos-setup
Gtk-Message: 08:52:16.563: GtkDialog mapped without a transient parent. This is discouraged.
....
Gtk-Message: 08:52:35.672: GtkDialog mapped without a transient parent. This is discouraged.
wine: failed to initialize: /opt/wasta-wine/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

Watching zenity process. If it is canceled then kill PID_PROCESS:

Fehler: Müll-Option

Aufruf:
 ps [Optionen]

 Versuchen Sie »ps --Hilfe <Einfach|Liste|Ausgabe|Threads|Verschiedenes|Alle>«
  oder »ps --Hilfe <s|l|o|t|m|a>«,
 um zusätzliche Hilfe anzuzeigen.

Für weitere Informationen siehe ps(1).

Zenity process and parallel process both ended: success


Watching zenity process. If it is canceled then kill PID_PROCESS: 5954

Gtk-Message: 08:52:38.949: GtkDialog mapped without a transient parent. This is discouraged.
ls: Zugriff auf '/home/dirk/.wine-logos/drive_c' nicht möglich: Datei oder Verzeichnis nicht gefunden
grep: /home/dirk/.wine-logos/*.reg: Datei oder Verzeichnis nicht gefunden
  PID TTY      STAT   TIME COMMAND

Zenity process and parallel process both ended: success


Watching zenity process. If it is canceled then kill PID_PROCESS: 6005

ls: Zugriff auf '/home/dirk/.wine-logos/drive_c' nicht möglich: Datei oder Verzeichnis nicht gefunden
grep: /home/dirk/.wine-logos/*.reg: Datei oder Verzeichnis nicht gefunden
Gtk-Message: 08:52:43.071: GtkDialog mapped without a transient parent. This is discouraged.
  PID TTY      STAT   TIME COMMAND

Zenity process and parallel process both ended: success

ls: Zugriff auf '/home/dirk/.wine-logos/drive_c' nicht möglich: Datei oder Verzeichnis nicht gefunden
grep: /home/dirk/.wine-logos/*.reg: Datei oder Verzeichnis nicht gefunden
------------------------------------------------------
WINEPREFIX INFO:
Drive C:

Registry info:
/home/dirk/.wine-logos/*.reg:
------------------------------------------------------
------------------------------------------------------
/opt/wasta-wine/bin/wine cmd.exe /c echo '%ProgramFiles%' returned empty string, error message "wine: failed to initialize: /opt/wasta-wine/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory"
------------------------------------------------------
ls: Zugriff auf '/home/dirk/.wine-logos/drive_c' nicht möglich: Datei oder Verzeichnis nicht gefunden
grep: /home/dirk/.wine-logos/*.reg: Datei oder Verzeichnis nicht gefunden
------------------------------------------------------
WINEPREFIX INFO:
Drive C:

Registry info:
/home/dirk/.wine-logos/*.reg:
------------------------------------------------------
------------------------------------------------------
/opt/wasta-wine/bin/wine cmd.exe /c echo '%ProgramFiles%' returned empty string, error message "wine: failed to initialize: /opt/wasta-wine/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory"
------------------------------------------------------

Sudo apt update already told me at the end of the process:

N: Das Laden der konfigurierten Datei »main/binary-i386/Packages« wird übersprungen, da das Depot »http://dl.google.com/linux/earth/deb stable InRelease« die Architektur »i386« nicht unterstützt.
I don't know if this is essential for the problem.

Posts 85
Dirk Kellner | Forum Activity | Replied: Mon, Oct 28 2019 1:09 AM

The ntdll.dll is not in the directory /opt/wasta-wine/lib/wine. See my screenshot below with additional informations about my system

Posts 43
Rik Shaw | Forum Activity | Replied: Mon, Oct 28 2019 1:25 AM

Something is a bit strange because the nttdll.dll.so is in the source at github:

https://github.com/wasta-linux/wasta-wine/tree/master/wasta-wine/lib/wine

And also at launchpad, where the package is built:

https://git.launchpad.net/wasta-wine/tree/wasta-wine/lib/wine

So we need to figure out why it isn't in the package (or is maybe getting removed)? Do you have wasta-wine version 0.1.1?

Posts 85
Dirk Kellner | Forum Activity | Replied: Mon, Oct 28 2019 1:28 AM

I used a fresh install of Mint 19.2 without any previous wasta-logos versions. I started directly with the 0.3.0 version following your google-doc.

Posts 43
Rik Shaw | Forum Activity | Replied: Mon, Oct 28 2019 1:53 AM

I downloaded the 0.1.1 version of wasta-wine for 18.04 and indeed the ntdll.dll.so file is NOT present. So maybe the .deb was built before all the files were in place or something? Not sure as I haven't seen this issue before, but I am now triggering a re-build of wasta-wine, version 0.1.2. I'll manually check it to ensure that ntdll.dll.so is present and then report back. Strange??

Posts 43
Rik Shaw | Forum Activity | Replied: Mon, Oct 28 2019 4:35 AM

OK I haven't figured it out yet, but launchpad is removing all ".so" files. I need to sort out why and how to avoid that, so will report back when I solve something. But in the meantime, wasta-wine will NOT work for people. Sorry!

Posts 9
Al Graham | Forum Activity | Replied: Mon, Oct 28 2019 4:59 AM

Rik:

      In /opt/wasta-wine/lib/wine/fakedlls     ntdll.dll is present without the .so

      This is after I downloaded wasta-wine_0.1.2~ubuntu18.04.1_all.deb

Posts 43
Rik Shaw | Forum Activity | Replied: Mon, Oct 28 2019 9:06 AM

OK, it has been a tricky road but the version from the Logos PPA on Launchpad now includes all of the ".so" files, so wasta-wine should work for people if you give it another try (version 0.1.7). The problem, I think, is related to these .so files being compiled binaries for 32bit and they get excluded from any built package at Launchpad. I tried various tricks such as making the package 32-bit only, "stripping" the files so they didn't contain the test cases, and other such shenanigans. In the end, what I am doing is including all the files renamed to "....so-wasta" so that Launchpad doesn't remove them. Then the "postinst" script of wasta-wine renames them all back to ".so" files. This is really a lot of hackery that shouldn't have to be but I couldn't figure out why the files were getting excluded.

Anyway, again please try installing wasta-wine again (0.1.7) and see if it works for you. Possibly, if you had a previous version of wasta-wine installed you may need to remove it manually first, due to the file name changes.

Regarding previous questions about upgrading, I still don't know exactly what Logos does when it wants to upgrade, but it seems that the recent upgrade to 8.8.0.0046 required all my resources to be downloaded again. But before any upgrade it is good if you can make sure to save your $HOME/.wine-logos/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/Data $HOME/logos-app-data/Data and /Users and /Documents then restore those after the upgrade. I will look more into automating this later after we understand a bit better what is happening.

In summary, if you get Logos working I would suggest to NOT upgrade Logos unless you have to: the risk is you may need to re-download your library again :-( Also, you may need to change the Windows version to "Win7" for any upgrade to work, so I have included a launcher in the main menu called "Configure Logos Wine" that will get you to the wine settings for this $HOME/.wine-logos wine prefix.

Let me know how you get along, good luck everyone!

Posts 27
Dominik Wagner | Forum Activity | Replied: Mon, Oct 28 2019 10:03 AM

On a clean Installation of Kubuntu 19.10 64Bit:

Currently I have the following error message and the file is missing in the file system.

(wasta-logos-setup 0.3.1, wasta-wine 0.1.7)

wine: failed to initialize: /opt/wasta-wine/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

Thank you for the great work.

Posts 85
Dirk Kellner | Forum Activity | Replied: Mon, Oct 28 2019 10:50 AM

Dominik Wagner:

On a clean Installation of Kubuntu 19.10 64Bit:

Currently I have the following error message and the file is missing in the file system.

(wasta-logos-setup 0.3.1, wasta-wine 0.1.7)

wine: failed to initialize: /opt/wasta-wine/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

Thank you for the great work.

Same issue here with Min 19.2 (wasta-logos-setup 0.3.1 after deinstalling the old version with sudo apt-get --purge remove wasta-logos-setup).

Keep on smiling, Rik. Everyone is patient. Don't forget to sleep even if it doesn't work at the moment. You'll find the key! Thank you for every hour you are spending in this project!

dirk@roterblitz:~$ wasta-logos-setup
Gtk-Message: 18:44:41.164: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: 18:44:45.891: GtkDialog mapped without a transient parent. This is discouraged.
sending incremental file list

sent 684 bytes  received 19 bytes  1,406.00 bytes/sec
total size is 383,813,768  speedup is 545,965.53

*** Watching zenity process. If it is canceled then kill PID_PROCESS: 3985

Gtk-Message: 18:44:48.237: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: 18:44:48.432: GtkDialog mapped without a transient parent. This is discouraged.
wine: failed to initialize: /opt/wasta-wine/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

Posts 5
Brian Hollifield | Forum Activity | Replied: Mon, Oct 28 2019 11:55 AM

I ran into the same issue until I did and 'apt update' then re-ran the wasta-logos-setup and it's working now.

Posts 85
Dirk Kellner | Forum Activity | Replied: Mon, Oct 28 2019 2:52 PM

What I did:

1. Run wasta-logos-setup  0.3.1 (Error: missing file, see above)

2. Update wasta-wine from 0.1.1 to 0.1.7.

3. Rerun wasta-logos-setup 0.3.1. Now it works but didnt find the installer.

3. Install wasta-logos-installer

4. Rerun wasta-logos-setup. Now the installer started and I have a launcher "Logos bible software"

BUT: It doesn't start. Wasta-Wine is set to xp.

Any idea? Where is the mistake in what I did?

Posts 27
Dominik Wagner | Forum Activity | Replied: Mon, Oct 28 2019 2:55 PM

It's working for me again now.
My workaround is that I copied all files in the directory "/opt/wasta-wine/lib/wine/" with the extension "*.so-wasta" into the same directory with the new extension "*.so".
After that I could start the setup and Logos.
"krename" is a good program to do that with a single click.

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