[GH-ISSUE #648] xpra persists after firejailed app is quit #448

Closed
opened 2026-05-05 05:53:14 -06:00 by gitea-mirror · 6 comments
Owner

Originally created by @xahare on GitHub (Jul 26, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/648

firejail version 0.9.42~rc1 ubuntu 16.04.1 amd64, same behavior in 0.9.40.1
running firejail like this,

firejail --name=workbrowser --x11 --net=fj0 --dns=8.8.8.8,8.8.4.4 --private=~/firejail/workbrowser google-chrome

the xpra session persists after the jailed app is quit.

Originally created by @xahare on GitHub (Jul 26, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/648 firejail version 0.9.42~rc1 ubuntu 16.04.1 amd64, same behavior in 0.9.40.1 running firejail like this, ``` firejail --name=workbrowser --x11 --net=fj0 --dns=8.8.8.8,8.8.4.4 --private=~/firejail/workbrowser google-chrome ``` the xpra session persists after the jailed app is quit.
gitea-mirror 2026-05-05 05:53:14 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@netblue30 commented on GitHub (Jul 27, 2016):

I've seen this happening on Debian Wheezy (old stable) with a old version of xpra. Yes, sometimes it doesn't attach.

What distro are you using, what is the version of xpra (xpra --version)?

<!-- gh-comment-id:235703625 --> @netblue30 commented on GitHub (Jul 27, 2016): I've seen this happening on Debian Wheezy (old stable) with a old version of xpra. Yes, sometimes it doesn't attach. What distro are you using, what is the version of xpra (xpra --version)?
Author
Owner

@xahare commented on GitHub (Aug 1, 2016):

Ubuntu 16.04.1 LTS
xpra v0.17.4

<!-- gh-comment-id:236581035 --> @xahare commented on GitHub (Aug 1, 2016): Ubuntu 16.04.1 LTS xpra v0.17.4
Author
Owner

@netblue30 commented on GitHub (Aug 2, 2016):

It is possible it was fixed by this commit: https://github.com/netblue30/firejail/pull/679

There is more testing coming.

<!-- gh-comment-id:236900311 --> @netblue30 commented on GitHub (Aug 2, 2016): It is possible it was fixed by this commit: https://github.com/netblue30/firejail/pull/679 There is more testing coming.
Author
Owner

@xahare commented on GitHub (Aug 2, 2016):

those changes only apply to xephyr.

<!-- gh-comment-id:236901409 --> @xahare commented on GitHub (Aug 2, 2016): those changes only apply to xephyr.
Author
Owner

@netblue30 commented on GitHub (Aug 4, 2016):

You are right, sorry.

<!-- gh-comment-id:237550126 --> @netblue30 commented on GitHub (Aug 4, 2016): You are right, sorry.
Author
Owner

@netblue30 commented on GitHub (Aug 12, 2016):

All fixed.

<!-- gh-comment-id:239459841 --> @netblue30 commented on GitHub (Aug 12, 2016): All fixed.
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#448
No description provided.