github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #5738] PCSX2: profile needs to be converted for appimages #3078

New issue

Open

opened 2026-05-05 09:43:09 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 09:43:09 -06:00

Owner

Originally created by @NetSysFire on GitHub (Mar 18, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5738

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.

Originally created by @NetSysFire on GitHub (Mar 18, 2023). Original GitHub issue: https://github.com/netblue30/firejail/issues/5738 ### 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.

gitea-mirror commented

2026-05-05 09:43:11 -06:00

Author

Owner

@ghost commented on GitHub (Mar 18, 2023):

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

@ghost commented on GitHub (Mar 18, 2023): 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 ```

gitea-mirror commented

2026-05-05 09:43:12 -06:00

Author

Owner

@NetSysFire commented on GitHub (Mar 18, 2023):

Did you test the current PCSX2.profile with an AppImage yet?

No, not yet.

users who place the AppImage under their home dir

I am unsure but I think upstreams proposed workflow is that no distros should package PCSX2 and instead want users download the appimages manually. Which means it will usually be in $DOWNLOADS. The file name I just fetched from their website would be pcsx2-v1.7.4245-linux-AppImage-64bit-Qt.AppImage. It is dynamic, so it will likely cause issues, too I guess.

@NetSysFire commented on GitHub (Mar 18, 2023): >Did you test the current PCSX2.profile with an AppImage yet? No, not yet. >users who place the AppImage under their home dir I am unsure but I *think* upstreams proposed workflow is that no distros should package PCSX2 and instead want users download the appimages manually. Which means it will usually be in `$DOWNLOADS`. The file name I just fetched from their website would be `pcsx2-v1.7.4245-linux-AppImage-64bit-Qt.AppImage`. It is dynamic, so it will likely cause issues, too I guess.

gitea-mirror commented

2026-05-05 09:43:13 -06:00

Author

Owner

@rusty-snake commented on GitHub (Mar 18, 2023):

@glitsj16 Noexec works fine with AIs as long as you use --appimage.

@rusty-snake commented on GitHub (Mar 18, 2023): @glitsj16 Noexec works fine with AIs as long as you use --appimage.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#3078

No description provided.

Rows
Columns