Repository navigation
[Question] How to bypass the launcher #651
Description
Pre-submit checks
- I checked for similar issues beforehand, but could not find any, not even closed ones. I could not add my bug report to any existing issue.
- I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.
Describe the bug
If i have a app i just want to run and not integrate,
there seems to be no obvious way to do that.
I have a appimage file that I like handle myself,
so I like that to be excluded by the appimage launcher.
Then the gui wont come up and it will start automatically.
Expected behavior
Maby have something like ail-cli -run $Appimage to just run a appimage
Steps to reproduce the issue
No response
Screenshots
No response
Distribution and desktop environment
Garuda Linux x86_64
Installed AppImageLauncher version
AppImageLauncher version 2.2.0 (git commit 0f91801), built on 2024-05-25 15:13:12 UTC
List of AppImages you tried
No response
Additional context
No response
Activity
[-]How to bypass the launcher[/-][+][Question] How to bypass the launcher[/+]Lenni-builder commentedon Dec 11, 2024
marvin1099 commentedon Dec 11, 2024
Last time i tryed this this it opened the AppImage launcher as well.
This was one of the first things I tryed to bypass it.
I have not tryied it in a while though.
After I was not able to bypass the launcher I removed it.
If you say this works I will try this with the newest version in the next few days.
Lenni-builder commentedon Dec 11, 2024
AIL hasn't really been updated in years, so that definitely didn't change.
marvin1099 commentedon Dec 11, 2024
In that case I don't think just running the appimage in the terminal works.
I can still see if that works.
Can't hurt to check.
Beep6581 commentedon Dec 28, 2024
Considering the vast amount of AppImages which fail to run due to AppImageLauncher being installed (search the internet for "execv error: No such file or directory"), and considering
AppImageLauncher --appimagelauncher-helpoffers no helpful information, it would be great if you answered here and updated the--appimagelauncher-helpoutput with information on how to bypass AppImageLauncher.midnight-wonderer commentedon Jan 6, 2025
I found this little script on GitHub; it covers my use cases.
https://github.com/un1t/appimage-desktop-entry
The launcher can be bypassed by uninstalling and switching to the script instead.
marvin1099 commentedon Jan 6, 2025
That works, but it also means not installing / uninstalling the launcher.
So its like using the Appimage Launcher Lite.
So its not really bypassing, but its basically what I do nowadays because there seems to be no way to really bypass the launcher (when it is installed) as mentioned.
Beep6581 commentedon Jan 6, 2025
That script does not bypass AppImageLauncher, it very clearly creates a desktop shortcut which launches the AppImage directly, and if you have AppImageLauncher installed and unpatched then that script will not help you one bit.
And obviously uninstalling AppImageLauncher is not bypassing it.
TheAssassin commentedon Jan 6, 2025
There's a lot of wrong information in this thread. Let's clear some things up.
First, I'm defining "bypassing the launcher" as "you won't see the dialog". Your definition may vary, you would have to explain your motivation then. A regular AppImageLauncher installation cannot be "bypassed", as some of its components (mainly the so-called binfmt-bypass) is always used by the kernel. It's a technical limitation of the
binfmt_miscLinux feature.When using a terminal, you can always set
APPIMAGELAUNCHER_DISABLEin your environment to suppress the dialog.If you want to make a specific AppImage never trigger the integration dialog, you need to alter its main desktop file and include one of the flags supported by libappimage, e.g.,
X-AppImage-Integrate=false.To truly avoid using AppImageLauncher's
binfmt_bypass, you can either disablebinfmt_miscresp. the specific AppImagebinfmt_miscintegration manually (which applies system-wide and requires root access), or you can uninstall it and may have to reboot (YMMV, uninstall log messages recommend it if in doubt).