github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #2860] seccomp causes steam (and other) games to freeze #1785

New issue
Closed
opened 2026-05-05 08:27:05 -06:00 by gitea-mirror · 10 comments
gitea-mirror commented 2026-05-05 08:27:05 -06:00
Owner
Copy link

Originally created by @ghost on GitHub (Jul 16, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2860

Nvidia 418.56 Ubuntu 18.04 up-to-date w/ Gnome. Firejail built today from master.

So to track down some issues I ran steam with noprofile and when I added seccomp Proton/Wine games would freeze. Usually 1-2 seconds of intro video (or something else) would play with sound before freezing completely. The freeze is not global so alt tabbing works, mouse is not released though. Ctrl C on the firejail steam terminal window works.

I settled on

--disable-mnt --net=eth0 --defaultgw=192.168.0.1 --dns=1.1.1.1 --private=~/jailed --noroot --nonewprivs --nogroups --noprofile steam

And steam and its proton games run with no issues.

The same is true of Lutris (python wine manager), seccomp causes games to not even start and game launchers to start slowly - the wine virtual desktop starts. In this particular case I also noted that Lutris itself was unable to kill the wine processes it started (it has an option to kill all wine processes), probably related. Running the above options with Lutris solved all problems.

Originally created by @ghost on GitHub (Jul 16, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2860 Nvidia 418.56 Ubuntu 18.04 up-to-date w/ Gnome. Firejail built today from master. So to track down some issues I ran steam with noprofile and when I added seccomp Proton/Wine games would freeze. Usually 1-2 seconds of intro video (or something else) would play with sound before freezing completely. The freeze is not global so alt tabbing works, mouse is not released though. Ctrl C on the firejail steam terminal window works. I settled on --disable-mnt --net=eth0 --defaultgw=192.168.0.1 --dns=1.1.1.1 --private=~/jailed --noroot --nonewprivs --nogroups --noprofile steam And steam and its proton games run with no issues. The same is true of Lutris (python wine manager), seccomp causes games to not even start and game launchers to start slowly - the wine virtual desktop starts. In this particular case I also noted that Lutris itself was unable to kill the wine processes it started (it has an option to kill all wine processes), probably related. Running the above options with Lutris solved all problems.
gitea-mirror commented 2026-05-05 08:27:08 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jul 17, 2019):

@LamaRaz can you try if firejail --ignore=seccomp steam also works.
EDIT:
What is the output from journalctl --grep=syscall after crashing with firejail steam.

<!-- gh-comment-id:512139912 --> @rusty-snake commented on GitHub (Jul 17, 2019): @LamaRaz can you try if `firejail --ignore=seccomp steam` also works. EDIT: What is the output from `journalctl --grep=syscall` after crashing with `firejail steam`.
gitea-mirror commented 2026-05-05 08:27:09 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (Jul 17, 2019):

only these:

audit[5477]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 pid=5477 comm="steam" exe="/home/*/.steam/ubuntu12_32/steam" sig=31 arch=40000003 syscall=26 compat=1 ip=* code=0x0

kernel: audit: type=1326 audit(1563350012.331:81): auid=1000 uid=1000 gid=1000 ses=2 pid=5477 comm="steam" exe="/home/*/.steam/ubuntu12_32/steam" sig=31 arch=40000003 syscall=26 compat=1 ip=* code=0x0

audit[5798]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 pid=5798 comm="wineserver" exe=2F686F6D652F*******************************************************************************5736572766572 sig=31 arch=c000003e syscall=101 compat=0 ip=* code=0x0

kernel: audit: type=1326 audit(1563350036.867:82): auid=1000 uid=1000 gid=1000 ses=2 pid=5798 comm="wineserver" exe=2F686F6D652F***********************************************************************766572 sig=31 arch=c000003e syscall=101 compat=0 ip=* code=0x0
<!-- gh-comment-id:512146372 --> @ghost commented on GitHub (Jul 17, 2019): only these: ``` audit[5477]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 pid=5477 comm="steam" exe="/home/*/.steam/ubuntu12_32/steam" sig=31 arch=40000003 syscall=26 compat=1 ip=* code=0x0 kernel: audit: type=1326 audit(1563350012.331:81): auid=1000 uid=1000 gid=1000 ses=2 pid=5477 comm="steam" exe="/home/*/.steam/ubuntu12_32/steam" sig=31 arch=40000003 syscall=26 compat=1 ip=* code=0x0 audit[5798]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 pid=5798 comm="wineserver" exe=2F686F6D652F*******************************************************************************5736572766572 sig=31 arch=c000003e syscall=101 compat=0 ip=* code=0x0 kernel: audit: type=1326 audit(1563350036.867:82): auid=1000 uid=1000 gid=1000 ses=2 pid=5798 comm="wineserver" exe=2F686F6D652F***********************************************************************766572 sig=31 arch=c000003e syscall=101 compat=0 ip=* code=0x0 ```
gitea-mirror commented 2026-05-05 08:27:11 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jul 17, 2019):

@LamaRaz can you try firejail --allow-debuggers steam

<!-- gh-comment-id:512152944 --> @rusty-snake commented on GitHub (Jul 17, 2019): @LamaRaz can you try `firejail --allow-debuggers steam`
gitea-mirror commented 2026-05-05 08:27:12 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (Jul 17, 2019):

Well now --seccomp doesn't freeze my games. --allow-debuggers is the fix, not sure what it means though but results are results.

<!-- gh-comment-id:512349383 --> @ghost commented on GitHub (Jul 17, 2019): Well now --seccomp doesn't freeze my games. --allow-debuggers is the fix, not sure what it means though but results are results.
gitea-mirror commented 2026-05-05 08:27:13 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jul 17, 2019):

FYI: your journal show that syscall=101 is blocked, the following show what syscall is blocked. And --allow-debuggers allow ptrace.

firejail --debug-syscalls | grep 101
101	- ptrace
<!-- gh-comment-id:512354453 --> @rusty-snake commented on GitHub (Jul 17, 2019): FYI: your journal show that `syscall=101` is blocked, the following show what syscall is blocked. And `--allow-debuggers` allow `ptrace`. ``` firejail --debug-syscalls | grep 101 101 - ptrace ```
gitea-mirror commented 2026-05-05 08:27:14 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (Jul 17, 2019):

I was more wondering why Wine needs ptrace to not freeze and why others have not reported the same issue. Is it only my setup that requires ptrace for some reason?

<!-- gh-comment-id:512442695 --> @ghost commented on GitHub (Jul 17, 2019): I was more wondering why Wine needs ptrace to not freeze and why others have not reported the same issue. Is it only my setup that requires ptrace for some reason?
gitea-mirror commented 2026-05-05 08:27:16 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (Jul 17, 2019):

Game now froze randomly in a battle where before it never froze. Nothing in journalctl.
Will just be on the safe side and not use seccomp, not particularly worried about steam games doing targeted exploitation, just don't want spyware anticheats uploading lists of my filesystem.

<!-- gh-comment-id:512591840 --> @ghost commented on GitHub (Jul 17, 2019): Game now froze randomly in a battle where before it never froze. Nothing in journalctl. Will just be on the safe side and not use seccomp, not particularly worried about steam games doing targeted exploitation, just don't want spyware anticheats uploading lists of my filesystem.
gitea-mirror commented 2026-05-05 08:27:17 -06:00
Author
Owner
Copy link

@boltronics commented on GitHub (Jul 28, 2019):

Confirming seccomp has been causing me issues as well (0.9.58.2-2 as shipped in Debian buster). Shows the same error when launching Steam as was introduced by the recent kernel networking issue, making this quite frustrating to troubleshoot.

<!-- gh-comment-id:515722809 --> @boltronics commented on GitHub (Jul 28, 2019): Confirming seccomp has been causing me issues as well (0.9.58.2-2 as shipped in Debian buster). Shows the same error when launching Steam as was introduced by the recent kernel networking issue, making this quite frustrating to troubleshoot.
gitea-mirror commented 2026-05-05 08:27:17 -06:00
Author
Owner
Copy link

@boltronics commented on GitHub (Jul 28, 2019):

In fact, even with that directive ignored, I'm still getting intermittent issues connecting, so there must be something else as well going on. I'm probably going to have to slowly narrow down this issue over time.

<!-- gh-comment-id:515723487 --> @boltronics commented on GitHub (Jul 28, 2019): In fact, even with that directive ignored, I'm still getting intermittent issues connecting, so there must be something else as well going on. I'm probably going to have to slowly narrow down this issue over time.
gitea-mirror commented 2026-05-05 08:27:18 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Oct 13, 2019):

I'm closing here due to inactivity, please fell free to reopen if you have more questions.

<!-- gh-comment-id:541425932 --> @rusty-snake commented on GitHub (Oct 13, 2019): I'm closing here due to inactivity, please fell free to reopen if you have more questions.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear labels   
LTS merge

   
LTS merge

   
bug

   
bug

   
converted-to-discussion

   
doc-todo

   
documentation

   
duplicate

   
enhancement

   
file-transfer

   
firecfg

   
firejail-in-firejail

   
firetools

   
graphics

   
help wanted

   
information_old

   
installation

   
invalid

   
modif

   
moved

   
needinfo

   
networking

   
notabug

   
notourbug

   
old-version

   
overlayfs

   
packaging

   
profile-request

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1785
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?