silverblue-site VS AppImageKit

Fedora; from its 'flagship' Workstation, to their glorious Spins and their Immutable Desktops

Fedora Silverblue - pretty well-known at this point, but it’s championing immutability

Couldn't have said it better!

An example of an installable immutable OS is Fedora Silverblue. Notably, you can change the "distro" flavor of Silverblue to try out KDE and then just flip back to Gnome. Each change is seen as an "update" that just moves you over to the new GUI. The article below explains a bit more.

I guess something like Fedora Silverblue might offer you something (to paraphrase) "stupid proof". For example, in this case the rpm-ostree rollback command would have been sufficient. Disclaimer: rpm-ostree builds images, therefore it's by necessity slower than apt. Futhermore, until this change is merged and deployed you'd have to reboot for the changes to apply. You might want to look into Distrobox as well, perhaps it can solve your problems without having to change your distro.

However, I'll add one more that I'm especially fond of. It's one of the most 'stable'\1]) Linux desktop systems\2]) without sacrificing access to the latest kernel-updates and packages. It comes bundled with everything\3]) necessary for productivity right out of the box and is built on top of the fundamentals laid by Fedora's Immutable Desktops. Allow me to introduce uBlue; I know that I'll undersell it regardless, so I recommend you to check the provided link instead.

the immutable desktops offered by Fedora; which would be Silverblue, Kinoite and Sericea (special mention goes to uBlue)

OS: Fedora Silverblue

What you're looking for sounds like AppImages (https://appimage.org/) . I have only used them while downloading games from itch.io, etc. (since i prefer package managers) but they seem to work out of the box on popular distros.

Ideally a new instance of the application is installed for each user. This also provides better isolation if one user upgrades/removes/breaks their application instance. I, for one, have really come around to the AppImage model [0] in the last couple of years.

[0] https://appimage.org/

I found a similar issue on github and tried this solution but still getting the same error .

There is AppImage[1], which packs a lot of stuff into a SquashFS filesystem, appends it to the executable, so everything is in one file.

[1] https://appimage.org

Nah i think yall just hating appimage. Real gold standard.

Although I haven't used plugins feature myself yet, this does sound like the perfect use case for them. Not every patient needs to access every single source. With plugins you can load only the source (or few sources) that they actually need. You can still use something like https://appimage.org/ to give them "a single binary", but will actually contain your slim binary and all the plugins.

```dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information```

This doesn't look like a squashfs image. Cannot mount AppImage, please check your FUSE setup. You might still be able to extract the contents of this AppImage  if you run it with the --appimage-extract option.  See https://github.com/AppImage/AppImageKit/wiki/FUSE  for more information open dir error: No such file or directory

appimages. Appimages are similar to flatpaks, exept that they are a file you download and double click to run. Think of them as portable softwares like windows has (portable apps). They are sandboxed too. You can learn more about appimages here