mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #5186] steam: Paradox Interactive Lancher does not open (missing whitelist) #2906
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#2906
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @swimik on GitHub (Jun 9, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5186
Is your feature request related to a problem? Please describe.
On Debian bullseye with Steam installed via Debian repo and a game installed that uses Paradox Interactive Launcher a folder is required to be whitelisted for the launcher to open.
Without the folder being whitelisted the Paradox Launcher will fail to load with a 'permission denied' error and it will ask to reinstall the launcher, which also fails.
Describe the solution you'd like
add to the whitelist for steam.profile the following
whitelist ${HOME}/.paradoxlauncher
Describe alternatives you've considered
There does not seem to be an alternative.
Additional context
I am using firejail 0.9.64.4-2 with default steam.profile
the master steam.profile also lacks this folder in the whitelist
@rusty-snake commented on GitHub (Jun 9, 2022):
Open a PR ;)
@swimik commented on GitHub (Jun 9, 2022):
Sorry, was not sure of the proper way to submit this. Will do
@kmk3 commented on GitHub (Aug 20, 2022):
Fixed by #5223.