github-starred/firejail

Fork 0

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

[GH-ISSUE #1319] [DOC] Firefox doesn’t open in a new sandbox... #900

New issue

Closed

opened 2026-05-05 07:05:33 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 07:05:33 -06:00

Owner

Originally created by @Anyon3 on GitHub (May 29, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1319

Firefox doesn’t open in a new sandbox. Instead, it opens a new tab in an existing Firefox
instance

By default, Firefox browser uses a single process to handle multiple windows. When you start the browser, if another Firefox process is already running, the existing process opens a new tab or a new window. Make sure Firefox is not already running when you start it in Firejail sandbox.

To open a new firefox instance, you can use the following argument --new-instance (with firefox, example : firefox --new-instance)

I think this point should be add on this part of the FAQ. It could be necessary to pass -P argument to select a different profile for each new instance if you handle different FIrefox profile in the same home directory

Hope it's helpful

Thanks,

Edit : I made several test and can confirm --new-instance, no matter if one or more Firefox processus are running, will create a new uniq firefox processus.

Torbrowser will have the same effect if a Firefox processus is already running. A bigger problem related to TB is : While another processus of Firefox is running and no argument --new-instance was used, TB will keep your session data (history, cookie, cache...) after you close it as long a Firefox processus is running.

Originally created by @Anyon3 on GitHub (May 29, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1319 > Firefox doesn’t open in a new sandbox. Instead, it opens a new tab in an existing Firefox instance > > By default, Firefox browser uses a single process to handle multiple windows. When you start the browser, if another Firefox process is already running, the existing process opens a new tab or a new window. Make sure Firefox is not already running when you start it in Firejail sandbox. To open a new firefox instance, you can use the following argument --new-instance (with firefox, example : firefox --new-instance) I think this point should be add on this part of the FAQ. It could be necessary to pass -P argument to select a different profile for each new instance if you handle different FIrefox profile in the same home directory Hope it's helpful Thanks, Edit : I made several test and can confirm --new-instance, no matter if one or more Firefox processus are running, will create a new uniq firefox processus. Torbrowser will have the same effect if a Firefox processus is already running. A bigger problem related to TB is : While another processus of Firefox is running and no argument --new-instance was used, TB will keep your session data (history, cookie, cache...) after you close it as long a Firefox processus is running.

gitea-mirror

2026-05-05 07:05:33 -06:00

closed this issue
added the
enhancement
label

gitea-mirror commented

2026-05-05 07:05:43 -06:00

Author

Owner

@netblue30 commented on GitHub (Jun 4, 2017):

all set: https://firejail.wordpress.com/support/frequently-asked-questions/#firefox-dual

@netblue30 commented on GitHub (Jun 4, 2017): all set: https://firejail.wordpress.com/support/frequently-asked-questions/#firefox-dual

gitea-mirror commented

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

Author

Owner

@Anyon3 commented on GitHub (Jun 5, 2017):

You right, I missed this argument (--no-remote), my bad.

@Anyon3 commented on GitHub (Jun 5, 2017): You right, I missed this argument (--no-remote), my bad.

gitea-mirror commented

2026-05-05 07:05:49 -06:00

Author

Owner

@netblue30 commented on GitHub (Jun 5, 2017):

I think --no-remote and --new-instance are equivalent, or the difference between them is very small. They both do the job.

@netblue30 commented on GitHub (Jun 5, 2017): I think --no-remote and --new-instance are equivalent, or the difference between them is very small. They both do the job.

gitea-mirror referenced this issue

2026-05-05 10:07:57 -06:00

[PR #900] [MERGED] completed ecryptfs blacklist #3791

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

No description provided.

Rows
Columns