[GH-ISSUE #1486] xpra window isn't displaying / xpra-extra-params broken in firejail-git #995

Closed
opened 2026-05-05 07:16:40 -06:00 by gitea-mirror · 9 comments
Owner

Originally created by @cryzed on GitHub (Aug 20, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1486

Recently the x11 xpra option seemingly has stopped working. The application still seems to be starting correctly, however an actual window is never displayed. With Discord for example, it displays the icon in the tray, however the window can not be brought up by clicking on it.

I'm running Arch Linux with xpra-winswitch 2.1.1-1 and firejail 0.9.48-1 in KDE. Disabling the compositor does not make a difference. My user is part of the xpra group.

Originally created by @cryzed on GitHub (Aug 20, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1486 Recently the `x11 xpra` option seemingly has stopped working. The application still seems to be starting correctly, however an actual window is never displayed. With Discord for example, it displays the icon in the tray, however the window can not be brought up by clicking on it. I'm running Arch Linux with `xpra-winswitch 2.1.1-1` and `firejail 0.9.48-1` in KDE. Disabling the compositor does not make a difference. My user is part of the `xpra` group.
Author
Owner

@SkewedZeppelin commented on GitHub (Aug 20, 2017):

Is this different from #1405 fixed by #1415?
Try installing firejail-git from the AUR and then sudo sed -i 's/# xpra-attach no/xpra-attach yes/' /etc/firejail/firejail.config

<!-- gh-comment-id:323612690 --> @SkewedZeppelin commented on GitHub (Aug 20, 2017): Is this different from #1405 fixed by #1415? Try installing firejail-git from the AUR and then `sudo sed -i 's/# xpra-attach no/xpra-attach yes/' /etc/firejail/firejail.config`
Author
Owner

@cryzed commented on GitHub (Aug 20, 2017):

That works, thank you. I was searching for open issues regarding this problem, that's why I couldn't find it.

<!-- gh-comment-id:323614096 --> @cryzed commented on GitHub (Aug 20, 2017): That works, thank you. I was searching for open issues regarding this problem, that's why I couldn't find it.
Author
Owner

@cryzed commented on GitHub (Aug 20, 2017):

@SpotComms before I open a new issue: is it known that enabling the xpra-extra-params option is broken? When simply uncommenting the default (--dpi 96) I get the following error:

firejail: x11.c:996: x11_start_xpra_new: Assertion `server_argv[spos-1] == NULL' failed.

<!-- gh-comment-id:323614357 --> @cryzed commented on GitHub (Aug 20, 2017): @SpotComms before I open a new issue: is it known that enabling the `xpra-extra-params` option is broken? When simply uncommenting the default (`--dpi 96`) I get the following error: ```firejail: x11.c:996: x11_start_xpra_new: Assertion `server_argv[spos-1] == NULL' failed.```
Author
Owner

@SkewedZeppelin commented on GitHub (Aug 20, 2017):

firejail: x11.c:996: x11_start_xpra_new: Assertion server_argv[spos-1] == NULL' failed.`

@chiraag-nataraj have you encountered that?

<!-- gh-comment-id:323614977 --> @SkewedZeppelin commented on GitHub (Aug 20, 2017): > `firejail: x11.c:996: x11_start_xpra_new: Assertion `server_argv[spos-1] == NULL' failed.` @chiraag-nataraj have you encountered that?
Author
Owner

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

@SpotComms Yes I have (see #1404 - I never got any replies and decided to focus on fixing the issue of xpra not attaching instead).

<!-- gh-comment-id:324068888 --> @chiraag-nataraj commented on GitHub (Aug 22, 2017): @SpotComms Yes I have (see #1404 - I never got any replies and decided to focus on fixing the issue of xpra not attaching instead).
Author
Owner

@ghost commented on GitHub (Aug 25, 2017):

@cryzed xpra-extra-params is broken when used with xpra-attach yes simultaneously. Both options work when used alone. This is bug in firejail I think.

To workaround this you can set xpra-attach yes in fiejail.config keep xpra-extra-params disabled there and set dpi through xpra own config in /etc/xpra/conf.d/30_picture.conf

<!-- gh-comment-id:324911060 --> @ghost commented on GitHub (Aug 25, 2017): @cryzed `xpra-extra-params` is broken when used with `xpra-attach yes` simultaneously. Both options work when used alone. This is bug in firejail I think. To workaround this you can set `xpra-attach yes` in `fiejail.config` keep `xpra-extra-params` disabled there and set dpi through xpra own config in `/etc/xpra/conf.d/30_picture.conf`
Author
Owner

@ghost commented on GitHub (Aug 26, 2017):

Also with xpra-attach yes in firejail.config some apps lose window theming on my machine. Setting attach=yes in xpra.conf works good. It seems that it's generally better to tweak xpra on it's own and leave firejail specific config intact.

<!-- gh-comment-id:325111172 --> @ghost commented on GitHub (Aug 26, 2017): Also with `xpra-attach yes` in `firejail.config` some apps lose window theming on my machine. Setting `attach=yes` in `xpra.conf` works good. It seems that it's generally better to tweak xpra on it's own and leave firejail specific config intact.
Author
Owner

@xelxebar commented on GitHub (Oct 25, 2017):

@ghost
Are you sure setting attach=yes in xpra.conf does what you want? On my machine it causes the xpra session to remain open after cloing the program window. I have to do a manual xpra stop to kill it. This isn't a problem however with xpra-attach yes in firejail.config.

<!-- gh-comment-id:339478422 --> @xelxebar commented on GitHub (Oct 25, 2017): @ghost Are you sure setting `attach=yes` in `xpra.conf` does what you want? On my machine it causes the xpra session to remain open after cloing the program window. I have to do a manual `xpra stop` to kill it. This isn't a problem however with `xpra-attach yes` in `firejail.config`.
Author
Owner

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

Fixed in 2d3c4e43a1

<!-- gh-comment-id:406837862 --> @chiraag-nataraj commented on GitHub (Jul 22, 2018): Fixed in 2d3c4e43a14a6ee06f90758a88dfbd57ca394046
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#995
No description provided.