[GH-ISSUE #1939] Firefox version 60 breaks completely with the default Firejail profile or any profile containing seccomp. #1294

Closed
opened 2026-05-05 07:48:50 -06:00 by gitea-mirror · 12 comments
Owner

Originally created by @dkwls on GitHub (May 11, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1939

Originally created by @dkwls on GitHub (May 11, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/1939
Author
Owner

@SkewedZeppelin commented on GitHub (May 11, 2018):

See #1930 and #1937

The fix (#1935) has been merged and is in master as 64914b7ae7

<!-- gh-comment-id:388331255 --> @SkewedZeppelin commented on GitHub (May 11, 2018): See #1930 and #1937 The fix (#1935) has been merged and is in master as 64914b7ae78484483dd0f736f3eefcec4342482e
Author
Owner

@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.

<!-- gh-comment-id:388342534 --> @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.
Author
Owner

@smitsohu commented on GitHub (May 11, 2018):

@dkwls Which Firejail version do you use?

EDIT:

appears to have no effect at least in version 0.9.52

I should read more carefully 😄

<!-- gh-comment-id:388355047 --> @smitsohu commented on GitHub (May 11, 2018): @dkwls Which Firejail version do you use? EDIT: > appears to have no effect at least in version 0.9.52 I should read more carefully :smile:
Author
Owner

@smitsohu commented on GitHub (May 11, 2018):

We had to take out chroot from the seccomp filter to get Firefox working. If you replace seccomp with 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,vmsplice

This will be fixed in 0.9.54.

<!-- gh-comment-id:388358648 --> @smitsohu commented on GitHub (May 11, 2018): We had to take out chroot from the seccomp filter to get Firefox working. If you replace `seccomp` with 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,vmsplice` This will be fixed in 0.9.54.
Author
Owner

@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

<!-- gh-comment-id:388366586 --> @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
Author
Owner

@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

<!-- gh-comment-id:388368290 --> @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
Author
Owner

@dkwls commented on GitHub (May 11, 2018):

@smitsohu thank you that fixed the problem for me.

<!-- gh-comment-id:388496961 --> @dkwls commented on GitHub (May 11, 2018): @smitsohu thank you that fixed the problem for me.
Author
Owner

@Queeq commented on GitHub (May 12, 2018):

I tried using seccomp.keep option instead of listing all syscalls explicitly (this is much cleaner), but it then fails to start:

Error: cannot establish communication with the parent, exiting...

Do I understand its function incorrectly?

firejail version 0.9.38.10
Linux Mint 18.3

<!-- gh-comment-id:388538909 --> @Queeq commented on GitHub (May 12, 2018): I tried using `seccomp.keep` option instead of listing all syscalls explicitly (this is much cleaner), but it then fails to start: ``` Error: cannot establish communication with the parent, exiting... ``` Do I understand its function incorrectly? firejail version 0.9.38.10 Linux Mint 18.3
Author
Owner

@Vincent43 commented on GitHub (May 12, 2018):

seccomp.keep is the opposite of secomp.drop, it creates whitelist instead of blacklist. You have to pass explicitly each allowed syscall, probably not what you want.

<!-- gh-comment-id:388540776 --> @Vincent43 commented on GitHub (May 12, 2018): `seccomp.keep` is the opposite of `secomp.drop`, it creates whitelist instead of blacklist. You have to pass explicitly each allowed syscall, probably not what you want.
Author
Owner

@Queeq commented on GitHub (May 12, 2018):

Right, so I was trying to pass chroot.

<!-- gh-comment-id:388540905 --> @Queeq commented on GitHub (May 12, 2018): Right, so I was trying to pass chroot.
Author
Owner

@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.

<!-- gh-comment-id:388607030 --> @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.
Author
Owner

@Fred-Barclay commented on GitHub (May 13, 2018):

@Wolf-Italy Excellent, that's exactly what we want to hear. Thanks!

<!-- gh-comment-id:388638783 --> @Fred-Barclay commented on GitHub (May 13, 2018): @Wolf-Italy Excellent, that's exactly what we want to hear. Thanks!
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#1294
No description provided.