AppImageLauncher

Message
Author
User avatar
Otter
Posts: 25
Joined: Sun Jul 02, 2017 2:58 pm

AppImageLauncher

#1 Post by Otter »

AppImageLauncher makes your Linux desktop AppImage ready™. By installing it, you won't ever have to worry about AppImages again. You can always double click them without making them executable first, just like you should be able to do nowadays. You can integrate AppImages with a single mouse click, and manage them from your application launcher. Updating and removing AppImages becomes as easy as never before.

Due to its simple but efficient way to integrate into your system, it plays well with other applications that can be used to manage AppImages, for example app stores. However, it doesn't depend on any of those, and can run completely standalone.

How it works

AppImageLauncher is responsible for the desktop integration. When the user launches an AppImage, the software checks whether the AppImage has been integrated already. If not, 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.
Sources:
https://github.com/TheAssassin/AppImageLauncher
https://www.opendesktop.org/p/1228228

Need for it: Makes AppImage installation simple without needing to add/remove menu entries manually.
:dancingman: Happy MX Linux User!

User avatar
Paul..
Posts: 1787
Joined: Sun Mar 18, 2007 6:34 pm

Re: AppImageLauncher

#2 Post by Paul.. »

How has AppImageLauncher been working for you?

How many have you installed, etc.

What version of MX are you using...some details would be nice for others...

Asus Prime X570-Pro | AMD Ryzen 7 3700X
16 Gig DDR4 3600 | Radeon RX 5600 XT Graphics
Samsung 860 500GB SSDs (2)

User avatar
manyroads
Posts: 2657
Joined: Sat Jun 30, 2018 6:33 pm

Re: AppImageLauncher

#3 Post by manyroads »

Paul.. wrote: Sat Apr 20, 2019 8:11 am How has AppImageLauncher been working for you?
[...]
I agree. I don't actually find manual remove of application links to be a huge problem. :p
Pax vobiscum,
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken

User avatar
Otter
Posts: 25
Joined: Sun Jul 02, 2017 2:58 pm

Re: AppImageLauncher

#4 Post by Otter »

Paul.. wrote: Sat Apr 20, 2019 8:11 am How has AppImageLauncher been working for you?

How many have you installed, etc.

What version of MX are you using...some details would be nice for others...
The available releases doesn't seem to work because they're systemd based packages.

I'm on MX18 and using 3 AppImages for now because discord flatpak doesn't work, Telegram crashes randomly and Kdevelop isn't available as flatpak.
:dancingman: Happy MX Linux User!

User avatar
dolphin_oracle
Developer
Posts: 22677
Joined: Sun Dec 16, 2007 12:17 pm

Re: AppImageLauncher

#5 Post by dolphin_oracle »

Otter wrote: Mon Apr 22, 2019 9:45 am
Paul.. wrote: Sat Apr 20, 2019 8:11 am How has AppImageLauncher been working for you?

How many have you installed, etc.

What version of MX are you using...some details would be nice for others...
The available releases doesn't seem to work because they're systemd based packages.

I'm on MX18 and using 3 AppImages for now because discord flatpak doesn't work, Telegram crashes randomly and Kdevelop isn't available as flatpak.
while flatpaks don't technically require systemd, there is a small problem in the way debian's sysVinit configures some temporary memory (/dev/shm). flatpaks can't follow symlinks, so the debian defualt symlink from /dev/shm to /run/shm doesn't work.

using the modified /lib/init/mount-functions.sh in the attached tarball (in place of the existing /lib/init/mount-functions.sh) and a reboot should resolve the issue with discord, and may improve your crashes in others.

these changes are already made in debian buster for the future.
You do not have the required permissions to view the files attached to this post.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/

User avatar
Otter
Posts: 25
Joined: Sun Jul 02, 2017 2:58 pm

Re: AppImageLauncher

#6 Post by Otter »

Thank you very much. It worked.

I'm back to flatpaks for discord & telegram.

Could you please let me know where the configs related to flatpaks are stored? I don't see it under .config. Thanks.
:dancingman: Happy MX Linux User!

User avatar
asqwerth
Developer
Posts: 8036
Joined: Sun May 27, 2007 5:37 am

Re: AppImageLauncher

#7 Post by asqwerth »

.var
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
Otter
Posts: 25
Joined: Sun Jul 02, 2017 2:58 pm

Re: AppImageLauncher

#8 Post by Otter »

Hah, yes, thanks.

Again same issue with flatpak. In telegram it doesn't let me choose a directory in another mounted drive as default download directory. Back to AppImage.
:dancingman: Happy MX Linux User!

User avatar
asqwerth
Developer
Posts: 8036
Joined: Sun May 27, 2007 5:37 am

Re: AppImageLauncher

#9 Post by asqwerth »

Could just be that the flatpak packagers for telegram got something wrong.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

nimbosa

Re: AppImageLauncher

#10 Post by nimbosa »

this should work now on MX 19, right?

Locked

Return to “Package Requests/Status - MX 17/18”