Skip to content

Error: cannot open display: :0.0 caused #268

Open
cattaka opened this Issue Jan 26, 2013 · 8 comments

4 participants

@cattaka
cattaka commented Jan 26, 2013

I'm using Debian squeeze.
When I pressed lunch button on Simulator Dashboar,
The window of emulator is not displayed.

I checked terminal and got logs.
info: r2d2b2g: Simulator.onMessage toggle
info: r2d2b2g: rsc.remoteDebuggerPort: found free port 60481
No protocol specified
No protocol specified
Error: cannot open display: :0.0
info: r2d2b2g: linux/b2g/b2g terminated with 256

It seems that, when display's access control was enabled,
The window of emulator can not displayed.

I solved this issue using "$ xhost +".
But I wish to notice about that error to user.

@mykmelez
Mozilla member

I'm not familiar with display access control in Debian/Linux, so I don't know if this is a bug in Simulator or an issue with OS configuration.

@rpl: do you have any insight?

@doomsplayer

exactly the same issue

@nfroidure

idem, has the same issue. The stderr :
(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64

(firefox:10269): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: mauvaise classe ELF : ELFCLASS64
/usr/lib/gio/modules/libgvfsdbus.so: mauvaise classe ELF : ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
debug: r2d2b2g: XULAPP: Firefox 19.0 19.0
debug: r2d2b2g: HAS_CONNECT_DEVTOOLS: false
warning: rotate-image: Plural form unknown for locale "null"
info: rotate-image: startup
info: r2d2b2g: Simulator.onMessage getIsRunning
info: r2d2b2g: Simulator.onMessage listApps
info: r2d2b2g: Simulator.sendListApps
info: r2d2b2g: Simulator.onMessage listTabs
info: r2d2b2g: Simulator.onMessage getPreference
info: r2d2b2g: Simulator.onMessage toggle
info: r2d2b2g: rsc.remoteDebuggerPort: found free port 60777
No protocol specified
No protocol specified
Error: cannot open display: :0.0
info: r2d2b2g: linux/b2g/b2g terminated with 256

@mykmelez
Mozilla member

@doomsplayer @nfroidure Are you also using Debian, and if so, which version are you using? I'm just trying to figure out if this is a Debian-specific issue or if it affects multiple Linux distributions.

@doomsplayer
@nfroidure

i use debian (squeeze) indeed :
Linux 3.2.0-0.bpo.1-amd64 #1 SMP Sat Feb 11 08:41:32 UTC 2012 x86_64 GNU/Linux

@nfroidure

xhost + also solved the problem for me

@mykmelez
Mozilla member
mykmelez commented Apr 2, 2013

Ok, so then the question is why a b2g process spawned by the Firefox process doesn't have access to the xserver, even though the Firefox process itself has access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.