How to install Bibletime in Fossapup? [SOLVED]

[Subito Piano]

Hmm...does anyone know how to install Bibletime in FossaPup without downloading 150MB+ of dependencies through PPM?

I've tried about all the pet and sfs versions I can find, even installing on a virgin install of Fossa (i.e., pfix=ram). No go. On the virgin install I get the following:

Code: Select all

root# ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
bibletime-bin: error while loading shared libraries: libpng14.so.14: wrong ELF class: ELFCLASS64

FYI, I do have the 32-bit compatibility sfs running. I've tried install with the required sword, clucene, bibletime, and qt lib pets.

Thoughts always appreciated.

[mikeslr]

Just to let you know you aren't being ignored. Your post reminded me that I no longer have a working version. When I ran into a problem other than the one you reported I tried under other Puppies. I've been able get bibletime running to under both Xenialpup64 and Bionicpup64 after finding some libraries. And the 32-bit Windows program runs under Wine (but hangs sometimes).

I have an idea which I'm following up.

[mikeslr]

Well, my idea didn't work. The problem I had run into is that Bibletime required libraries inconsistent with those otherwise used under fossapup64. The idea I had was to create a portable which contained the libraries Bibletime needed specifying that those should be used. It should have worked. But I'm no coder.
I suspect someone who is will have to look into this problem.

Maybe this will help. I originally created an SFS using fossapup64's Puppy Package Manager and packing then with PaDS, https://www.forum.puppylinux.com/viewtopic.php?t=933. IIRC, I had to hunt up a couple of libs which ListDD reported missing. The following screenshot show all required libs.

bibletime-libs.png (71.96 KiB) Viewed 1487 times

Looking at it, I think all that was missing was lsword-1.8.1.so.

SFS-loading the bibletime.sfs produced /usr/share/applications/bibletime.desktop and so a menu entry. I had selected x-personal using PaDS. So it showed up on the Personal Submenu. It could not be started from the menu, by click the desktop file, or by clicking the executable: /usr/bin/bibletime.

However, when I tried to run it from a terminal [Right-Click /usr/bin/bibletime > Run-in-terminal] in order to try to find out what was going wrong, the application started. The terminal reported nothing. I don't know what's wrong with starting it normally; and don't know how to investigate further.

The application comes without BOOKs, and without them it's not very useful. They have to be downloaded by the application. Using the version under Wine I previously mentioned, it took over an hour to download everything offered except 'Daily Devotionals'. I couldn't figure out where they were stored; so can't copy them.

In its current state I don't trust the application under fossapup64. Certainly not sufficiently to tie-up my computer downloading Books.

[Subito Piano]

Mike, that's great! Sounds like you invested a lot of time -- much appreciated. It's late here, but I plan to try it tomorrow and report back. I've used BibleTime for a decade and a half, no issues I couldn't solve until now.

FossaPup has great features but I've had a few issues with it. You've seen one or two other posts by me about snags encountered with FossaPup; it seems as if some underlying structures have changed, as Barry recently pointed out. Not his fault or Phil's, that's just life. :-/

As for your first post, this is the Puppy forum! I've NEVER felt ignored here. Quite the opposite, ppl. are very eager to assist others. I only wish I had more time to give back by helping answer more posts.

[mikeslr]

Here's what I did. Create a folder --I named mine 'more', without the quotes-- in /root, then used PPM>options to set that as the download directory. Otherwise PPM just downloads to /root and creates a mess. In PPM's Search I typed in bibletime and selected all applicable files. IIRC, it didn't find one, asked to try again, which I ok'd. Then it thought it had everything.
Moved all the debs into a folder named 'bibletime_fossa64-2'. With PaDS from here, https://www.forum.puppylinux.com/viewto ... 6355#p6355 already SFS-loaded, Right-Clicking the folder offered 'Combine-to-SFS'. Chose that and an SFS was produced in /root. Move it.. If you test it from there when you close it it will be deleted.

SFS-loading the bibletime.sfs enabled me to check what libraries were missing. File-browse to IIRC /usr/bin and look for it. There may also be a file named something like bibletime-edit? At any rate, right-click them and select listDD from the pop-up menu. If you don't have it, you'll find it here, http://www.smokey01.com/radky/. IT IS INVALUABLE IN DIAGNOSING PROBLEMS and will work with every Puppy.

I worked on it early in the day, then worked on Xenialpup64 and Bionicpup64. So I'm hazy about what was missing. I think it was just the libsword-1.8.1.so AND YOU CAN AVOID THAT by specifically having PPM download it at the same time as the other bibletime related files. But if I'm mistaken let me know. The screenshot shows some symlinks. I may have had to download the latest version and create symlinks to the latest named for what bibletime was looking for. I still have them and can upload them.

There's another problem which might pop-up. Ubuntu often puts some libraries in one of the folders named something like lib/gnu_linux64. Puppys' can't find those folders. These have to be moved to /usr/lib. Examine your structures at the top most level and under /usr, /usr/local. At any rate, obviously you can't move files in an SFS. What you have to do is mount [Left-Click] the SFS, select View, then copy the files into another folder. That's why the original folder was named bibletime_fossa64-2. The next folder was named bibletime_fossa64-2.11 reflecting the name of the binary.

Before Right-Clicking and dir2sfs that folder, you can check /usr/share/bibletime.desktop in a text editor to see if any changes are necessary: points to an actual pixmap, doesn't include u% or f% in the Exec= argument.

[bigpup]

I installed it using PPM.
Just let PPM download and install.
I do not have PPM set to save anything it downloads.
Set to just install.
Sure it downloaded some dependencies, but they are needed.
It is an older version than the latest one that can be found at their web site.
But it works with no issue, so far.
.

Screenshot(1).jpg (93.3 KiB) Viewed 1470 times

.
.

[mikeslr]

I wonder why "Download all (Packages and dependencies)" missed libsword-1.8.1.so?

[bigpup]

It seems to have installed it for me with PPM, when I installed Bibletime.

From user installed packages, info for installing bibletime.

bibletime_2.11.2|bibletime|2.11.2|11build1|BuildingBlock|2883K|pool/universe/b/bibletime|bibletime_2.11.2-11build1_amd64.deb|+libc6&ge2.29,+libclucene-core1v5&ge2.3.3.4+dfsg,+libgcc-s1&ge3.0,+libqt5core5a&ge5.12.2,+libqt5gui5&ge5.6.0,+libqt5printsupport5&ge5.0.2,+libqt5webchannel5&ge5.6.1,+libqt5webenginewidgets5&ge5.7.1,+libqt5widgets5&ge5.11.0,+libqt5xml5&ge5.0.2,+libstdc++6&ge4.9,+libsword-1.8.1,+bibletime-data&eq2.11.2|bible study tool for Qt|ubuntu|focal|

I looked at the file libsword-1.8.1.so
It seems to be dated for the time I did the Bibletime install.

Maybe you just got a bad download
Internet hiccuped on you
I know, you know, that if there is not enough free space in the save, for the download.
PPM will not tell you and make it look like it got everything, when it did not.

[Subito Piano]

Not getting to it today, Mike, but a question for Bigpup: are you saying you downloaded BibleTime and dependencies from PPM? That's a 150+MB download, which I was trying to avoid. The BibleTime pets and SFS files to date have been way smaller

[bigpup]

Yes from PPM.
Well, with the Bibletime in PPM, being from a Ubuntu repository, and compiled for Ubuntu.
That 150MB download is it and the dependencies, that are in Ubuntu, that Puppy does not have.

It does have a bunch of different languages support stuff in it.
But it is only about 4 or 6 MB.
Puppy pets or SFS usually only have the English stuff in them.

If a Puppy pet or SFS Bibletime is compiled for Puppy.
The compile is more for what is in Puppy, for dependencies.
So, they should not need to add any or very few.

[Subito Piano]

Hmm -- yeah. The sfs versions I have are about 40MB. sigh....

I'm assuming Mike's method takes up less space, hoping to try that and find out. Right now I've gotta work on my bathroom subflooring.

[OscarTalks]

I managed to compile the latest bibletime-3.0.3 in FossaPup along with latest sword-1.9.0 (for libsword)
It seems rather unstable though so I won't upload it anywhere.
I think the problem is that it depends on Qt5 and some elements of that are missing in FossaPup (modules, plugins and stuff like that).
So not just a case of adding missing libs from error messages, it would take time to experiment with it. I managed to fix one segfault but then as I continued testing, another cropped up.

It is always going to be quite big whatever you do, plus you then have to download the "works" to somewhere, so space is needed for that. Earlier versions of bibletime depend on Qt4 but that still includes the large libqtwebkit so I reckon the PPM route is not a bad option if it works and if it is a program that you really want.

[Subito Piano]

OK, I see. Yeah, too many times I've chased libs down only to have more pop up, as you (Oscar) mention. It's not that I don't have space for the full PPM download, but there's less room on this Mac than on my T60. I want to conserve -- plus it's the principle here; I'm rather annoyed by the huge size of a couple of the dependencies -- libqt5webengine core & data total 138MB!

This all caused me to give TheWord another shot under WINE. I know it's more comprehensive than BibleTime, but in the past I opted to stay with BT because of the interface, plus there may have been an issue with font clarity under WINE. However, there is currently no font issue running it in Fossa, I can rearrange it to my liking, it includes Thayer and other works, plus I purchased a module for it, my preferred translation, years ago, which in not available in BT. So -- we'll see.

So, first, thank you to all; second, Mike, I still plan to try your idea and post back before I leave for the ADKs Wednesday.

[OscarTalks]

Strictly for testing if anyone is interested
I had another go at compiling everything
bibletime-3.0.3
sword-1.9.0 built from source and included
clucene-core-2.3.3.4 built from source and included
A few Ubuntu Qt5 components included
Packaged as .pet or .sfs it is under 6 megs, but installed size is 26 megs in total
Package is for FossaPup only

I installed a couple of bibles and one map thing as my "bookshelf works" and it seemed OK
There may be some actions that make it crash, I didn't try all of the functions and options.
If it happens it may be missing Qt5 stuff such as qml-module packages relating to QtQuick

Anyway, menu entry is in the Personal section, but run from terminal with the command bibletime to see warnings, errors and segfaults
The manual and how-to should be working (english only), they open in your browser.
Uploaded here:-
http://smokey01.com/OscarTalks/bibletim ... -fossa.pet
http://smokey01.com/OscarTalks/bibletim ... -fossa.sfs

[mikeslr]

Subito Piano, it won't take up less space on your storage medium*; just less space in a SaveFile if you were using one. That and an SFS uses NO Ram when not loaded.

OscarTalk's builds are the way to go. Thanks, OscarTalks.

* Well, on second thought, as both a SaveFile and a SaveFolder are not compressed while an SFS is, it will take less space on your storage medium. Still, OscarTalks compiled specifically for Fossapup64 builds are to be preferred even if they had been the same size.

[Subito Piano]

SO close!!

Fonts are rendering white on white, even when I changed GTK themes. This is true for both the pet and sfs versions.

I had a similar issue with BibleTime way back in 2001 using Mint 9, but the issue then was that the icons did not show up; I simply had to install libqt-svg to solve the problem. So after I had the font issue today in Fossa, I opened up PPM and searched through the libqt packages -- but I failed to spot anything that had to do with fonts.

Terminal output:

Code: Select all

root# bibletime
ERROR: corrupt data during decompression

I get the same terminal output for both the pet and sfs versions. (I uninstalled the sfs before installing the pet.)

BTW, HOW did you mange to get that down to 5MB???? (That's pretty much what started this whole Puppy thing anyway -- minimalism!)

[OscarTalks]

OK, thanks for testing. That is a bit peculiar though because having created the .pet I then tested it in a fresh pfix=ram boot of FossaPup and it looked OK, fonts are as expected and no error about data decompression.

There is a setting for choice of font in the Preferences dialog, but that was set to DejaVu Sans by default when I looked, so I didn't change it.

I will try re-uploading the packages to smokey01 shortly after posting this, in case the uploads got corrupted. (done)
You could try deleting /root/.bibletime and /root/.sword (folder and contents in both cases) and try restarting bibletime

The package sizes are just what came out of the build process. The tree of files is 26 Megs total and the compression from using dir2pet or dir2sfs reduces that down to what you see. The handbook and how-to documentation files are english only and the pdf versions are turned off so only the html versions are built and included. These do open in palemoon when I click the buttons in the bibletime GUI.

I did another test in a fresh boot of FossaPup, installing bibletime via PPM. It was around 143 Megs in total size and it would not run as root (my build does), it would only run as spot. The documentation did not display, palemoon launched but it didn't seem to know the correct path. I was able to download and view bibles though.

[bigpup]

I did another test in a fresh boot of FossaPup, installing bibletime via PPM. It was around 143 Megs in total size and it would not run as root (my build does), it would only run as spot. The documentation did not display, palemoon launched but it didn't seem to know the correct path.

Strange.
The PPM one I installed is Bibletime v2.11.2 and it runs OK as root.
Documentation displays OK in Pale Moon browser.
It is the latest Pale Moon v31.3.0.1
Pale Moon is set as the default html viewer

All the html doc files are in /usr/share/bibletime/docs

The Fossapup64 9.5 I am using, has been fully updated, using the Quickpet -> Info -> Fossapup updates

This is the .desktop file for Bibletime:

Code: Select all

[Desktop Entry]
Comment=An easy to use bible study tool
Comment[C]=An easy to use bible study tool
Comment[cs]=Snadno použitelný nástroj pro studium Bible
Comment[da]=Et letanvendeligt bibelstudieprogram
Comment[de]=Ein einfach zu benutzendes Bibelprogramm
Comment[et]=Lihtne Piibliuurimise vahend
Comment[fi]=Helppokäyttöinen raamatunlukuohjelmisto
Comment[fr]=Un outil d'étude biblique facile à utiliser
Comment[it]=Un semplice strumento per studiare la Bibbia
Exec=bibletime
Icon=bibletime.xpm
Name=BibleTime 
Name[C]=BibleTime 
Name[cs]=BibleTime 
Name[da]=Bibletime 
Name[de]=BibleTime 
Name[et]=BibleTime 
Name[fr]=BibleTime 
Name[it]=BibleTime 
GenericName=Bible Study Tool
Terminal=false
Type=Application
Categories=X-Personal-education
Keywords=bible;study;religion;literature;education;
DocPath=bibletime/handbook/index.html

This PPM one does have a lot of different languages stuff in it.
.
.

[OscarTalks]

Thanks bigpup, I was wondering how your test compared to mine
Version is indeed bibletime-2.11.2
I admit I did not do the FossaPup updates, just a raw pfix=ram fresh boot. Maybe I will try again when I get a bit of time.
The documentation not displaying in palemoon may be connected to the fact that bibletime was running as spot (thinking about it).
When I tried to start bibletime as root the splash image displayed for a split second and then I got the error about needing --no-sandbox as is usual with chromium derivatives, so I was a bit baffled by that.
Just adding --no-sandbox to the bibletime command did not work.

One thing if anyone is testing my version, I get a crash if I try to open the Settings > Configuration window without first downloading and installing at least one bible or other "work".

[Subito Piano]

Oscar -- following your suggestions:

• renamed /root/.bibletime and /root/.sword (i.e., to /root/.bibletimeOLD, etc.) -- it didn't solve the issue

• renamed /root/.sword and /root/.bibletime – still no good

• renamed /usrshare/bibletime and /usr/sharesword – again, no joy

Next I followed your lead and fired up Fossa in pfix=ram mode -- all worked as it should. So -- the problem is somewhere in my particular configuration, whether it's another program or something in fonts or who knows what. Offhand, I don't know what could be causing this issue; I can play around for a while, but if need be I can reinstall Fossa and add programs and otherwise customize bit-by-bit, checking BibleTime every now and then, until I've got Fossa the way I like.

THANK YOU all for your help, and particularly OscarTalks for making this available in Fossa...

EDIT: I found the issue, it WAS my GTK theme. On inspiration, I switched to Stardust (which ALWAYS works) and then restarted X -- which I didn't do when I switched themes before -- and BT kicked in with clean & clear black-on-white text.