When a non-reproducible crash occurs in an installed .flatpak package, I can debug it with flatpak-coredumpctl, even if I've solely installed the relevant debug packages after the crash occurred . This is a useful way to retroactive generate a backtrace. With an .AppImage, I see (unofficial) documentation on how to proactively capture a coredump and generate a trace *there* , but that's not useful on another machine, or if unique crashes need to be captured. After all, the unexpected coredumps are the most useful. As an example: ~~~ RokeJulianLockhart@Beedell:~$ coredumpctl debug 63788 PID: 63788 (cursor) UID: 1000 (RokeJulianLockhart) GID: 1000 (RokeJulianLockhart) Signal: 5 (TRAP) Timestamp: Sat 2025-07-05 11:43:55 BST (11min ago) Command Line: /usr/share/cursor/cursor Executable: /usr/share/cursor/cursor Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-appimagelauncher@436976d275e044819cec0d32bc46e97e.service Unit: user@1000.service User Unit: app-appimagelauncher@436976d275e044819cec0d32bc46e97e.service Slice: user-1000.slice Owner UID: 1000 (RokeJulianLockhart) Boot ID: b2f81b0d22aa46928bace43988e7c488 Machine ID: b4f0bef5ffd640fba0ab31fdaa2820b8 Hostname: Beedell.RokeJulianLockhart.desktop.SSV2AY Storage: /var/lib/systemd/coredump/core.cursor.1000.b2f81b0d22aa46928bace43988e7c488.63788.1751712235000000.zst (present) Size on Disk: 1.7M Message: Process 63788 (cursor) of user 1000 dumped core. Module libbrotlicommon.so.1 from rpm brotli-1.1.0-6.fc42.x86_64 Module liblzma.so.5 from rpm xz-5.8.1-2.fc42.x86_64 Module libbrotlidec.so.1 from rpm brotli-1.1.0-6.fc42.x86_64 Module libbz2.so.1 from rpm bzip2-1.0.8-20.fc42.x86_64 Module libdatrie.so.1 from rpm libdatrie-0.2.13-11.fc42.x86_64 Module libjson-glib-1.0.so.0 from rpm json-glib-1.10.6-2.fc42.x86_64 Module libjpeg.so.62 from rpm libjpeg-turbo-3.1.0-2.fc42.x86_64 Module libxml2.so.2 from rpm libxml2-2.12.10-1.fc42.x86_64 Module libgraphite2.so.3 from rpm graphite2-1.3.14-18.fc42.x86_64 Module libXinerama.so.1 from rpm libXinerama-1.1.5-8.fc42.x86_64 Module libXcursor.so.1 from rpm libXcursor-1.2.3-2.fc42.x86_64 Module libwayland-egl.so.1 from rpm wayland-1.23.1-1.fc42.x86_64 Module libwayland-cursor.so.0 from rpm wayland-1.23.1-1.fc42.x86_64 Module libgmp.so.10 from rpm gmp-6.3.0-4.fc42.x86_64 Module libnettle.so.8 from rpm nettle-3.10.1-1.fc42.x86_64 Module libhogweed.so.6 from rpm nettle-3.10.1-1.fc42.x86_64 Module libtasn1.so.6 from rpm libtasn1-4.20.0-1.fc42.x86_64 Module libunistring.so.5 from rpm libunistring-1.1-9.fc42.x86_64 Module libidn2.so.0 from rpm libidn2-2.3.8-1.fc42.x86_64 Module libp11-kit.so.0 from rpm p11-kit-0.25.5-5.fc42.x86_64 Module libcrypto.so.3 from rpm openssl-3.2.4-3.fc42.x86_64 Module libkeyutils.so.1 from rpm keyutils-1.6.3-5.fc42.x86_64 Module libkrb5support.so.0 from rpm krb5-1.21.3-6.fc42.x86_64 Module libcom_err.so.2 from rpm e2fsprogs-1.47.2-3.fc42.x86_64 Module libk5crypto.so.3 from rpm krb5-1.21.3-6.fc42.x86_64 Module libkrb5.so.3 from rpm krb5-1.21.3-6.fc42.x86_64 Module libblkid.so.1 from rpm util-linux-2.40.4-7.fc42.x86_64 Module libcap.so.2 from rpm libcap-2.73-2.fc42.x86_64 Module libXau.so.6 from rpm libXau-1.0.12-2.fc42.x86_64 Module libdrm.so.2 from rpm libdrm-2.4.125-1.fc42.x86_64 Module libpixman-1.so.0 from rpm pixman-0.46.2-1.fc42.x86_64 Module libxcb-shm.so.0 from rpm libxcb-1.17.0-5.fc42.x86_64 Module libxcb-render.so.0 from rpm libxcb-1.17.0-5.fc42.x86_64 Module libXrender.so.1 from rpm libXrender-0.9.12-2.fc42.x86_64 Module libfreetype.so.6 from rpm freetype-2.13.3-2.fc42.x86_64 Module libpng16.so.16 from rpm libpng-1.6.44-2.fc42.x86_64 Module libthai.so.0 from rpm libthai-0.1.29-10.fc42.x86_64 Module libwayland-client.so.0 from rpm wayland-1.23.1-1.fc42.x86_64 Module libtinysparql-3.0.so.0 from rpm tinysparql-3.9.2-1.fc42.x86_64 Module libcloudproviders.so.0 from rpm libcloudproviders-0.3.6-1.fc42.x86_64 Module libXi.so.6 from rpm libXi-1.8.2-2.fc42.x86_64 Module libepoxy.so.0 from rpm libepoxy-1.5.10-9.fc42.x86_64 Module libgdk_pixbuf-2.0.so.0 from rpm gdk-pixbuf2-2.42.12-10.fc42.x86_64 Module libcairo-gobject.so.2 from rpm cairo-1.18.2-3.fc42.x86_64 Module libfribidi.so.0 from rpm fribidi-1.0.16-2.fc42.x86_64 Module libfontconfig.so.1 from rpm fontconfig-2.16.0-2.fc42.x86_64 Module libpangoft2-1.0.so.0 from rpm pango-1.56.3-1.fc42.x86_64 Module libharfbuzz.so.0 from rpm harfbuzz-10.4.0-1.fc42.x86_64 Module libpangocairo-1.0.so.0 from rpm pango-1.56.3-1.fc42.x86_64 Module libgdk-3.so.0 from rpm gtk3-3.24.49-2.fc42.x86_64 Module libgnutls.so.30 from rpm gnutls-3.8.9-3.fc42.x86_64 Module libavahi-client.so.3 from rpm avahi-0.9~rc2-2.fc42.x86_64 Module libavahi-common.so.3 from rpm avahi-0.9~rc2-2.fc42.x86_64 Module libgssapi_krb5.so.2 from rpm krb5-1.21.3-6.fc42.x86_64 Module libsystemd.so.0 from rpm systemd-257.7-1.fc42.x86_64 Module libplds4.so from rpm nss-3.112.0-1.fc42.x86_64 Module libplc4.so from rpm nss-3.112.0-1.fc42.x86_64 Module libselinux.so.1 from rpm libselinux-3.8-2.fc42.x86_64 Module libmount.so.1 from rpm util-linux-2.40.4-7.fc42.x86_64 Module libz.so.1 from rpm zlib-ng-2.2.4-3.fc42.x86_64 Module libgmodule-2.0.so.0 from rpm glib2-2.84.2-1.fc42.x86_64 Module libffi.so.8 from rpm libffi-3.4.6-5.fc42.x86_64 Module libpcre2-8.so.0 from rpm pcre2-10.45-1.fc42.x86_64 Module libatspi.so.0 from rpm at-spi2-core-2.56.2-1.fc42.x86_64 Module libasound.so.2 from rpm alsa-lib-1.2.14-3.fc42.x86_64 Module libudev.so.1 from rpm systemd-257.7-1.fc42.x86_64 Module libxkbcommon.so.0 from rpm libxkbcommon-1.8.1-1.fc42.x86_64 Module libxcb.so.1 from rpm libxcb-1.17.0-5.fc42.x86_64 Module libexpat.so.1 from rpm expat-2.7.1-1.fc42.x86_64 Module libgbm.so.1 from rpm mesa-25.0.7-2.fc42.x86_64 Module libXrandr.so.2 from rpm libXrandr-1.5.4-5.fc42.x86_64 Module libXfixes.so.3 from rpm libXfixes-6.0.1-5.fc42.x86_64 Module libXext.so.6 from rpm libXext-1.3.6-3.fc42.x86_64 Module libXdamage.so.1 from rpm libXdamage-1.1.6-5.fc42.x86_64 Module libXcomposite.so.1 from rpm libXcomposite-0.4.6-5.fc42.x86_64 Module libX11.so.6 from rpm libX11-1.8.11-1.fc42.x86_64 Module libcairo.so.2 from rpm cairo-1.18.2-3.fc42.x86_64 Module libpango-1.0.so.0 from rpm pango-1.56.3-1.fc42.x86_64 Module libgtk-3.so.0 from rpm gtk3-3.24.49-2.fc42.x86_64 Module libcups.so.2 from rpm cups-2.4.12-3.fc42.x86_64 Module libatk-bridge-2.0.so.0 from rpm at-spi2-core-2.56.2-1.fc42.x86_64 Module libatk-1.0.so.0 from rpm at-spi2-core-2.56.2-1.fc42.x86_64 Module libdbus-1.so.3 from rpm dbus-1.16.0-3.fc42.x86_64 Module libnspr4.so from rpm nss-3.112.0-1.fc42.x86_64 Module libsmime3.so from rpm nss-3.112.0-1.fc42.x86_64 Module libnssutil3.so from rpm nss-3.112.0-1.fc42.x86_64 Module libnss3.so from rpm nss-3.112.0-1.fc42.x86_64 Module libgio-2.0.so.0 from rpm glib2-2.84.2-1.fc42.x86_64 Module libgobject-2.0.so.0 from rpm glib2-2.84.2-1.fc42.x86_64 Module libglib-2.0.so.0 from rpm glib2-2.84.2-1.fc42.x86_64 Stack trace of thread 63788: #0 0x0000555b9189e4a9 n/a (/usr/share/cursor/cursor + 0x64384a9) #1 0x0000555b8dbff5ea n/a (/usr/share/cursor/cursor + 0x27995ea) #2 0x0000555b8dbfdac5 n/a (/usr/share/cursor/cursor + 0x2797ac5) #3 0x0000555b8dbfdf70 n/a (/usr/share/cursor/cursor + 0x2797f70) #4 0x0000555b8d8998f7 n/a (/usr/share/cursor/cursor + 0x24338f7) #5 0x00007f5ed2bc85f5 __libc_start_call_main (libc.so.6 + 0x35f5) #6 0x00007f5ed2bc86a8 __libc_start_main_impl (libc.so.6 + 0x36a8) #7 0x0000555b8d47102a n/a (/usr/share/cursor/cursor + 0x200b02a) ELF object binary architecture: AMD x86-64 GNU gdb (Fedora Linux) 16.3-1.fc42 Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... /usr/share/cursor/cursor: No such file or directory. This GDB supports auto-downloading debuginfo from the following URLs: Enable debuginfod for this session? (y or [n]) y Debuginfod has been enabled. To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit. warning: Can't open file /usr/share/cursor/libffmpeg.so during file-backed mapping note processing warning: Can't open file /usr/share/cursor/cursor during file-backed mapping note processing [New LWP 63788] Core was generated by `/tmp/.mount_Cursorco8TO2/usr/share/cursor/cursor'. Program terminated with signal SIGTRAP, Trace/breakpoint trap. #0 0x0000555b9189e4a9 in ?? () Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/79/bae446b9a2d28f83944da3e26fdc4738a35d86 /usr/lib/debug/.build-id/79/bae446b9a2d28f83944da3e26fdc4738a35d86.debug Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/60/fed38b5df7050dd9cfc6a9ff9082c863370451 /usr/lib/debug/.build-id/60/fed38b5df7050dd9cfc6a9ff9082c863370451.debug (gdb) bt full #0 0x0000555b9189e4a9 in ?? () No symbol table info available. #1 0x0000555b00000001 in ?? () No symbol table info available. #2 0xaaaaaa00ffffffff in ?? () No symbol table info available. #3 0x0000000000000000 in ?? () No symbol table info available. ~~~ ##### Rationale I've already enough information for a bug report to the developers , because I know what action caused it. However, considering the unusual signal, I'd like to be able to better confirm whether a [mis]configuration of mine is relevant, and provide *actionable* information.

Many applications (IntelliJ IDEA, PyCharm, Android Studio, etc) are available as a tar.gz or tar.xz files. They do not need to be installed. You just need to extract the archive file and run the application. On the other hand there are AppImages. By running an AppImage, the AppImage is temporally mounted on \tmp directory and then is executed. You can also extract the AppImage like any archive file and run the application. So my question is what is the difference between an AppImage and an archive file?

So yesterday I freshly installed my system (Linux Mint Wilma) and could open the AppImage in question from cinnamenu and grouped-windows-list. Today it's not possible anymore. The AppImage itself works fine, I can open it from nemo and the terminal, but not with a starter from menu or windows-list. Any advice appreciated.

I tried updating my Ubuntu and I started getting this error. I think I had some issues when installing launchpad but it works how its going at the moment. Iv tried looking at other similar issues but nothing has worked. Here is what i get when i try update

Hit:1 http://security.ubuntu.com/ubuntu  noble-security InRelease
Hit:2 http://gb.archive.ubuntu.com/ubuntu  noble InRelease        
Get:3 http://gb.archive.ubuntu.com/ubuntu  noble-updates InRelease [89.7 kB]
Hit:4 http://gb.archive.ubuntu.com/ubuntu  noble-backports InRelease         
Ign:5 https://ppa.launchpadcontent.net/appimagelauncher-team/stable/ubuntu  noble InRelease
Err:6 https://ppa.launchpadcontent.net/appimagelauncher-team/stable/ubuntu  noble Release
  404  Not Found [IP: 2620:2d:4000:1::81 443]
Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/appimagelauncher-team/stable/ubuntu  noble Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Thank you for any help

The APPIMAGE file is not working with these errors and it does not allow to install code command or other when it is run:

❯ ./Downloads/cursor-0.32.1x86_64.AppImage
[9512:0416/165640.500124:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser”
[9512:0416/165640.500162:ERROR:select_file_dialog_linux_portal.cc(280)] Failed to read portal version property
[main 2024-04-16T10:56:41.021Z] update#setState disabled
[main 2024-04-16T10:56:41.028Z] update#ctor - updates are disabled as there is no update URL
[main 2024-04-16T10:56:41.091Z] [storage state.vscdb] error checking size of src.vs.platform.reactivestorage.browser.reactiveStorageServiceImpl.persistentStorage.workspaceUser: Error: Unexpected number of rows - 0
[main 2024-04-16T10:56:41.091Z] [storage state.vscdb] error checking size of workbench.panel.aichat.view.aichat.chatdata: Error: Unexpected number of rows - 0
[main 2024-04-16T10:56:41.093Z] [uncaught exception in main]: Error: SQLITE_CANTOPEN: unable to open database file
[main 2024-04-16T10:56:41.093Z] Error: SQLITE_CANTOPEN: unable to open database file
[main 2024-04-16T10:56:42.170Z] [storage state.vscdb] error checking size of workbench.panel.aichat.view.aichat.chatdata: Error: Unexpected number of rows - 0
^C[main 2024-04-16T10:57:16.026Z] Extension host with pid 9819 exited with code: 0, signal: unknown.

I've been trying to run Qv2ray and other programs on Ubuntu 16.04 and Lubuntu 18, but I always get this error: cannot execute binary file: Exec format error. Here's the article that I've read in order to run appimage files: I tried these steps: 1. Installing fuse: sudo apt install libfuse2 2. Making the file executable in properties(Checked). 3. Double clicking on the file. Another file with a weird name appeared next to it, but the program was not executed, and also when I try to run it I get this error: cannot execute binary file: Exec format error.

I downloaded an AppImage (LogSeq to be precise) and wanted to add it to the dmenu. With the help of a friend i did the following: 1. move AppImage to a appropriate directory (not required, but appears cleaner to me). In this case i moved the LogSeq.AppImage to /home/[username]/.local/bin/LogSeq.AppImage 2. Create a .desktop entry with the required fields in /usr/share/applications -> logseq.desktop

[Desktop Entry]
Name=LogSeq
GenericName=logseq
Exec=/home/[username]/.local/bin/LoqSeq.AppImage
Terminal=false
Type=Application
Categories=Application;

After removing ~/.cache/dmenu_run to have dmenu rebuild it's cache, the app appears in the dmenu and i can run it. Cool! However both in dmenu_run as well as in the **dmenu** itself, the app appears as LogSeq.AppImage not as logseq as i had expected. How can i rename it so that it appears e.g. as logseq instead?

It is on debian on x86_64

me@debian:~/bin$ chmod a+x helix-23.03-aarch64.AppImage
me@debian:~/bin$ ./helix-23.03-aarch64.AppImage
/tmp/.mount_helix-RyzFyw/AppRun: 4: exec: /tmp/.mount_helix-RyzFyw/usr/bin/hx: Exec format error

I'm installing the Ultimaker Cura 3D printer slicer program from here (https://github.com/Ultimaker/Cura/releases/tag/5.1.0) onto Linux Ubuntu 20.04. 1. What is the difference between Ultimaker-Cura-5.1.0-linux-modern.AppImage and Ultimaker-Cura-5.1.0-linux.AppImage? Which should I use? Why? How do they differ? I've [posted this on their forum too](https://community.ultimaker.com/topic/41214-which-appimage-should-i-install-appimage-vs-modernappimage/) . ### Update: important installation reminder to myself and others: After downloading the desired AppImage for your operating system, per the accepted answer below, be sure to make it executable as well! Then, you can double-click on it in a file browser to run it. Ex: how to install Cura on Linux Ubuntu 20.04:

# download it
wget https://github.com/Ultimaker/Cura/releases/download/5.3.0/UltiMaker-Cura-5.3.0-linux.AppImage 

# Make it executable
chmod +x UltiMaker-Cura-5.3.0-linux.AppImage

# Now run it. 
# Option 1: double-click the file in a GUI file manager
# Option 2: run it from the command-line:
./UltiMaker-Cura-5.3.0-linux.AppImage    # run in foreground
./UltiMaker-Cura-5.3.0-linux.AppImage &  # run in background

### Related: 1. My question: [How do I check or verify a pgp/gpg signature using a .asc PGP signature file?](https://unix.stackexchange.com/q/711976/114401)

I downloaded WSL (Windows Subsystem for Linux) and tried to run an AppImage, but received an error message that said AppImage needs FUSE to run When I tried the --appimage-extract and --appimage-extract-and-run options, neither of them worked. It seems that FUSE is not supported in WSL. How can I run an AppImage on WSL if it requires FUSE and FUSE is not supported in WSL?

I heard a while back that appimages are *only* a way to package software, not distribute it; however, if I go to the [wikipedia definition](https://en.wikipedia.org/wiki/AppImage) : > AppImage is a format for distributing portable software on Linux without needing superuser permissions to install the application. So is it both a way of packaging and distributing software, or just packaging?

I recognize this is a stretch, but I have a shadow of a memory of a way to do it, and I'm hoping someone here will recognize what I'm talking about and help jog it. Traditional programs, both by terminal and GUI, have a starting sequence and a closing sequence of instructions, which can sometimes take some time to execute. Additionally, they may have other constraints, such as retrieving data from a database which may not always be available. A "memory image" of a program, I am defining as its footprint in RAM while running. That is, a one-to-one mapping of all memory allocated to the program. It is possible to image (and even mount the image of) a physical disk, to create an AppImage for an entire dependency structure, and to keep a virtual machine state (effectively an image) of the state of a virtual OS; so I may be wrong; but is it possible to save the memory state of a program (warts, inefficiency, and all) to a binary file? (One of my concerns is that some references kept by the image may change between boots, but this is technically a solvable problem and might not disqualify the idea.) If so, how would I go about doing this on a *nix system? It clearly isn't always (or even usually) an advantage, but I feel it bears investigation. To illustrate what I am trying to do: 1. Open Vim 2. Write a lengthy amount of text in Vim 3. Serialize Vim to disk without formally closing it 4. Wait several days 5. Deserialize instance of Vim from disk 6. Continue writing the same text So, save the state of the whole program, instead of just the file. One workaround I thought of is to run the program in a virtual instance, but this feels like it might typically be excessive.

Compiled a Qt project and created .AppImage for it, on two different Linux distros ( Qt was installed via different ways). The two output .AppImage contain different .so files. Both .AppImage run. I want to know : 1. How do AppImage tools decide what libraries to include? 2. Why two .AppImage files have different libraries included, while they both run? Does one of them (or do both of them) have no 100% feature? Do they have different compatibility to various Linux distros? I used linuxdeploy + linuxdeploy-plugin-qt like this:

./linuxdeploy --plugin qt --appdir ........

Comparison of the two .AppImage's .so files:

I am using PopOs 22. I am not able to download Etcher using the appimage file available on their official website. I was easily able to open it in the previous distributions just by double-clicking but on PopOs it does not open. I searched quite a but about this but couldn't find a fix. These are some things I have done trying to fix the issue. 1) Changed the file permissions. Now it looks like this. 2) Tried to create an executable by entering `chmod +x balenaEtcher-1.7.9-x64.AppImage ` in the directory where the appimage file exists. I still can not open the appimage file after making the above 2 changes. Using the Deb repos: I tried installing Etcher using the deb repos as well but it does not install successfully even using this method. It says chmod: balena-etcher-electron: no such file or directory at the end of the installation. This installs Etcher on the system though (I can see it in the list of applications) but when I try to open it, nothing happens, I cant open this app either. This is the link that I followed There are alternatives for Etcher so this is not a huge issue (PopOs has pre-installed popsicle for burning iso files). However, I really like this distro and I want to stick with it. Not being able to open appimage files is a concern for me. Any help with this issue is appreciated! Thanks in advance. Errors on console when I run ./*.AppImage

[Axios v1.7.9] Transitional option 'clarifyTimeoutError' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.9] Transitional option 'forcedJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.9] Transitional option 'silentJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
[4724:0828/182040.725841:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/tmp/.mount_balenacTllMg/balena-etcher-electron: line 10:  4724 Trace/breakpoint trap   (core dumped) "${script_dir}"/balena-etcher-electron.bin "$@"

I'm trying to run an .appimage in Pop OS 22.04 that requires the command --disable-gpu-sandbox. It works fine when launching from terminal, but when I create a .desktop file with the below: Encoding=UTF-8 Version=1.0 Type=Application Terminal=false Path=/home/evan/installs Exec=zoho64.AppImage --disable-gpu-sandbox Name=ZohoMail Icon=home/evan/installs/icon-zoho.png I get the following error: ./zoho.desktop: line 6: --disable-gpu-sandbox: command not found Sorry if this is a no-brainer, I'm a newbie just trying to leave Windows behind.

If you're running an AppImage application, and you make settings changes to it (or anything else that would change the state of the application), are those changes saved within the AppImage file itself? And if so, how do you preserve those settings upon upgrading to a later version of that AppImage application?

I have the password manager KeePassXC as an AppImage on my system. I run it _thousands_ times a day and I want to add a key-bind/shortcut to launch it, not just have the icon on the menu with a regular .desktop file. Edit. I did this: 1. **Create a script** named keepassxc (or the name of the AppImage you want to launch) that points to the /path/of/app.AppImage. I created mine in a hidden folder called .bin in my user's home directory (~/.bin) with a content like this:

#!/bin/bash
   /home/username/AppImages/KeePassXC.AppImage

2. **Add the directory of the script to your $PATH**. (In my case the directory was ~/.bin, so): 1. Edit the file ~/.profile (with nano, vim, or any text editor) 2. Add:

export PATH="$HOME/.bin:$PATH"

3. Refresh it (or logout - login):

source ~/.profile

3. Edit keyboard shortcuts (this deppends your desktop environment...) - The shortcut should have keepassxc (or the name you gave to the script) as the **command** - Then, select the key combination you want. Don't forget, of course, to have the **AppImage with permission to be executed**. Cheers! Edit 2 reason: make notes more clear as requested

I am trying to package my application in appimage format. I'm using appimage-builder to do so, and using Ubuntu 18.04, as appimage-builder documentation recommends. But I am unable to do so. I cloned my repository, and I ran meson build -Dprefix=/usr, then DESTDIR=$PWD/AppDir ninja -C build install then appimage-builder --generate, this did not add any dependency at all in the recipe, so I added them manually, then I run appimage-builder. My asset files fails to load using this method when testing on the machine the appimage is being generated on. As I am generating a config.h based on the prefix the user passes to meson and using those paths inside application to find asset files like icons and all. When the generation completes, all tests pass, while failing to load assets, which does not cause application to stop just gives a warning. But outside of this machine I cannot run this appimage anywhere, I get this error when running on a different machine,

**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error
== NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
[appimage-binfmt-bypass/bin] ERROR: child exited with code 6

Here is a link to my project - SampleHive If needed I can also share the generated recipe, including the things a I added manually.

I removed the AppImage launcher using

uninstall appimagelauncher

and deleted the appimage files from

~/Applications

as well but it didn't remove the two apps I had imstalled using appimage i.e. Visual studio code and OnlyOffice. I can still see their menu entry when I search for them. Even when I do a catfish search I see leftovers like these. I think It's because the appimage launcher integrates the images or something IIRC. So is there any way to ensure no residue is left? Some help will be appreciated :)

I'm sometimes working on the command line (or in the Ranger file manager), and it's annoying to have to move to a graphical interface to double-click on a AppImage. It looks like Ranger tries xdg-open; I tried that on the command line, myself, and that fails. My permissions are correct, so how can I actually run an AppImage from the command line?