github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #1065] --x11=xorg "unable to open display" but runs anyway #721

New issue
Closed
opened 2026-05-05 06:31:27 -06:00 by gitea-mirror · 6 comments
gitea-mirror commented 2026-05-05 06:31:27 -06:00
Owner
Copy link

Originally created by @xahare on GitHub (Jan 23, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1065

xlogo does run. this also happens with firefox.
host is ubuntu 16.04 amd_64 running in virtualbox with guest extensions

$ firejail --x11=xorg xlogo
Reading profile /etc/firejail/default.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/disable-passwdmgr.inc

** Note: you can use --noprofile to disable default.profile **

Parent pid 4897, child pid 4898
/usr/bin/xauth: (argv):1:  unable to open display ":0".
Child process initialized

Parent is shutting down, bye...
Originally created by @xahare on GitHub (Jan 23, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1065 xlogo does run. this also happens with firefox. host is ubuntu 16.04 amd_64 running in virtualbox with guest extensions ``` $ firejail --x11=xorg xlogo Reading profile /etc/firejail/default.profile Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-programs.inc Reading profile /etc/firejail/disable-passwdmgr.inc ** Note: you can use --noprofile to disable default.profile ** Parent pid 4897, child pid 4898 /usr/bin/xauth: (argv):1: unable to open display ":0". Child process initialized Parent is shutting down, bye... ```
gitea-mirror 2026-05-05 06:31:27 -06:00
gitea-mirror commented 2026-05-05 06:31:32 -06:00
Author
Owner
Copy link

@chiraag-nataraj commented on GitHub (Jan 23, 2017):

Huh. I get a "No protocol specified" and "Error: Can't open display: :0" and xlogo doesn't launch. I'm running on Debian sid/experimental x86_64.

<!-- gh-comment-id:274651366 --> @chiraag-nataraj commented on GitHub (Jan 23, 2017): Huh. I get a "No protocol specified" and "Error: Can't open display: :0" and `xlogo` doesn't launch. I'm running on Debian sid/experimental x86_64.
gitea-mirror commented 2026-05-05 06:31:36 -06:00
Author
Owner
Copy link

@netblue30 commented on GitHub (Jan 24, 2017):

Working fine for me on Debian stable:

$ firejail --x11=xorg xlogo
Reading profile /etc/firejail/default.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/disable-passwdmgr.inc

** Note: you can use --noprofile to disable default.profile **

Parent pid 3363, child pid 3364
Child process initialized
<!-- gh-comment-id:274798675 --> @netblue30 commented on GitHub (Jan 24, 2017): Working fine for me on Debian stable: ````` $ firejail --x11=xorg xlogo Reading profile /etc/firejail/default.profile Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-programs.inc Reading profile /etc/firejail/disable-passwdmgr.inc ** Note: you can use --noprofile to disable default.profile ** Parent pid 3363, child pid 3364 Child process initialized `````
gitea-mirror commented 2026-05-05 06:31:39 -06:00
Author
Owner
Copy link

@netblue30 commented on GitHub (Jan 24, 2017):

When I run --x11=xorg firefox I get a warning: Xlib: extension "RANDR" missing on display ":0.0". Other than that, firefox (version 45.6.0) seems to be working fine. It is possible newer firefox versions behave differently, or don't work at all.

<!-- gh-comment-id:274799578 --> @netblue30 commented on GitHub (Jan 24, 2017): When I run --x11=xorg firefox I get a warning: Xlib: extension "RANDR" missing on display ":0.0". Other than that, firefox (version 45.6.0) seems to be working fine. It is possible newer firefox versions behave differently, or don't work at all.
gitea-mirror commented 2026-05-05 06:31:41 -06:00
Author
Owner
Copy link

@valoq commented on GitHub (Jan 24, 2017):

Is there another window server running?
If X11 access is blocked but e.g. access to a wayland server is available, which is the case on modern gnome desktops, the application will still run, but display this warning.

<!-- gh-comment-id:274831151 --> @valoq commented on GitHub (Jan 24, 2017): Is there another window server running? If X11 access is blocked but e.g. access to a wayland server is available, which is the case on modern gnome desktops, the application will still run, but display this warning.
gitea-mirror commented 2026-05-05 06:31:44 -06:00
Author
Owner
Copy link

@xahare commented on GitHub (Jan 25, 2017):

seems a difference between newer and older xorg then. there must be a way to automate testing across a few distros. this approach looks promising, https://github.com/Oefenweb/ansible-fail2ban/blob/master/Vagrantfile

@valoq when using xwayland, couldn't query security extension on display ":0"

<!-- gh-comment-id:274991602 --> @xahare commented on GitHub (Jan 25, 2017): seems a difference between newer and older xorg then. there must be a way to automate testing across a few distros. this approach looks promising, https://github.com/Oefenweb/ansible-fail2ban/blob/master/Vagrantfile @valoq when using xwayland, couldn't query security extension on display ":0"
gitea-mirror commented 2026-05-05 06:31:48 -06:00
Author
Owner
Copy link

@xahare commented on GitHub (Jan 26, 2017):

[edit] not firejail related. gimp and printsrc just show blank backgrounds with or without firejail. maybe its virtualbox.

just confirmed this in ubuntu desktop. only the terminal windows showed in xwd. not the background, any of the desktop/window manager widgets, or file manager that was open. tried again in xterm, and again, only the gnome-terminal windows showed against a black background.

any idea where to go from here? where could the bug be?

user@work-terminal:~$ cat rootdump.sh 
xwd -root > root.xwd
user@work-terminal:~$ firejail --x11=xorg ./rootdump.sh 
Reading profile /etc/firejail/default.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/disable-passwdmgr.inc

** Note: you can use --noprofile to disable default.profile **

Parent pid 19026, child pid 19027
/usr/bin/xauth: (argv):1:  unable to open display ":0".
Child process initialized

Parent is shutting down, bye...
user@work-terminal:~$ gimp root.xwd
<!-- gh-comment-id:275410593 --> @xahare commented on GitHub (Jan 26, 2017): [edit] not firejail related. gimp and printsrc just show blank backgrounds with or without firejail. maybe its virtualbox. just confirmed this in ubuntu desktop. only the terminal windows showed in xwd. not the background, any of the desktop/window manager widgets, or file manager that was open. tried again in xterm, and again, only the gnome-terminal windows showed against a black background. any idea where to go from here? where could the bug be? ``` user@work-terminal:~$ cat rootdump.sh xwd -root > root.xwd user@work-terminal:~$ firejail --x11=xorg ./rootdump.sh Reading profile /etc/firejail/default.profile Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-programs.inc Reading profile /etc/firejail/disable-passwdmgr.inc ** Note: you can use --noprofile to disable default.profile ** Parent pid 19026, child pid 19027 /usr/bin/xauth: (argv):1: unable to open display ":0". Child process initialized Parent is shutting down, bye... user@work-terminal:~$ gimp root.xwd ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#721
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?