mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1939] Firefox version 60 breaks completely with the default Firejail profile or any profile containing seccomp. #1294
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#1294
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 @dkwls on GitHub (May 11, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1939
@SkewedZeppelin commented on GitHub (May 11, 2018):
See #1930 and #1937
The fix (#1935) has been merged and is in master as
64914b7ae7@dkwls commented on GitHub (May 11, 2018):
Thanks for the response. I may be missing something but weather or not tracelog is in the profile appears to have no effect at least in version 0.9.52. Commenting out seccomp is the only way I have found to get Firefox to work again. I have tested this problem in Ubuntu 18.04 and 17.10.
@smitsohu commented on GitHub (May 11, 2018):
@dkwls Which Firejail version do you use?
EDIT:
I should read more carefully 😄
@smitsohu commented on GitHub (May 11, 2018):
We had to take out chroot from the seccomp filter to get Firefox working. If you replace
seccompwith the following long line it should work again:seccomp.drop @clock,@cpu-emulation,@debug,@module,@obsolete,@raw-io,@reboot,@resources,@swap,acct,add_key,bpf,fanotify_init,io_cancel,io_destroy,io_getevents,io_setup,io_submit,ioprio_set,kcmp,keyctl,mount,name_to_handle_at,nfsservctl,ni_syscall,open_by_handle_at,personality,pivot_root,process_vm_readv,ptrace,remap_file_pages,request_key,setdomainname,sethostname,syslog,umount,umount2,userfaultfd,vhangup,vmspliceThis will be fixed in 0.9.54.
@Vincent43 commented on GitHub (May 11, 2018):
Here's some info about sandboxing in FF 60: https://www.morbo.org/2018/05/linux-sandboxing-improvements-in_10.html
@Wolf-Italy commented on GitHub (May 11, 2018):
To your kind attention.
I would like to point out, a problem between firejail and the
new version of Firefox 60.0
I just installed the new version of Firefox 60.0,
in Linux Mint 18.3 Sylvia
I use LTS version firejail_0.9.38.12_1_amd64.deb
The Browser starts, but the page remains blank.
See screenshots:
https://imgur.com/a/YE2L2Et
This problem seems to be the same, which happened a while ago,
With the Sandboxie program, the problem was due to
Multiprocess function.
Translated with www.DeepL.com/Translator
@dkwls commented on GitHub (May 11, 2018):
@smitsohu thank you that fixed the problem for me.
@Queeq commented on GitHub (May 12, 2018):
I tried using
seccomp.keepoption instead of listing all syscalls explicitly (this is much cleaner), but it then fails to start:Do I understand its function incorrectly?
firejail version 0.9.38.10
Linux Mint 18.3
@Vincent43 commented on GitHub (May 12, 2018):
seccomp.keepis the opposite ofsecomp.drop, it creates whitelist instead of blacklist. You have to pass explicitly each allowed syscall, probably not what you want.@Queeq commented on GitHub (May 12, 2018):
Right, so I was trying to pass chroot.
@Wolf-Italy commented on GitHub (May 13, 2018):
To your kind attention.
As indicated, in Support I installed firejail_0.9.54~rc2_1_amd64.deb
Firefox 60.0 works correctly.
See screenshot:
https://imgur.com/a/YOovTGx
Thank you.
@Fred-Barclay commented on GitHub (May 13, 2018):
@Wolf-Italy Excellent, that's exactly what we want to hear. Thanks!