Open illtellyoulater opened 5 days ago
As per the previous link, this is causes by the way some AppImages are packaged, which conflicts with AppImageLauncher
.
A simple workaround is to temporarily remove AppImageLauncher with
sudo apt remove appimagelauncher
This will not remove all the AppImages files which AppImageLauncher has so far moved to its dir (usually ~/Applications) nor remove the menu entries for previous AppImages, and later, you can just reinstall AppImageLauncher with
sudo apt install appimagelauncher
However for someone heavily relying on it, this is not an ideal solution. Can something be done on this?
i'm trying to see if I can build a flatpak to offer an alternative way. Not sure I can do anything about AppImageLauncher bugs sadly...
@jcelerier are there specific difficulties involved in fixing the AppImage version, or you just have more expeerience with flatpak?
Having them both would be great, but since we already have an AppImage I'd give more priority to fix that, if feasible within a reasonable time/energy frame.
Can't really do anything on the appimage side, this isn't under my control - the appimage is packaged the way it is because it's the only way to make it work easily on modern Ubuntu versions (older type1 appimages don't run as-is above Ubuntu 22.04) so i'm a bit between a rock and a hard place... Could try to build both types maybe. Or ship a .tar.gz with the content directly. Does --appimage-extract work or not at all?
Ah ok I understand the issue better now, thanks I tried with --appimage-extract but it didn't work. I don't think it makes a lot of sense to waste time on building a type1 AppImage. In my case the distro I'm using will be rebased on a more recent Ubuntu version soon. A tar.gz could always come handy though.
could you try the flatpak ? at the bottom here: https://github.com/ossia/score/actions/runs/9752236615
I get this error while launching latest AppImage (both stable and bleeding edge):
execv error: No such file or directory
I'm on: