mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3837] firefox: firefox -p fails to launch (seccomp) #2414
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#2414
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 @EauBureau on GitHub (Dec 18, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3837
Since upgrading to Firefox 84 it no longer launches using
$ fireljail firefox -pFirefox's profile selector window is supposed to open.
Using
$ firejail firefoxdoes work. i.e Firefox opens and runs without profile selector option.Using
$ firefox -pdoes work. i.e. without firejail the profile selector window appearsUbuntu 20.04 LTS
firejail version 0.9.62
@rusty-snake commented on GitHub (Dec 19, 2020):
I can not reproduce this.
@EauBureau commented on GitHub (Dec 19, 2020):
Here's
jounralctl -ffor the following if they're of any use@rusty-snake commented on GitHub (Dec 19, 2020):
Maybe
firejail '--seccomp=!chroot,!kcmp' firefox -pworks.@EauBureau commented on GitHub (Dec 21, 2020):
Unfortunately it doesn't.
@rusty-snake commented on GitHub (Dec 21, 2020):
Gotcha! The
seccompin the profile overrides theseccompon the command line. See "Seccomp list in: !chroot, check list: @default-keep, prelist: unknown,".firejail '--seccomp=!chroot,!kcmp' '--ignore=seccomp' firefox -p.@EauBureau commented on GitHub (Dec 22, 2020):
Great job. Thank you.
What does this mean: for now I use the new command above, but down the road when a newer version of firejail is released the previous simple
firejail firefox -pwill work again?Or is this issue somehow just relevant to my system's setup?
Edit: Does running with the workaround command diminish the security at all?
@rusty-snake commented on GitHub (Dec 22, 2020):
#3219
You can also add the
!kcmpto your firefox.profile/firefox.local, sofirejail firefox -pworks.It allows the
kcmpsyscall.@EauBureau commented on GitHub (Dec 23, 2020):
That's perfect, thanks.
Will I close this or do you want to keep it open?
@rusty-snake commented on GitHub (Dec 23, 2020):
Yes, I think we can closes here, there is still #3219 for a general solution on kcmp in mesa+amd.