mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1101] Latest firefox doesn't work with firejail #755
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#755
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 @Pentarctagon on GitHub (Feb 13, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1101
Firefox version is 53.0a2(downloaded to my desktop from here, e10s is enabled)
Firejail version is 0.9.44.8
OS is Mint 18.1
When starting firefox through firejail, it shows the following:
My profile:
I also modified /usr/bin/firefox to do:
exec firejail --name=foxjail /home/derpy/Desktop/firefox/firefox "$@"Using
--forcedoes not help.@curiosity-seeker commented on GitHub (Feb 13, 2017):
I suspect that this might be caused by the fact that sandboxing finally might be enabled in that version which is based on seccomp-bpf. If that's the case this probably collides with the Firejail seccomp option (as it is the case for Chromium/Chrome).
So you can try 2 things to solve the problem:
seccompin the Firejail profile.@Pentarctagon commented on GitHub (Feb 13, 2017):
For 1) removing
seccompfrom the profile does not fix the problem.For 2) I attempted to disable seccomp via this environment variable, which didn't help. Neither did using about:config to disable the sandbox as a whole. In fact, neither of these seem to do anything at all. The about:config entries didn't even exist and I had to create them myself. Disabling e10s also did not cause the error to go away.
@netblue30 commented on GitHub (Feb 13, 2017):
I got the developer version from your link, and is working fine. Apparently, they don't start the sandbox by default.
@Pentarctagon commented on GitHub (Feb 14, 2017):
Huh, that's odd. I've changed quite a few things, but the sandbox was never one of them. I have been thinking of starting over with a fresh profile for a while though; maybe it's time I finally do that.
Thanks for the replies.