-
-
Notifications
You must be signed in to change notification settings - Fork 566
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
Execute AppImage file, get the error message "execv error: No such file or directory" #508
Comments
Is there an You should follow good practices and provide an MWE that has the bug, e.g., by uploading your AppImage somewhere and providing a link. Otherwise, we're just guessing wildly here. |
Which application are you packaging, and is the script you are using to do this available? |
Closing due to inactivity. Please reopen in case you still think this is a bug. |
Thank you for your anwsers and sorry for inactivity. |
Here, I do a summary. |
I think what you are trying to do is |
Yes, exactly! |
@probonopd I'm facing the same error while trying to run a previously AppImage'd app (this one for the record). I'm following the "manual steps" described here. The output of
I also double-checked the absence of hard-coded paths in the binary that would prevent it from being relocateable. Running the appImage's version always yields Here is the .AppImage dir I'm currently using: giada-appimage.zip |
Multiple issues:
Checking for additional missing libraries yields:
These libraries, as well as their dependencies, need to be bundled as well. It may be much easier to use https://github.com/probonopd/linuxdeployqt instead, which would do the required work automatically for you. Please check out the Travis CI example in its documentation; you should be able to copy-and-paste it almost 1:1 and go from there. |
@probonopd thanks for your quick reply (and sorry for my late one)! You are right, there are still some missing dependencies. I'll also look into https://github.com/probonopd/linuxdeployqt more closely. |
Hey! I'm trying to make an AppImage of a C++ executable which also uses glade XML files for GTK+ user interface. When I try to run the executable directly, it runs fine, but when I try to use AppRun it fails to locate the glade files. (QuizTech:10130): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (QuizTech:10130): GLib-GObject-WARNING **: invalid (NULL) pointer instance (QuizTech:10130): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (QuizTech:10130): GLib-GObject-WARNING **: invalid (NULL) pointer instance (QuizTech:10130): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (QuizTech:10130): Gtk-CRITICAL **: gtk_widget_show_all: assertion 'GTK_IS_WIDGET (widget)' failed Also the appimage created does not execute with: Here is my appdir: |
suggests that this is trying to load |
I tried changing the file name from "login.glade" to a path "./login.glade" inside the source code. Still no improvement. |
Again, you need to make it load from a path relative to the main executable. Not relative to |
Got it solved using |
For me the problem was somehow in AppRun the second line of code got tangled with the #!/bin/bash on the first line. |
This workaround is currently necessary because '/usr' is replaced by '././' in binaries, so a chdir() is needed to make './' point to the root of the AppDir. Unfortunately, linuxdeployqt, which is an alternative, is not available on all required platforms. Note that another workaround that works prior to this commit is to provide absolute path names. See the following issue threads for additional context: - AppImage/AppImageKit#172 - AppImage/AppImageKit#989 - https://docs.appimage.org/packaging-guide/environment-variables.html#type-2-appimage-runtime - AppImage/AppImageKit#1035 - linuxdeploy/linuxdeploy#123 - AppImage/AppImageKit#508
I had a similar problem, but I found solution here: OpenShot/openshot-qt#93 (comment) Running |
The |
You're right, and I've always wanted to do this. I was about to ask you to create an issue, but let's just fix this once and for all.
A little convenience doesn't hurt IMO. This should be the final step of the |
True ;-) |
I found it is permission problem on linux. fuse2 may be solve this problem but it is good idea if we set permissions before pack. |
I reported this as ungoogled-software/ungoogled-chromium#3175 thinking it was an issue with their build system, but the appimage at https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/appimage/64bit/132.0.6834.110-1 works on machines not running appimagelauncher... I'm using the latest appimagelaunche-git build on manjaro; if there's a more recent version maybe there's a build system issue. |
I download the 'appimagetool-x86_64.AppImage'. And use it to make my appimage file successfully. However, when I execute 'myfile.AppImage' by typing "./myfile.AppImage", it returns:
Anyone encounter this situation? Or anyone has some ideas? Thanks alot.
The text was updated successfully, but these errors were encountered: