github-starred/firejail

Fork 0

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

[GH-ISSUE #1839] F1 2017 doesn't start - Firejail is more than likely to be the barrier #1247

New issue

Closed

opened 2026-05-05 07:43:26 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 07:43:26 -06:00

Owner

Originally created by @ghost on GitHub (Mar 26, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1839

Hi!

I always run all my programs firejailed, for the get-go. This includes Steam.

I'm running Debian Testing and Steam worked fine, all my games work fine.
However, I bought F1 2017 a few days ago and just couldn't make it run. It's a Vulkan-only game.

After a brief thread about the subject I asked if my friend would test it with Firejail, and, according to him, firejail is what's preventing F1 2017 from starting.

I'm a bit paranoid to run Steam completely outside of firejail, so do you guys have any tips to what I could do to make F1 2017 start?

Thanks!

Originally created by @ghost on GitHub (Mar 26, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/1839 Hi! I always run all my programs firejailed, for the get-go. This includes Steam. I'm running Debian Testing and Steam worked fine, all my games work fine. However, I bought F1 2017 a few days ago and just couldn't make it run. It's a Vulkan-only game. After [a brief thread about the subject](http://steamcommunity.com/app/221410/discussions/0/1698294337773862910/?tscn=1522066122#c1698294337784130051) I asked if my friend would test it with Firejail, and, according to him, firejail is what's preventing F1 2017 from starting. I'm a bit paranoid to run Steam completely outside of firejail, so do you guys have any tips to what I could do to make F1 2017 start? Thanks!

gitea-mirror closed this issue

2026-05-05 07:43:27 -06:00

gitea-mirror commented

2026-05-05 07:43:29 -06:00

Author

Owner

@SkewedZeppelin commented on GitHub (Mar 26, 2018):

Could you try again with 0.9.52?

I'm not sure what is blacklisted in 0.9.38, but the current version of the profile has the following lines which might be of help

noblacklist ${HOME}/.local/share/vulkan
# with >=llvm-4 mesa drivers need llvm stuff
noblacklist /usr/lib/llvm*
# needed for STEAM_RUNTIME_PREFER_HOST_LIBRARIES=1 to work
noblacklist /sbin

@SkewedZeppelin commented on GitHub (Mar 26, 2018): Could you try again with 0.9.52? I'm not sure what is blacklisted in 0.9.38, but the current version of the profile has the following lines which might be of help ``` noblacklist ${HOME}/.local/share/vulkan # with >=llvm-4 mesa drivers need llvm stuff noblacklist /usr/lib/llvm* # needed for STEAM_RUNTIME_PREFER_HOST_LIBRARIES=1 to work noblacklist /sbin ```

gitea-mirror commented

2026-05-05 07:43:30 -06:00

Author

Owner

@ghost commented on GitHub (Mar 26, 2018):

I'm running 0.9.52 already ^^
Debian Testing here, as per OP.

@ghost commented on GitHub (Mar 26, 2018): I'm running 0.9.52 already ^^ Debian Testing here, as per OP.

gitea-mirror commented

2026-05-05 07:43:31 -06:00

Author

Owner

@ghost commented on GitHub (Mar 27, 2018):

@netblue30 It conflicts with seccomp. How would I go about knowing what to keep and what not? e.g.

seccomp.keep poll,select,nanosleep

Thanks!

@ghost commented on GitHub (Mar 27, 2018): @netblue30 It conflicts with seccomp. How would I go about knowing what to keep and what not? e.g. `seccomp.keep poll,select,nanosleep` Thanks!

gitea-mirror commented

2026-05-05 07:43:32 -06:00

Author

Owner

@Sector14 commented on GitHub (Oct 19, 2018):

Ran into this issue also. F1 2017 won't run unless seccomp is commented out in steam.profile. Has anyone found what the cause is and a workaround that allows seccomp to be left enabled?

@Sector14 commented on GitHub (Oct 19, 2018): Ran into this issue also. F1 2017 won't run unless seccomp is commented out in steam.profile. Has anyone found what the cause is and a workaround that allows seccomp to be left enabled?

gitea-mirror commented

2026-05-05 07:43:33 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (May 21, 2019):

You should be able to use the audit log to figure out which syscall it's trying to call which is killing it (e.g. sudo ausearch --raw after it's killed).

@chiraag-nataraj commented on GitHub (May 21, 2019): You should be able to use the audit log to figure out which syscall it's trying to call which is killing it (e.g. `sudo ausearch --raw` after it's killed).

gitea-mirror commented

2026-05-05 07:43:36 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (May 29, 2019):

Closing for inactivity. @amarildojr or @Sector14, please feel free to re-open and provide more info to help us figure out how we can fix this.

@chiraag-nataraj commented on GitHub (May 29, 2019): Closing for inactivity. @amarildojr or @Sector14, please feel free to re-open and provide more info to help us figure out how we can fix this.

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#1247

No description provided.

Rows
Columns