mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1486] xpra window isn't displaying / xpra-extra-params broken in firejail-git #995
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#995
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cryzed on GitHub (Aug 20, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1486
Recently the
x11 xpraoption 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-1andfirejail 0.9.48-1in KDE. Disabling the compositor does not make a difference. My user is part of thexpragroup.@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@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.
@cryzed commented on GitHub (Aug 20, 2017):
@SpotComms before I open a new issue: is it known that enabling the
xpra-extra-paramsoption 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.@SkewedZeppelin commented on GitHub (Aug 20, 2017):
@chiraag-nataraj have you encountered that?
@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).
@ghost commented on GitHub (Aug 25, 2017):
@cryzed
xpra-extra-paramsis broken when used withxpra-attach yessimultaneously. Both options work when used alone. This is bug in firejail I think.To workaround this you can set
xpra-attach yesinfiejail.configkeepxpra-extra-paramsdisabled there and set dpi through xpra own config in/etc/xpra/conf.d/30_picture.conf@ghost commented on GitHub (Aug 26, 2017):
Also with
xpra-attach yesinfirejail.configsome apps lose window theming on my machine. Settingattach=yesinxpra.confworks good. It seems that it's generally better to tweak xpra on it's own and leave firejail specific config intact.@xelxebar commented on GitHub (Oct 25, 2017):
@ghost
Are you sure setting
attach=yesinxpra.confdoes what you want? On my machine it causes the xpra session to remain open after cloing the program window. I have to do a manualxpra stopto kill it. This isn't a problem however withxpra-attach yesinfirejail.config.@chiraag-nataraj commented on GitHub (Jul 22, 2018):
Fixed in
2d3c4e43a1