Linux version of Logos Bible Software
Comments
-
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??
0 -
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!
0 -
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
0 -
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!
0 -
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.
0 -
Dominik Wagner said:
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 directory0 -
I ran into the same issue until I did and 'apt update' then re-ran the wasta-logos-setup and it's working now.
0 -
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?
0 -
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.0 -
While installing the .NET 4.7.2 I have a lot of messages like the following:
0082:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0082:fixme:process:SetProcessDEPPolicy (1): stub
0082:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0082:fixme:path:parse_url failed to parse L"System"
0082:fixme:process:FlushProcessWriteBuffers : stub
0082:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011dThe process is running, but Idk if there is an issue related to my problem of not starting. Did you have the same output?
0 -
I think that looks normal.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
Dominik Wagner said:
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".
Dominik, so the files still had the .so-wasta extension name after the install of wasta-wine finished? The postinst "should have renamed them" so I will have to see if others have that issue.
Everyone, to re-run the postinst script to see if it would automatically rename the files, I think the easiest thing to do is this:
sudo dpkg-reconfigure wasta-wine
0 -
Dirk Kellner said:
BUT: It doesn't start. Wasta-Wine is set to xp.
Dirk, please try to start Logos from the terminal and see if it gives more clues:
WINEPREFIX=$HOME/.wine-logos/ /opt/wasta-wine/bin/wine $HOME/.wine-logos/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/Logos.exe LC_ALL=C
0 -
Hi Rik
I tried that too. Logos started and told me .net 4.7.2 is required. "Do you want to install it now..."?
I have reset my system with rsync now and will retry it in the evening. While installing .net there were some irritating messages like "failed to parse...". I could upload the whole terminal output next time, if you want. Maybe you can see the problem.
Greetings
0 -
Dirk Kellner said:
I tried that too. Logos started and told me .net 4.7.2 is required. "Do you want to install it now..."?
I have reset my system with rsync now and will retry it in the evening. While installing .net there were some irritating messages like "failed to parse...". I could upload the whole terminal output next time, if you want. Maybe you can see the problem.
You may want to first save your Logos/Data, Logos/Documents, and Logos/Users from your current ~/.wine-logos install. Then when running wasta-logos-setup choose to delete and re-install the wine prefix (this ~/.wine-logos folder). That way you would have a clean attempt that may show the errors more clearly, or may even get you all the way to a working install.
0 -
Rik Shaw said:
... Dominik, so the files still had the .so-wasta extension name after the install of wasta-wine finished? The postinst "should have renamed them" so I will have to see if others have that issue....
Yes, the files still had the "*.so-wasta" extension after installation.
0 -
Rik:
Attached is the terminal output of Logos with recent changes installed.
Wine gives Program Error soon after Logos is launched.
Thanks for all you are doing to get Logos to run on Linux.
0 -
Do you have cabextract installed? If not, that will be one of the reasons it fails. Winetricks needs cabextract in order to install .Net. However, you're trying to run it on Arch right? It was added as a dependency in the Wasta installer, but as a dependency for Ubuntu. if you're trying to get this working on Arch, then you would need to install it on your own.
0 -
Yeah, it's working now. And it's relatively fast on my old 4GBRAM-Machine. Thank you so much. The only thing is, that I must launch it in the terminal mith:
WINEPREFIX=$HOME/.wine-logos/ /opt/wasta-wine/bin/wine $HOME/.wine-logos/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/Logos.exe LC_ALL=C
After clicking on the official starter nothing happens.Even if I copy this command and overwrite the command of the starter nothing happens.
0 -
Dirk, glad you got it working! You could run wasta-logos-setup again (do NOT create a new prefix) and it should repair your launcher. Alternatively, you can manually adjust it. Here is what my launcher has:
Exec=env WINEPREFIX="/home/rik/.wine-logos" /opt/wasta-wine/bin/wine C:\\\\windows\\\\command\\\\start.exe /Unix /home/rik/.wine-logos/dosdevices/c:/users/rik/Start\\ Menu/Programs/Logos\\ Bible\\ Software.lnk LC_ALL=C
0 -
Al Graham said:
Attached is the terminal output of Logos with recent changes installed.
Wine gives Program Error soon after Logos is launched.
Thanks for all you are doing to get Logos to run on Linux.
Al, sorry I don't see anything apparent there. There are a LOT of messages that fly by and I am not good enough to know which may be the problem you are facing.
Can you possibly try re-creating the ~/.wine-logos prefix by re-running wasta-logos-setup? This would require a full re-download of your Data, however. You could save your Logos/Data, Logos/Documents, and Logos/Users from your existing ~/.wine-logos first and then restore them after the install finishes, but if you have decent internet maybe you want to fetch it cleanly from the internet again? I think that would give the best chance to make sure it isn't anything in the local ~/.wine-logos that is causing the issues.
Rik
0 -
Rik:
Somehow got it working. Reran wasta-logos-setup, did not setup new .wine-logos directory.
Did a uninstall of Logos software in the Logos installer, which did not uninstall Logos.
I do not know why but it is working now.
Thank you again for all of your efforts.
Logos runs very well on an old Compaq 6710b with a Intel Celeron processor.
I am running Lubuntu 18.04
0 -
Hi Rik
I replaced the starter command by what you wrote me and adopted it. No success: "directory or file not found". Now I created my own shell-script logos.sh and a launcher to run it. That's not the direct and simple way, but it works. Thank you for the support.
Dirk
0 -
Dirk Kellner said:
I replaced the starter command by what you wrote me and adopted it. No success: "directory or file not found". Now I created my own shell-script logos.sh and a launcher to run it. That's not the direct and simple way, but it works. Thank you for the support.
Dirk, I am glad after a LOOOONG process that you finally have it running. I can't exactly say why your launcher isn't working, but if you want to post the contents of it, maybe something would be apparent. Again it seems "possible" that by re-running wasta-logos-setup and choosing "repair" that it should repair your launcher, but maybe you don't want to mess around too much if it is working now via a script to launch it.
Rik
0 -
Hi Rik
I deleted the old launcher. And you are right: Ich don't want to mess around. I'm fine with my own little script (my first linux-script, lol). I'll test the other issue I wrote in the google doc. Maybe it works now.
Greetings, Dirk
0 -
I updated wasta-wine to version 0.1.8 that adds "rename" as a dependency. I am hoping this will take care of the issue of some users getting errors from the .so-wasta files not getting renamed to .so on install.
So if anyone else has an error where something like ntdll.dll.so is not found, but the files are still named .so-wasta (so ntdll.dll.so-wasta for example) in the /opt/wasta-wine/lib/wine folder then please let me know.
0 -
I have completely reinstalled logos with the new packages on Kubuntu 19.10.
Everything works great now. Thank you [:)]
0 -
I hadn't read this thread since August or early September, so imagine my surprise when I stumbled upon this post last night! As a sysadmin, this made it very difficult to sleep: to finally be rid of Windows.[^0] As with many others, I no longer need Windows at all. As a student at RTS, this is great news for my research! When BibleWorks went down, I bought the crossover package and setup my virtual machine. (Here's that caveat: unfortunately the seminary requires use of the Lockdown Browser for exams so the drive will be dual booted until graduation, but the VBox machine can be destroyed!)
Seeing that Logos was more than willing to let their installer be included in a repo was also wonderful news full of brotherly love. [:)]
Thank you so much for everyone's hard work! Louis Lenders, our Wine dev, @Rik, @John, and all other contributors. Surely there must be treasures stored up in heaven for this!
My main workstation's setup is i7-4790k, 32 GB[^1], on SSD; Kubuntu 18.04, using KDE Plasma w/ GTX 970.
The install through wasta took me 15 minutes. Now its downloading the rest of my library and indexing.
I will have to checkout an rsync of the data over to my laptop!
[^0]: One caveat.
[^1]: Because VirtualBox Logos had to be a thing.
0 -
So, I am back trying to get this to work on my chromebook. Long story short, I am dual-booting into GalliumOS, which is a build of Xubuntu 18.04. Here is my terminal output when I try to run wasta-logos-setup:
chrx@chrx:~$ sudo apt install wasta-logos-setup
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:The following packages have unmet dependencies:
wasta-logos-setup : Depends: wasta-wine but it is not going to be installed
E: Unable to correct problems, you have held broken packages0 -
Bill Anderson said:
The following packages have unmet dependencies:
wasta-logos-setup : Depends: wasta-wine but it is not going to be installed
E: Unable to correct problems, you have held broken packagesBill, can you try to install wasta-wine directly so we can see what (sub) dependency has issues?
sudo apt install wasta-wine
Then keep manually trying each package that gives an error saying it is not going to be installed so we can build a list of packages that are not able to be installed, thus leading to wasta-logos-setup not being able to be installed.
Rik
0
