mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2616] Firefox 66 is using chroot. Ubuntu 16.04 with seccomp enabled will break firefox. #1659
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#1659
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 @Shifting5164 on GitHub (Mar 23, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2616
Running system:
Mozilla Firefox 66.0
Ubuntu 16.04.6 LTS
firejail version 0.9.38.10
Excluding:
Excluding current GTK_IM_MODULE problems with ibus.
Fix:
xim firejail firefoxProblem description:
Firefox does not appear to load any webpage. Screen remains blank.
Reproducing error:
firejail firefox -no-remote
Error tracing:
Syslog will show the flowing message
syscall=161 = chroot
Running firefox strace native it turns out firefox is using the chroot syscal
Circumvention:
/etc/firejail/firefox.profile
NOTE: This will completely disable seccomp protection. This is NOT a fix
@SkewedZeppelin commented on GitHub (Mar 23, 2019):
iirc this has been fixed since 0.9.54
you can use this profile instead https://github.com/netblue30/firejail/blob/master/etc-fixes/0.9.38/firefox.profile
@Shifting5164 commented on GitHub (Mar 23, 2019):
Yes, it is fixed in this version.
Thanks