also it happens for the portable version.
for the portable version this works to resolve it:
Download and extract.
cd ./draft-linux_portable
sudo chown root:root chrome-sandbox
sudo chmod 4577 chrome-sandbox
./drafft
and that will run correctly from any where
i am going to assume that it may work with an extracted app image. using –appimage-extract then using the same procedure but instead of folder name above its likely to be squashfs
but i havent tried that as im not home to test.
hm this issue leads me to apparmour profile again and also a strange case where the appimage has a space in the path.
do you have any space in your path? https://github.com/electron/electron/issues/44414 https://github.com/electron/electron/issues/41066
BTW: Electron builder 26 which have apparmour support/fix will be stable soon apparently.
no spaces in path on my end, its an interesting bug, because it doesnt effect every system or os, so i decided to test other random app images as well, and some have the issue and some dont, i hope they fix the bugs with it as i think app images are great (not so much for security but for ease of use) thats where flatpak is good, provided that people set their permissions correctly (to be fair they usually dont so devs just leave it loose to ensure it runs. its a pretty common set of issues that really needs standardisation. it varies so greatly between systems even apparmor features varies between distro’s. i think their should be enforcement of feature set minimums but alas there is not.
im trying to find ways around these issues in my spare time as well, so if anything pops up that immediately fixes it ill be sure to share it.
i dont how ever, recommend people start adding the userns clone to 1. it will open a can of security worms that most people cannot fix or configure making them vulnerable.