makes your Linux desktop AppImage ready™
Integrate AppImages to your application launcher with one click, and manage, update and remove them from there. Double-click AppImages to open them, without having to make them executable first.
AppImageLauncher plays well with other applications managing AppImages, for example app stores. However, it doesn't depend on any of those, and can run completely standalone.
😃 Info on how to install and use AppImageLauncher on the wiki.
AppImageLauncher is a novel and unique solution of integrating with the system. It intercepts all attempts to open an AppImage to provide its integration features.
Being the launcher for AppImages, AppImageLauncher can control how the system treats AppImages. It integrates them into the system, provides helpers for updating or removing AppImages, and a lot more.
On their first execution (i.e., if they have not been integrated yet), it displays a dialog prompting the user whether to run the AppImage once, or move it to a predefined location and adding it to the application menus, launchers, etc.
This core feature allows you to integrate AppImages you download into your application menu or launcher, to make it easier for you to launch them. It also takes care of moving them into a central location, where you can find them later. Furthermore, it sets up the update and removal entries in the launcher for you.
AppImages use the term "desktop integration", as they're not "installed" in the traditional sense. They remain single, self-contained executable files. AppImageLauncher and other tools extract and patch the desktop entry as well as the related icons into the relevant locations. More information on desktop integration can be found in the AppImage docs.
After desktop integration, the context menu of the AppImage's entry in the application launcher will have an "Update" entry that launches a little helper tool to apply updates.
Click the "Remove" entry in the context menu in the application launcher and the removal tool will ask you to confirm. If you choose to do so, the desktop integration is undone, and the file is removed from your system.
The packages ship with a CLI tool called ail-cli, providing basic operations in the terminal, for automation in scripts etc. As of February 2020, only integration and unintegration are supported. More features planned!
From version 1.4.0, there's a Lite edition of AppImageLauncher.
It provides all of AppImageLauncher you can get without having root access to your computer. AppImageLauncher Lite is shipped as an AppImage, which can be installed by users from the command-line.
Enter ./appimagelauncher-lite...AppImage install. in a terminal, and it integrates itself in the users' home directory.
Traditional packages are highly recommended if possible, as they provide many more features and provide a much better overall experience.
Note: if you're interested in a GUI installer, please consider sending a pull request. More information in #243.
Currently, desktop environments consider executables a security risk, and would rather have users use the app stores they include.
The ability to easily run them, however, isn't all that's needed to provide a good AppImage desktop experience. Making them accessible from the application menus and launchers is a level of "desktop integration" that can't be provided by the AppImages themselves properly (even though some AppImages ship with a "desktop integration script" prompting the user to do so). There are too many impliciations requiring external software, especially regarding cleanup and removal of AppImages. (If applications are simply made executable, they're still spread all over the users' personal files and folders.) The average user will not find a "Downloads" directory full of AppImages with cryptic filenames friendly.
Therefore, system-side ways have been developed to perform the desktop integration.
One of the first solutions was appimaged, a daemon users could install to perform everything automagically in the background, without notifying the user in any way.
It scans a predefined set of directories including ~/Downloads and ~/.bin, making recognized AppImages executable and then performing the desktop integration. Those operations and monitoring produced a lot of file I/O, so were rather inefficent. Also, many users don't like the lack of control. The approach also opens attack vectors and thus can be considered a security hazard, as a vulnerability discovered in appimaged recently has shown.
- DLN Xtend 11h
- DLN Xtend 14
- Linux Uprising (English)
- Linux-OS.net (Spanish)
- Same article also available here.
- Edvaldo Brito (Portuguese)
- przystajnik (Polish)
- Linux Mint Magyar Közösség (Hungarian)
- FreeYourDesktop (English)
- Please note that AppImageLauncher could not be "installed" via AppImage at that time, only recently was a Lite version added, that now can be installed from an AppImage (more info to follow.)
- Pardus forum (Turkish)
- Linux Team Vietnam (Vietnamese)
- Contains a few wrong assumptions: as soon as AppImageLauncher is installed, you do not have to make AppImages executable, you can just double-click them (or otherwise open them, e.g., from your file- or web-browsers' downloads).
- RealLinuxUser (English)
- manjaro.site (English)
- CubicleNate's Techpad (English)
- See also: CubicleNate's Techpad
- CHRIS R MILLER (English)
- doLys Forum (French)
- LINUXUSER (Greek)
AppImageLauncher integrates deeply into the system. Therefore, an installation via native system packages is the preferred way to install AppImageLauncher. This way, AppImageLauncher's package can perform the necessary steps to have your system use it for all AppImage invocations.
Compatibility table (likely incomplete.) Please, feel free to open PRs to add distributions.
| Release filename | Build system | Compatible distributions (incomplete) |
|---|---|---|
appimagelauncher-<version>.xenial_(amd64,i386).deb |
Ubuntu Xenial | Ubuntu Xenial (16.04), Debian Stretch (9), Netrunner 17.01 |
appimagelauncher-<version>.bionic_(amd64,i386).deb |
Ubuntu Bionic | Ubuntu Bionic (18.04), Ubuntu Disco (19.04), Ubuntu Eoan (19.10) and newer, Debian buster (10) and newer, Netrunner 19.01, 19.08 and newer, LMDE 6 "Faye" |
appimagelauncher-<version>.disco_(amd64,i386).deb |
||
appimagelauncher-<version>.eoan_(amd64,i386).deb |
||
appimagelauncher-<version>.buster_(amd64,i386).deb |
||
appimagelauncher-<version>.(i386,x86_64).rpm |
Ubuntu Xenial | openSUSE Leap 42 and newer, possibly openSUSE Tumbleweed, SUSE Enterprise Linux, RHEL 7, CentOS 7 |
- Ubuntu Trusty (14.04) and newer
- Important: Ubuntu Bionic (and newer) broke with the backwards compatibility of its
libcurlpackages, therefore users of these systems need to install the specialbionicpackage
- Important: Ubuntu Bionic (and newer) broke with the backwards compatibility of its
- Debian stable (Jessie, 8) and newer
- Netrunner 17 and newer
- openSUSE Leap 42 and newer
- openSUSE Tumbleweed
The installation of packages on systems with a set of packages similar to one of the listed ones (e.g., Linux Mint, Fedora, etc.) should work as well.
Note: For Ubuntu 19.04 and newer as well as derivatives, there's two PPAs (personal package archives) available providing a simple way to install and update AppImageLauncher (thanks Peter Jonas for creating and maintaining them):
- stable (provides all releases): https://launchpad.net/~appimagelauncher-team/+archive/ubuntu/stable
- daily (latest and greatest but possibly unstable): https://launchpad.net/~appimagelauncher-team/+archive/ubuntu/daily
Manjaro and Netrunner Rolling users can install AppImageLauncher with a distribution-provided package called appimagelauncher.
Arch Linux, Manjaro, Antergos and Netrunner Rolling users can use AUR to install AppImageLauncher by installing appimagelauncher or appimagelauncher-git (possibly broken, see #574) (thanks @NuLogicSystems for setting up the build).
Other systems derived from the listed ones, such as for instance Linux Mint (Ubuntu), should support AppImageLauncher as well. If they don't, please don't hesitate to create an issue.
Note: Feel free to request support for other distributions by opening an issue.
Build instructions in BUILD.md.
Technical details about how AppImageLauncher registers itself on this wiki page.
