this post was submitted on 12 Mar 2026
137 points (91.5% liked)
Linux
12879 readers
653 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why can’t they do that already? Just choose whichever one you want it’s trivial for me to run whichever as a user
Just not snaps.
AppImage and flatpak are fine though
Whats wrong with snaps? My only "issue" with appimages is i tend to leave them in my downloads folder and lose them
That's why I whenever I download an appimage that I intend to use somewhat regurarly, I typically make a .desktop file for it in /usr/share/applications so it shows up in my app menu or rofi or dmenu or whatever and I don't have to go looking for it. It also helps to have a folder you toss them all into
The snap store is a shit show of security issues.
Forced migration to snaps.
Performance issues.
Proprietary back end.
Slow to install
Slow to start
Eat up RAM
Eat up disk space
They screw up access to devices.
They automatically update themselves without user confirmation.
Fuck snaps. Fuck Canonical.
My issues with snaps are:
I didn't realize, damn.
There's an appimaged daemon you can install that will manage them, and it watches a bunch of folders to integrate appimages with xdg and whatever window manager you've got.
~/Applicationslooks like an easy pick, or~/.local/bin.Appimages you decide to keep you can just move there!
Why do you keep appimages? I don't do that and now I'm wondering if I do something wrong. But I try to install from repos as much as possible.
The appImage is the program. If you don't keep it, you don't have the program.
I'm sorry, I was an idiot. I thought appimages are debs when I made the comment.
I've used one or two tools that only distribute for my system as an appimage or as source code.
I can't always be bothered to set up a compilation environment or deal with removing dependencies.
I only use one or two regularly, but it's nice to have them integrated!
I prefer from the distro's repos, then source, then flatpack, then appimage. Sometimes you have to take what you can get!
snaps are essentially ubuntu-only
I have an ~/app directory for appimages
Ty for both
Gearlevel is a good app to tidy up the Appimage apss.
Correct
Recently I wanted to uninstall $thing. Couldn’t via the package manager. I had forgotten that it wasn’t a native package. So what was it? *scratches head* Flatpak, snap or Appimage? Aw damn, it’s an AppImage. Now where did I put the binary? *scratches head*.
I present to you: https://flathub.org/en-GB/apps/it.mijorus.gearlever
I think it's really funny that it's a flatpak used to manage AppImages
I know right?! ;)
Maybe you would like appimagelauncher. It allows you to define a directory for storing your appimages and you just put them in there and you can automatically launch it from the system menu as if they were installed apps. It also makes removing them easier, since they're all in the same directory and you just remove them and the shortcuts get deleted as well
The fluxer appimage will 'install' itself into /opt/ without your knowledge. I think because it's essentially an electron package similar to stoat, standard notes and discord, large parts of it can self-update without needing to bump the actual package version, but this is really shitty behaviour considering what appimages are designed to do.
In ~/Downloads/
If you can run it, it shouldn't be more than a couple of clicks to find it.
Uhh…should probably get yourself in order because that sounds like a you problem to be completely honest