I am late as well to the new package formats party . I currently use LibreOffice-7.2.5-x86_64.AppImage from the website. The applications I need/use are Calc and Writer and both work well. Haven't hit any show stoppers yet.

What I have observed so far with LibreOffice-7.2.5-x86_64.AppImage on Slackware 15.0:
Calc - works
Writer - works
Math - works
Base - works
Impress - doesn't launch - no error displayed
Draw - Launches displays error dialog about missing libsdlo.so and exits.

As an experiment, I tried out my first AppImage, after upgrading to Slackware 15.0, in mid-march, and now I'm up to three (see below). I used to build Audacity (and other applications) myself and fight through dependencies and what not, but with the AppImage, none of that was needed, it just worked.

audacity-linux-3.1.3-x86_64.AppImage
KeePassXC-2.6.6-x86_64.AppImage
LibreOffice-7.2.5-x86_64.AppImage

1 members found this post helpful.

@random_guy,
Thanks for the information!

I get the same error even though the file exists. Not sure if it's in the wrong directory.

The libsdlo.so issue has been discussed before, more than once. See e.g.:
https://www.linuxquestions.org/quest...hi-4175635470/

No errors when built from Chris.Willing's LibreOffice slackbuild on SBO.
HTH
john

2 members found this post helpful.

Yeah, same here. Why bother downloading, compiling, packaging, etc etc, when you can have it all within a single file.

The only negative thing about the AppImage, as far as I can tell is that one of the apps it contains requires avahi... I used sbopkg to install this and everything seems to work. Some people don't like avahi, because of it's author... But just having it sit there for this purpose won't cause any harm.

I really like having a single binary file under /usr/local/bin which everyone can use and can be upgraded in seconds, and, despite its size works just as fast as a native installation.

2 members found this post helpful.

The avahi issue has been discussed before; a simple fix that satisfies libreoffice is to create dummy .so files as mentioned in this post: https://www.linuxquestions.org/quest...8/#post5955765

Obviously the remote control functionality won't work then though...

3 members found this post helpful.

Totally agree, the convenience of single binary file that just works, blew me away. AppImages do tend to be larger but with the large drives available today
the overhead is well worth it to me.

1 members found this post helpful.

I guess you're all not Slackware users then. So readily accepting binary code compiled on an unnamed OS by anonymous people.
Who knows what's inside? Well at least foreign code like Avahi. Good luck cobbling together your hacks to make it "work". Give me a SBo anytime. Or a Slackware package.

2 members found this post helpful.

That's funny! Heh.

Even funnier: You'll happily take the source code, but not a binary compiled by the same people who wrote it? Well, I hope you read every line of that source code... Because who knows what's in there???

No, avahi is not in the AppImage. It is a dependency for one of the apps. I think the presentation one. You don't need it to do word processing or spreadsheets.

2 members found this post helpful.

Brilliant! I verified that it works by removing the avahi package first (which I didn't really want anyway).

Quoted here, in full for posterity:
What I did was to run those two gcc commands under the /usr/local/lib64 directory, then "ldconfig". Boom "Impress" loads. Couldn't care less that I can't control it remotely.

2 members found this post helpful.

I'm not sure how it goes against of Slackware cult. AppImage or Flatpack are great and convenient things for desktop applications, because they are totally isolated from core system.

Did you intend to use the word "culture" there?

One of the great things about Slackware is that it doesn't force you into any particular way of doing things. If you want to spend hours/days compiling & installing stuff, you can go for your life.

For those of us who actually like to use our computers instead of constantly working on them, AppImages and containers work fine too.

Thanks to Slackware's design, any combination of the above can be expected to work.

With that said, one can't help but think that the mentality of not using "someone else's binary" is more than just a little bit silly... especially when said binary comes from the same people who wrote the source code. The end user would certainly not be able to distinguish between LibreOffice compiled from source and the AppImage.

I am sure you wanted to say something here but your crooked use of the English language makes it hard to see.

If that total isolation were true then Slackware people using these appimages would not suffer from the reported Avahi problem, right?
Appimages, containers, they are all dependent on the host operating system, there's nothing mysterious at work, The application is bundled with all its dependencies (or so these developers think when they never used Slackware) and run as a process on the OS. They use resources from the OS that the kernel's capabilities will isolate for them from the rest of the OS. If you want total separation/isolation, use a Virtual Machine.

Wrong.