github-starred/firejail

Fork 0

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

[GH-ISSUE #1290] console switching, xpra crashes #877

New issue

Closed

opened 2026-05-05 07:01:57 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

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

Owner

Originally created by @gso on GitHub (May 21, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1290

This is possibly a downstream Xpra bug.

However, I switch from a graphical X server login to a text console quite frequently, when switching back to the X server any instances of firejail --x11=xpra ... crash (n.b. this is not a problem with --x11=xephyr).

I thought in the first instance xpra configuration options would solve the issue:

idle-timeout = 3600  # also tried '0' which should disable the timeout
server-idle-timeout = 3600  # also tried '0' which should disable the timeout
clipboard-direction = to-server
dpi = 96

While the clipboard conf. line worked as expected, console switching back to X still crashed any running instances of xpra with the following error:

2017-05-21 09:26:27,314 Disconnecting client /var/run/user/1001/xpra/localhost.localdomain-454:
2017-05-21 09:26:27,315  client ping timeout (waited 60 seconds without a response)
2017-05-21 09:26:27,331 xpra client 1 disconnected.
2017-05-21 09:33:56,292 server failure: client ping timeout
2017-05-21 09:33:56,293 server requested disconnect: client ping timeout (waited 60 seconds without a response)
2017-05-21 09:33:56,663 Connection lost

A [Ctrl]-C is needed to completely close firejail down at that point.

Current Firejail 0.9.46 build, Xpra 2.0.2, Fedora 25 (i386).

Originally created by @gso on GitHub (May 21, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1290 This is possibly a downstream Xpra bug. However, I switch from a graphical X server login to a text console quite frequently, when switching back to the X server any instances of `firejail --x11=xpra ...` crash (n.b. this is not a problem with `--x11=xephyr`). I thought in the first instance `xpra` configuration options would solve the issue: ``` idle-timeout = 3600 # also tried '0' which should disable the timeout server-idle-timeout = 3600 # also tried '0' which should disable the timeout clipboard-direction = to-server dpi = 96 ``` While the clipboard conf. line worked as expected, console switching back to X still crashed any running instances of `xpra` with the following error: ``` 2017-05-21 09:26:27,314 Disconnecting client /var/run/user/1001/xpra/localhost.localdomain-454: 2017-05-21 09:26:27,315 client ping timeout (waited 60 seconds without a response) 2017-05-21 09:26:27,331 xpra client 1 disconnected. 2017-05-21 09:33:56,292 server failure: client ping timeout 2017-05-21 09:33:56,293 server requested disconnect: client ping timeout (waited 60 seconds without a response) 2017-05-21 09:33:56,663 Connection lost ``` A `[Ctrl]-C` is needed to completely close `firejail` down at that point. Current Firejail 0.9.46 build, Xpra 2.0.2, Fedora 25 (i386).

gitea-mirror

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

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 07:02:04 -06:00

Author

Owner

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

Is this still an issue?

@chiraag-nataraj commented on GitHub (Jul 22, 2018): Is this still an issue?

gitea-mirror commented

2026-05-05 07:02:05 -06:00

Author

Owner

@owenh000 commented on GitHub (Apr 2, 2019):

I see this behavior on Devuan ascii (Debian Stretch). I tried firejail --x11 firefox and after some VT switches it crashed:

2019-04-01 19:30:51,740 Disconnecting client /home/user/.xpra/myhost-958:
2019-04-01 19:30:51,741  client ping timeout (waited 60 seconds without a response)
2019-04-01 19:30:51,758 xpra client disconnected.
2019-04-01 20:15:12,686 Connection lost
^C
Parent received signal 2, shutting down the child process...
Parent is shutting down, bye...
2019-04-01 20:49:14,726 got signal SIGINT, exiting
Child received signal 15, shutting down the sandbox...
2019-04-01 20:49:14,763 removing socket /home/user/.xpra/myhost-958
2019-04-01 20:49:14,763 killing xvfb with pid 2965
(II) Server terminated successfully (0). Closing log file.

Edit: firejail 0.9.44.8-2 or 0.9.58.2-1, xpra 0.17.6+dfsg-1

@owenh000 commented on GitHub (Apr 2, 2019): I see this behavior on Devuan ascii (Debian Stretch). I tried `firejail --x11 firefox` and after some VT switches it crashed: ``` 2019-04-01 19:30:51,740 Disconnecting client /home/user/.xpra/myhost-958: 2019-04-01 19:30:51,741 client ping timeout (waited 60 seconds without a response) 2019-04-01 19:30:51,758 xpra client disconnected. 2019-04-01 20:15:12,686 Connection lost ^C Parent received signal 2, shutting down the child process... Parent is shutting down, bye... 2019-04-01 20:49:14,726 got signal SIGINT, exiting Child received signal 15, shutting down the sandbox... 2019-04-01 20:49:14,763 removing socket /home/user/.xpra/myhost-958 2019-04-01 20:49:14,763 killing xvfb with pid 2965 (II) Server terminated successfully (0). Closing log file. ``` **Edit:** firejail 0.9.44.8-2 or 0.9.58.2-1, xpra 0.17.6+dfsg-1

gitea-mirror commented

2026-05-05 07:02:07 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (May 21, 2019):

Is this true if you manually start xpra and a random program (say, firefox or a terminal emulator) and do the VT switches? That is, if you run stuff without firejail, do you still run into this bug?

@chiraag-nataraj commented on GitHub (May 21, 2019): Is this true if you manually start `xpra` and a random program (say, `firefox` or a terminal emulator) and do the VT switches? That is, if you run stuff without `firejail`, do you still run into this bug?

gitea-mirror commented

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

Author

Owner

@owenh000 commented on GitHub (May 22, 2019):

I am not seeing this problem now, with or without firejail. I am using the same versions as before: firejail 0.9.58.2-1~bpo9+1 and xpra 0.17.6+dfsg-1.

Feel free to close this issue if that seems appropriate. I'll post an update here if this starts happening again. Thank you!

@owenh000 commented on GitHub (May 22, 2019): I am not seeing this problem now, with or without firejail. I am using the same versions as before: firejail 0.9.58.2-1~bpo9+1 and xpra 0.17.6+dfsg-1. Feel free to close this issue if that seems appropriate. I'll post an update here if this starts happening again. Thank you!

gitea-mirror commented

2026-05-05 07:02:12 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (May 23, 2019):

Great, I'll go ahead and close this for now, thanks for getting back! :)

@chiraag-nataraj commented on GitHub (May 23, 2019): Great, I'll go ahead and close this for now, thanks for getting back! :)

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

No description provided.

Rows
Columns