[GH-ISSUE #1937] Firefox 60 does not close #1296

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

Originally created by @curiosity-seeker on GitHub (May 10, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1937

I'm having problems with FF 60 on Fedora 28 KDE with the existing profile. Whenever I close Firefox I can still see processes in the task manager (and FF can't be restarted):

grafik

After killing those processes and starting FF anew, quite often it's not possible to load any websites.

I haven't had time enough to do a thorough research regarding the culprit - but a combination of 3 measures seem to be necessary here to make FF work reliably again:

  1. Remove ptrace from seccomp.drop
  2. Comment nodbus
  3. Comment private-dev

Can anybody reproduce my findings?

Originally created by @curiosity-seeker on GitHub (May 10, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/1937 I'm having problems with FF 60 on Fedora 28 KDE with the existing profile. Whenever I close Firefox I can still see processes in the task manager (and FF can't be restarted): ![grafik](https://user-images.githubusercontent.com/14075215/39883503-8bea9594-5476-11e8-97d6-531797536e76.png) After killing those processes and starting FF anew, quite often it's not possible to load any websites. I haven't had time enough to do a thorough research regarding the culprit - but a combination of 3 measures seem to be necessary here to make FF work reliably again: 1. Remove `ptrace` from `seccomp.drop` 2. Comment `nodbus` 3. Comment `private-dev` Can anybody reproduce my findings?
Author
Owner

@curiosity-seeker commented on GitHub (May 10, 2018):

Oops - I just saw this pull request. And indeed - the culprit seems to be tracelog. After commenting it and reverting the other changes everything seems to work well again.

<!-- gh-comment-id:388126764 --> @curiosity-seeker commented on GitHub (May 10, 2018): Oops - I just saw [this](https://github.com/netblue30/firejail/pull/1935) pull request. And indeed - the culprit seems to be `tracelog`. After commenting it and reverting the other changes everything seems to work well again.
Author
Owner

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

Fixed with 6830065197

<!-- gh-comment-id:388310753 --> @Vincent43 commented on GitHub (May 11, 2018): Fixed with https://github.com/netblue30/firejail/commit/6830065197cc574898850bb7f2b2f5b214505704
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#1296
No description provided.