glitsj16
commented
1 year ago Did you test the current PCSX2.profile with an AppImage yet? A quick glance at the profile suggests these potential bottlenecks:
- include disable-exec.inc --> users who place the AppImage under their home dir will need to add
ignore noexec ${HOME}in PCSX2.local - apparmor --> users who place the AppImage under their home dir and use AppArmor will need to allow the path in their /etc/apparmor.d/local/firejail-default
Obviously firecfg wouldn't be able to create a working symlink for an AppImage. A simple shell wrapper like the below should work without any changes to the current profile - assuming both the script and the AppImage are placed in /usr/local/bin:
#!/bin/sh
# firejail wrapper for PCSX2 AppImage
firejail --appimage --profile=PCSX2 /usr/local/bin/PCSX2.AppImage
NetSysFire
rusty-snake
Description
PCSX2 has dropped the support for anything but appimages. The profile needs to be adjusted. Also, when you try building it yourself (explicitely unsupported by upstream), there are two flavors: the deprecated GTK PCSX2 binary and the qt (iirc called PCSX2-qt, capitalization might be off) one, adding extra complexity that might need to be taken care of for users of older PCSX2 builds (debian? ubuntu?). The comments on this, which was dropped from the community, might help, too: https://aur.archlinux.org/packages/pcsx2
If possible, assign a Help Wanted label to this issue. In any case, I think some input on how to handle the situation with both appimages and binaries is appreciated as it is not really clear how to proceed.