AppImageLauncher | Helper application for Linux distributions
kandi X-RAY | AppImageLauncher Summary
kandi X-RAY | AppImageLauncher Summary
Currently, desktop environments consider exexutables 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 wasappimaged, 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.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of AppImageLauncher
AppImageLauncher Key Features
AppImageLauncher Examples and Code Snippets
Community Discussions
Trending Discussions on AppImageLauncher
QUESTION
I'm having trouble using the CLion integration environment under linux.
When I execute a script using the system terminal, it is possible to run. compile_test.sh:
...ANSWER
Answered 2021-Oct-22 at 08:46I know why there is such a reason. Because I use flatpak to install, it has its own virtual environment. It's fine after I use the source code to install
QUESTION
I launched an appimage using appimagelauncher. Then, I modified some settings of that app.
I know that appimages are not installed, so it can't be uninstalled. So, I deleted the appimage file.
But, when I downlaoded the appimage again, I observed that the user's previously modified settings were still there.
Now, how can I completely remove those user modified settings and launch that software as if it were newly installed?
...ANSWER
Answered 2020-Nov-11 at 19:32The AppImage format doesn't define an explicit place where the applications configuration should be installed. Which means that the application can write such file wherever they please (as a regular installed application does).
Applications usually write their configurations to "$HOME/.config", you can look there for a file or folder with the application name. You can also ask the application author or check the documentation.
QUESTION
My build system, which uses meson, puts some files my application needs on AppDir under AppDir/usr/share/myapp/resources
. The application needs both, read and write to those files when it is running. The files are in AppDir when I look at it, but when the .AppImage is generated, the standalone running executable cannot access those files. When integrating the application with the desktop, the application gets installed in ~/Applications
, but it doesn't contain those files.
Here is a visualization of how it looks when the application is installed on the system without using AppImage (ninja install
)
ANSWER
Answered 2020-Apr-14 at 21:26To resolve the AppImage mount point at runtime you can use the APPDIR
environment variable. For example, if you want to resolve usr/share/icons/hicolor/myicon.png
you need to use the following path $APPDIR/usr/share/icons/hicolor/myicon.png
.
It's recommended that you modify the application to be able to resolve its resources depending on the binary location. As an alternative, you can use a custom environment variable to set up the path or a configuration file next to your main binary.
Regarding writing files inside the AppImage. This is not possible by design. An AppImage is a read-only SquashFS image that is mounted at runtime. Any application data should be written to $HOME/.config
or $HOME/.local/share
depending on whether it's a configuration data or other kind of data. The recommended workflow is to copy such data on the first run.
For more information about whether to copy your application data see https://www.freedesktop.org/wiki/Software/xdg-user-dirs/
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install AppImageLauncher
Ubuntu Trusty (14.04) and newer Important: Ubuntu Bionic (and newer) broke with the backwards compatibility of its libcurl packages, therefore users of these systems need to install the special bionic package
Debian stable (Jessie, 8) and newer
Netrunner 17 and newer
openSUSE Leap 42 and newer
openSUSE Tumbleweed
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
Build instructions in BUILD.md.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page