mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4543] --join-or-start=program shouldn't create program-PID sandboxes if multiple instances try to start simultaneously. #2700
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#2700
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 @crocket on GitHub (Sep 14, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4543
If my bookmark manager tries to open multiple bookmarks by launching multiple invocations of
firejail --join-or-start=librewolf librewolf URLsimultaneously, the first invocation createslibrewolfsandbox and some of subsequent invocations end up creatinglibrewolf-PIDsandboxes.If multiple firejail invocations are trying to launch simultaneously with
--join-or-start=program, the first invocation should reserve a named sandbox which subsequent invocations wait for before joining the named sandbox.Because not all invocations of librewolf join the same sandbox, I had to insert
into
librewolf.localin order to launch multiple bookmarks simultaneously on librewolf.If
--join-or-startwas good at putting all simultaneous invocations of firejail in one named sandbox, I didn't need to make all librewolf instances share /tmp and dbus with programs outside sandbox.@rusty-snake commented on GitHub (Sep 14, 2021):
Previous discussion: #4538
@rusty-snake commented on GitHub (Jun 8, 2022):
firejail 0.9.70 has improved join code, can you test if this still happens with it when it is released.
@crocket commented on GitHub (Jun 9, 2022):
I will test. Just notify me on this issue when it's released.
@kmk3 commented on GitHub (Jun 9, 2022):
It has been released.
Note that you can subscribe to new releases through the Watch button (next to
the Fork button).
@crocket commented on GitHub (Jun 10, 2022):
I installed 0.9.70 and rebooted. I tested librewolf with
join-or-start librewolfin librewolf.local.The issue was reproduced reliably. I still need to ignore private-tmp and dbus-user.
@Stoxis commented on GitHub (May 22, 2023):
This fix for librewolf doesn't work
How do I fix this? I don't receive the error when I launch tabs using the commandline with firefox, only librewolf. Both are using firejail.
@rusty-snake commented on GitHub (May 22, 2023):
@Stoxis did you got that will bulk opening link or with only one link? If you got it with only one link, it has a different cause. Open a new Discussion then. (There are already a lot for Firefox).
@Stoxis commented on GitHub (May 23, 2023):
If I run the command
librewolf google.com/it'll work the first time, but if I try to run the command a second time while the previous instance is still open I'll get the "Firefox is already running" error.If I do the same thing
firefox google.com/I can do it as many times as I want to open new tabs without encountering the error.Both Firefox and Librewolf are using Firejail.