Crash (openSUSE Tumbleweed)
RafaelLinux opened this issue · 4 comments
CLI output:
./Bottles_51.6-x86_64.appimage
proot warning: can't sanitize binding "/media": No such file or directory
proot error: it seems the current temporary directory (/tmp) is mounted with no execution permission.
proot info: Please set PROOT_TMP_DIR env. variable to an alternate location ('/tmp/.mount_BottleCyMhSd/.junest/tmp' for example).
proot error: execve("/usr/bin/sh"): No such file or directory
proot info: possible causes:
* the program is a script but its interpreter (eg. /bin/sh) was not found;
* the program is an ELF but its interpreter (eg. ld-linux.so) was not found;
* the program is a foreign binary but qemu was not specified;
* qemu does not work correctly (if specified);
* the loader was not found or doesn't work.
fatal error: see `proot-x86_64 --help`.
proot error: can't chmod '/tmp/proot-16514-flwlcW': No such file or directory
proot warning: can't sanitize binding "/media": No such file or directory
proot error: it seems the current temporary directory (/tmp) is mounted with no execution permission.
proot info: Please set PROOT_TMP_DIR env. variable to an alternate location ('/tmp/.mount_BottleCyMhSd/.junest/tmp' for example).
proot error: execve("/usr/bin/sh"): No such file or directory
proot info: possible causes:
* the program is a script but its interpreter (eg. /bin/sh) was not found;
* the program is an ELF but its interpreter (eg. ld-linux.so) was not found;
* the program is a foreign binary but qemu was not specified;
* qemu does not work correctly (if specified);
* the loader was not found or doesn't work.
fatal error: see `proot-x86_64 --help`.
proot error: can't chmod '/tmp/proot-16517-xypSY9': No such file or directory
Error: Something went wrong with proot command. Exiting
rm: no se puede borrar '[': Sistema de ficheros de sólo lectura
the only way I have to export JuNest-based AppImages is to run them in proot mode, but this seems to give limits to some apps (like Bottles or GNOME Boxes). Using normal version with namespaces made the Appimage non portable.
As surely you read in Bottles issues, they will not release (despite they did time ago) an AppImage. So Bottles is forget for me now so I will not recommend it if someone ask me about. FlatPak "way fo work" is not so transparent as AppImage.
I use Linux since 2009, I had less problems to use WINE from command line or by using q4wine... while Bottles have never worked for me, not as a Flatpak, nor as an AppImage, nor as an AUR package.
I must say it worked for me, and very well. But FlatPak eated my DATA partition (home) and after learn how it works, decided to not use FlatPaks anymore.