Bookworm - MasterPDF.AppImage error (SOLVED by Fredx's method)

[soniabu]

I solved with the Master PDF prepared by the great Fredx181 (which works very well with Bookworm);
follow this link. viewtopic.php?p=8674#p8674
sonia.

----------------------
OLD MESSAGE
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------!
|
|
hello everyone I try to use some AppImage I used before and among those that I still can't start is MasterPDF( downloaded from the Apprepo.de site).
The image I am merging describes the error.

Since I can't find the library in Synaptic, I found a Debian 11 specific .deb file (Bullseye) but before
installing it I would like some advice from you on whether to do so.

sonia

[fredx181]

libsane1: should be able to install it with apt or synaptic in Bookworm : https://packages.debian.org/bookworm/libsane1

[soniabu]

thanks Fred.
This time I found libstdc6 installed in Synaptic but maybe it doesn't match the version?
I tried after updating and upgrade but nothing changes. I think libstdc6 is not up to date ...

[fredx181]

This cannot be fixed, Im afraid, I think the Appimage is too old for Bookworm (or the GLIBCXX version in Bookworm too new, depends how you look at it).

[soniabu]

This cannot be fixed, Im afraid, I think the Appimage is too old for Bookworm (or the GLIBCXX version in Bookworm too new, depends how you look at it).

I followed the installation of your Master pdf squashfs file (viewtopic.php?p=8674#p8674) and it works great on Bookworm too.
Well Fred, I'm glad I tried it.
thx Fred.
sonia

[mikewalsh]

@soniabu :-

Sonia, I suspect you're going to have this problem with most of the AppImage-based portables I produce.

You're using the very newest 'testing' version of Debian. As in so many of these situations, it's put together to expect to find - and use! - the very newest of everything.

Many of these AppImages are either ones I've found myself, or in some cases, using Fred's scripts, I've built them from the standard packages. But in every case, most are now 3-4 years old.....and this often means that bang-up-to-date OS releases won't function with them any longer (despite the 'myth' of 'backwards-compatibility').

It's perhaps my fault, in a way. I'm one of those that never, EVER uses brand-new releases. Every resident of my kennels is at least 2-3 yrs old, since I prefer long-term support (LTS) releases. Thus, I don't have any "up-to-date" OSs to test with; I'm one of those that doesn't HAVE to have the very newest of everything. I'm just not that obsessive about it!

About the only place where you'll find sufficiently new AppImages is the apropos.de site. I believe the guys who supply most of these are using Arch Linux.....a 'rolling' release that runs the bleeding-edge versions of everything the instant it comes out.

That's NOT for me, I'm afraid! Sorry an' all that...

Mike.

[backi]

Hi @mikewalsh :

You probably meant https://apprepo.de/.......instead of apropos.de

Good Hint ......fine !

[mikewalsh]

Hi @mikewalsh :

You probably meant https://apprepo.de/.......instead of apropos.de

Good Hint ......fine !

Oops! Yup, sorry.....my bad. Thanks for the correction, mate. I did that one off the top of my head; knew it was summat similar....

Mike.

[fredx181]

.....
But in every case, most are now 3-4 years old.....and this often means that bang-up-to-date OS releases won't function with them any longer (despite the 'myth' of 'backwards-compatibility').
...

Yes, you are right of course that on very new systems, appimages from few years ago won't work in some cases.
But it depends, I'd say that basic core system libraries such as libstdc++.so.6 (see above) shouldn't be part of an appimage or any portable setup, it can easily cause errors.
Also, as example for some of your portables, often running the "LAUNCH" script doesn't work for me, but then the "LAUNCH-NL" (no included libs in portable LD_LIBRARY_PATH) often works OK.