search

AppImage / appimage.github.io

Given an URL to an AppImage, the GitHub action in this project inspects the AppImage and puts it into a community-maintained catalog
https://appimage.github.io/
Other
306 stars 550 forks source link

Why? "Permission denied" #17

Open probonopd opened 7 years ago

probonopd commented 7 years ago

Firejail related?

The AppImage runs just fine on my local machine without Firejail.

firejail ./DeviceInterface-x86_64.AppImage /bin/bash: /run/firejail/appimage/.appimage-7979/AppRun: Permission denied

https://travis-ci.org/AppImage/AppImageHub/builds/266091972#L555

probonopd commented 6 years ago

May be caused by Firejail? https://github.com/AppImage/appimage.github.io/pull/456#issuecomment-377820382

simoniz0r commented 6 years ago

I'm pretty sure this happens when the AppImage unmounts itself before the next command can run. The only solution I've really found for this is to move the component that is being called out of the AppImage temporarily and call it from the directory I've moved it to. I've tried adding sleeps and such, but no dice.

For example, with ROSA ImageWriter, it needs to be ran as root with something like xdg-su. xdg-su will run fine, but the AppImage seems to unmounts itself as soon as xdg-su finishes running unless I move the RosaImageWriter executable outside of the AppImage and call it from there.

probonopd commented 5 years ago

Many apps have this "permission denied" thing: https://github.com/AppImage/appimage.github.io/search?q=%22permission+denied%22&type=Issues

Why?

probonopd commented 5 years ago

Seems to be related to Firejail. E.g., https://github.com/AppImage/appimage.github.io/pull/1025#issuecomment-491495519 shows how to verify this.