[GH-ISSUE #6705] Error: preproc_lock_file: open: Permission denied (SELinux) #3343

Open
opened 2026-05-05 09:55:47 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @disposableone on GitHub (Apr 10, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6705

Fedora 40. Confined user (staff_u). Firejail errors out when launching firejail firefox:

Error: cannot create a lockfile at /run/firejail/firejail-run.lock
Error ../../src/frejail/preproc.c:47: preproc_lock_file: open: Permission denied

I know this may be a SELinux policy problem... but maybe something Firejail should be doing differently? And how would we mitigate this, since this is the default SELinux policy on Fedora 40?

Originally created by @disposableone on GitHub (Apr 10, 2025). Original GitHub issue: https://github.com/netblue30/firejail/issues/6705 Fedora 40. Confined user (staff_u). Firejail errors out when launching `firejail firefox`: ``` Error: cannot create a lockfile at /run/firejail/firejail-run.lock Error ../../src/frejail/preproc.c:47: preproc_lock_file: open: Permission denied ``` I know this may be a SELinux policy problem... but maybe something Firejail should be doing differently? And how would we mitigate this, since this is the default SELinux policy on Fedora 40?
gitea-mirror added the
needinfo
label 2026-05-05 09:55:47 -06:00
Author
Owner

@disposableone commented on GitHub (Apr 10, 2025):

It's getting SELinux write denial:

name="firejail-run.lock" scontext=staff_u:staff_r:staff_t tcontext=unconfined_u:object_r:var_run_t
<!-- gh-comment-id:2795075986 --> @disposableone commented on GitHub (Apr 10, 2025): It's getting SELinux write denial: ``` name="firejail-run.lock" scontext=staff_u:staff_r:staff_t tcontext=unconfined_u:object_r:var_run_t ```
Author
Owner

@kmk3 commented on GitHub (Apr 12, 2025):

Basic debugging information is missing; please follow the bug report template:

<!-- gh-comment-id:2798504113 --> @kmk3 commented on GitHub (Apr 12, 2025): Basic debugging information is missing; please follow the bug report template: * <https://github.com/netblue30/firejail/issues/new?template=bug_report.md>
Author
Owner

@kmk3 commented on GitHub (Apr 12, 2025):

(Offtopic)

Please see the following links for how to format code blocks in markdown:

<!-- gh-comment-id:2798504159 --> @kmk3 commented on GitHub (Apr 12, 2025): (Offtopic) Please see the following links for how to format code blocks in markdown: * <https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks> * <https://github.github.com/gfm/#fenced-code-blocks>
Sign in to join this conversation.
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#3343
No description provided.