[GH-ISSUE #1378] /usr/bin/dbus-launch inhibits --x11 server exit. Blacklisting it seems to fix it. #941

Closed
opened 2026-05-05 07:11:55 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @caoliver on GitHub (Jul 13, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1378

I'm not sure if this is documented, but some applications run dbus-launch when they start. This grabs the containing X server, and that server persists after the desired clients exit. The work-around I've just started playing with is to blacklist /usr/bin/dbus-launch. So far, this seems to do the trick, and the server now exits cleanly on application exit.

Example: firejail --net=eth0 --x11 --blacklist=/usr/bin/dbus-launch firefox

Originally created by @caoliver on GitHub (Jul 13, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1378 I'm not sure if this is documented, but some applications run dbus-launch when they start. This grabs the containing X server, and that server persists after the desired clients exit. The work-around I've just started playing with is to blacklist /usr/bin/dbus-launch. So far, this seems to do the trick, and the server now exits cleanly on application exit. Example: firejail --net=eth0 --x11 --blacklist=/usr/bin/dbus-launch firefox
gitea-mirror 2026-05-05 07:11:55 -06:00
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 22, 2018):

Yeah, we see this with gpg-agent sometimes as well (although on systemd systems, you can just use writable-run-user to allow the program to connect to the user's instance of gpg-agent).

<!-- gh-comment-id:406900517 --> @chiraag-nataraj commented on GitHub (Jul 22, 2018): Yeah, we see this with `gpg-agent` sometimes as well (although on systemd systems, you can just use `writable-run-user` to allow the program to connect to the user's instance of `gpg-agent`).
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 22, 2018):

We don't really have a way to fix this at present, since as far as firejail is concerned, there's still a process running within the sandbox.

<!-- gh-comment-id:406900575 --> @chiraag-nataraj commented on GitHub (Jul 22, 2018): We don't really have a way to fix this at present, since as far as `firejail` is concerned, there's still a process running within the sandbox.
Author
Owner

@Fred-Barclay commented on GitHub (Jul 22, 2018):

@chiraag-nataraj Firejail processes from thunderbird always seem to stick around on my system -- maybe this is why? I do have the enigmail extension so it probably calls some gpg stuff.

<!-- gh-comment-id:406901015 --> @Fred-Barclay commented on GitHub (Jul 22, 2018): @chiraag-nataraj Firejail processes from thunderbird always seem to stick around on my system -- maybe this is why? I do have the enigmail extension so it probably calls some gpg stuff.
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 23, 2018):

Yeah, if you run firejail --tree, you should see what's stuck around - in your case, it's probably gpg-agent.

<!-- gh-comment-id:406908531 --> @chiraag-nataraj commented on GitHub (Jul 23, 2018): Yeah, if you run `firejail --tree`, you should see what's stuck around - in your case, it's probably `gpg-agent`.
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#941
No description provided.