github-starred/firejail

Fork 0

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

[GH-ISSUE #1400] Xpra killing emacs daemon on exit #955

New issue

Closed

opened 2026-05-05 07:13:09 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 07:13:09 -06:00

Owner

Originally created by @chiraag-nataraj on GitHub (Jul 24, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1400

When I use x11 xpra with e.g. Mutt (something with a temporary xpra instance which is created upon launch), Xpra ends up killing the emacs daemon I start outside of the sandbox when Mutt exits.

Is this intended behavior?
If it is, how do I modify it or prevent this from happening?

Originally created by @chiraag-nataraj on GitHub (Jul 24, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1400 When I use `x11 xpra` with e.g. Mutt (something with a temporary xpra instance which is created upon launch), Xpra ends up killing the emacs daemon I start outside of the sandbox when Mutt exits. - Is this intended behavior? - If it is, how do I modify it or prevent this from happening?

gitea-mirror closed this issue

2026-05-05 07:13:11 -06:00

gitea-mirror commented

2026-05-05 07:13:13 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 24, 2017):

Just to clarify, this does not happen if I start an xpra instance independently and then pass the display as an environment variable to firejail (that is how I've mitigated this issue at the moment).

@chiraag-nataraj commented on GitHub (Jul 24, 2017): Just to clarify, this does not happen if I start an xpra instance independently and then pass the display as an environment variable to firejail (that is how I've mitigated this issue at the moment).

gitea-mirror commented

2026-05-05 07:13:14 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 24, 2017):

Even weirder...if I terminate existing Xpra instances, it also kills emacs. So I suppose this isn't a firejail-specific thing (although the temporary nature of the Xpra daemon in that case exacerbates the problem).

@chiraag-nataraj commented on GitHub (Jul 24, 2017): Even weirder...if I terminate existing Xpra instances, it also kills emacs. So I suppose this isn't a firejail-specific thing (although the temporary nature of the Xpra daemon in that case exacerbates the problem).

gitea-mirror commented

2026-05-05 07:13:15 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 30, 2017):

I will post this to the xpra bug tracker since I don't think this is related to firejail.

@chiraag-nataraj commented on GitHub (Jul 30, 2017): I will post this to the xpra bug tracker since I don't think this is related to firejail.

gitea-mirror commented

2026-05-05 07:13:16 -06:00

Author

Owner

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

Found something funny: if I add my user to tty group it solves the problem. It seems to be fixing the crash on the latest Ubuntu derivatives such as xubuntu. It could be something with the way xorg is set up.

@netblue30 commented on GitHub (Aug 5, 2017): Found something funny: if I add my user to tty group it solves the problem. It seems to be fixing the crash on the latest Ubuntu derivatives such as xubuntu. It could be something with the way xorg is set up.

gitea-mirror commented

2026-05-05 07:13:17 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Aug 5, 2017):

Hmmm okay, I will try that.

@chiraag-nataraj commented on GitHub (Aug 5, 2017): Hmmm okay, I will try that.

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

No description provided.

Rows
Columns