Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AppImage crashes upon launch: "execv error: No such file or directory" #1548

Open
illtellyoulater opened this issue Jun 30, 2024 · 10 comments
Open
Assignees

Comments

@illtellyoulater
Copy link

illtellyoulater commented Jun 30, 2024

I get this error while launching latest AppImage (both stable and bleeding edge):

execv error: No such file or directory

I'm on:

  • OS: Pop!_OS 22.04 LTS x86_64 (Ubuntu Based)
  • Kernel: 6.9.3-76060903-generic
  • DE: GNOME 42.9
@illtellyoulater
Copy link
Author

illtellyoulater commented Jun 30, 2024

@illtellyoulater
Copy link
Author

illtellyoulater commented Jul 1, 2024

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?

@jcelerier
Copy link
Member

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...

@illtellyoulater
Copy link
Author

@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.

@jcelerier
Copy link
Member

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?

@illtellyoulater
Copy link
Author

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.

@jcelerier
Copy link
Member

could you try the flatpak ? at the bottom here: https://github.com/ossia/score/actions/runs/9752236615

@illtellyoulater
Copy link
Author

It seems it doesn't work

flatpak run io.ossia.score
bwrap: Can't mkdir parents for /app/extensions/Plugins: Read-only file system
error: ldconfig failed, exit status 256

@jcelerier
Copy link
Member

can you try this one ?

flatpak install --user https://dl.flathub.org/build-repo/116649/io.ossia.score.flatpakref 

it's in process of being upstreamed to flathub and seems to work for multiple people

@jcelerier
Copy link
Member

You can get the actual official flatpak now : https://flathub.org/apps/io.ossia.score

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In progress
Development

No branches or pull requests

2 participants