Excludelist for files/directories to run AppImages without AppImageLauncher

[catcherxuefeng]

AppImageLaunche was work good at my pc , but i have some appimage apps , want run it without AppImageLaunche control . Can i configure it ？

[catcherxuefeng]

like a whitelist

[jpenguin]

export APPIMAGELAUNCHER_DISABLE=true

before you launch it

[sigzegv]

I think a better idea is to implement an exclusion list, for example if I install an appImage from my package manager, the package manager already handles desktop integration and updates, I don't want appimagelauncher to handle this file because it may cause a duplicate (the app will not be moved but copyied from it's original path because it's not authorized), and I cannot update the actual desktop runner because it should not be done.

[jmknoble]

I'll chime in here. The MuseScore AppImage has an issue where it doesn't play well with AppImageLauncher. In order for it to work, the AppImage requires that it be "installed" instead, which places resources under ~/.local/{bin,share,...}. The AppImage itself ends up in ~/.local/bin/.

It would be beneficial if I could tell AppImageLauncher to ignore files or directories in a way similar to .gitignore or Syncthing's .stignore. Then I can at least use AppImageLauncher for the things that work well, but avoid problems with AppImages like MuseScore that are imperfect.

I'm trying to use AppImages because a recent Ubuntu update broke some of my snaps, and I'm trying to find ways to get applications that Just Work:tm:. (Stil trying...).

[TheAssassin]

@jmknoble MuseScore should add X-AppImage-Integrate=false to their desktop file IMO.

[TheAssassin]

Technically all AppImages will always be run with AppImageLauncher. The environment variable just suppresses the dialog, but that's it. There's certainly the need for an excludelist of some kind.

[Moilleadoir]

I’d also like to exclude directories. If my package manager installs in /usr/bin I really don’t need the AppImage moved and if I edit the .desktop file it may just be replaced on update anyway.

Edit: also X-AppImage-Integrate=false doesn’t seem to work, but adding env APPIMAGELAUNCHER_DISABLE=true to the Exec= does.

[begin-theadventure]

Third tab: Exclude

AppImages to exclude +- Directories to exclude +-

Edit: ~~And it should automatically exclude /usr/bin~~ Scratch that, ideally all root directories should be automatically excluded.

This issue's also a duplicate of https://github.com/TheAssassin/AppImageLauncher/issues/441.

[cbartondock]

Just want to second this, there are certain tools that install appimages and don't expect them to be moved.

[Nyalnara]

Just want to second this, there are certain tools that install appimages and don't expect them to be moved.

Came looking through the issues to mention this too, some Steam games are distributed as appimages, and some of those are packaged in such a bad way that they need external resources they won't find anymore if moved, which breaks everything. Those aren't launched through a .desktop file so the work-around provided in #441 won't work. Adding APPIMAGELAUNCHER_DISABLE=true to the launch options will, but I cannot know before launching it if a game is an appimage, whereas I know where I did put my steam folders and could just add those to the ignoreFoldersList if it existed as part of the initial config.

[ardhill]

I just wanted to add my agreement to this suggestion.

I use Joplin a lot and it has it's own integration that works very well, even adds that app into my Desktop Applications Menu. If AppImage Launcher integrates Joplin, it gets messy. I would much rather have AppImage Launcher Ignore it.

APPIMAGELAUNCHER_DISABLE=true Isn't a great workaround for Joplin