github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #1589] Firejail still running after closing Firefox #1058

New issue

Closed

opened 2026-05-05 07:22:37 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 07:22:37 -06:00

Owner

Originally created by @selectiveduplicate on GitHub (Oct 4, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1589

I previously wrote about certain warning messages that I receive here: #1576 ...

Just today I've got a pile of those random messages (I had been using it for a long time, so...), and when I closed Firefox, I found that my Firejail session is still running...

As you can see the list is quite much, I can't really provide all the messages...

Somewhat similar issue happened before, in that scenario I wasn't able to close Firefox at all and so couldn't open another Firefox session, and finally Firefox crashed...

Right now, I'm writing this post from a normal Firefox session, not a Firejail-sandboxed one, while my previous Firejail session is still running, as seen from the photo...

If any other information is needed in this regard, I'd be happy to provide!

Thanks!

Originally created by @selectiveduplicate on GitHub (Oct 4, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1589 I previously wrote about certain warning messages that I receive here: #1576 ... Just today I've got a pile of those random messages (I had been using it for a long time, so...), and when I closed Firefox, I found that my Firejail session is still running... ![fire_bug](https://user-images.githubusercontent.com/32275394/31196085-5084d90a-a96e-11e7-8a8f-a7bcd785fb59.png) As you can see the list is quite much, I can't really provide all the messages... Somewhat similar issue happened before, in that scenario I wasn't able to close Firefox at all and so couldn't open another Firefox session, and finally Firefox crashed... Right now, I'm writing this post from a normal Firefox session, not a Firejail-sandboxed one, while my previous Firejail session is still running, as seen from the photo... If any other information is needed in this regard, I'd be happy to provide! Thanks!

gitea-mirror

2026-05-05 07:22:37 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 07:22:40 -06:00

Author

Owner

@SkewedZeppelin commented on GitHub (Oct 5, 2017):

None of those error messages really matter.

As for why its still running... are you running the non-Firejailed version with -no-remote? Because if you aren't, your non-sandboxed Firefox instance is really actually running under the Firejailed instance. Which would explain why its still running.

@SkewedZeppelin commented on GitHub (Oct 5, 2017): None of those error messages really matter. As for why its still running... are you running the non-Firejailed version with `-no-remote`? Because if you aren't, your non-sandboxed Firefox instance is really actually running under the Firejailed instance. Which would explain why its still running.

gitea-mirror commented

2026-05-05 07:22:42 -06:00

Author

Owner

@selectiveduplicate commented on GitHub (Oct 6, 2017):

No, I'm not running with -no-remote( I've never used it actually)... generally I start a sandboxed Firefox with firejail firefox and when I close it, Firejail also closes (parent is shutting down, bye)... but in this case Firejail didn't close. If I want to start a normal Firefox session, I just launch it from my launcher. Just now I'm running a normal session...

@selectiveduplicate commented on GitHub (Oct 6, 2017): No, I'm not running with `-no-remote`( I've never used it actually)... generally I start a sandboxed Firefox with `firejail firefox` and when I close it, Firejail also closes (**parent is shutting down, bye**)... but in this case Firejail didn't close. If I want to start a normal Firefox session, I just launch it from my launcher. Just now I'm running a normal session...

gitea-mirror commented

2026-05-05 07:22:44 -06:00

Author

Owner

@netblue30 commented on GitHub (Oct 6, 2017):

but in this case Firefox didn't close

In a different terminal run firejail --tree" and put the output of the command here. It will tell us what process in still running in the sandbox after you closed firefox.

@netblue30 commented on GitHub (Oct 6, 2017): > but in this case Firefox didn't close In a different terminal run firejail --tree" and put the output of the command here. It will tell us what process in still running in the sandbox after you closed firefox.

gitea-mirror commented

2026-05-05 07:22:46 -06:00

Author

Owner

@selectiveduplicate commented on GitHub (Oct 6, 2017):

Sorry, I miswrote... actually I meant

Firejail didn't close

@selectiveduplicate commented on GitHub (Oct 6, 2017): Sorry, I miswrote... actually I meant >Firejail didn't close

gitea-mirror commented

2026-05-05 07:22:47 -06:00

Author

Owner

@netblue30 commented on GitHub (Oct 10, 2017):

Just run "firejail --tree". Firejail will not close if there is something running inside the sandbox. It will wait for all processes to finish.

@netblue30 commented on GitHub (Oct 10, 2017): Just run "firejail --tree". Firejail will not close if there is something running inside the sandbox. It will wait for all processes to finish.

gitea-mirror referenced this issue

2026-05-05 10:08:53 -06:00

[PR #1062] [MERGED] Add support for joining a persistent, named network namespace. #3840

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#1058

No description provided.

Rows
Columns