Re: sux: "cannot open display: :0".
Good time of the day, Camaleón. Thank You for Your time and answer! You wrote: > I suggested because you seemed to have many X related packages > udpated and it could be that Xorg needed to be power-cycled. And that's why I did it. :o) > > But I have already solved the problem for me - removing all seemed > > Gconf-related config. garbage accumulated over time in the sux-ed > > user home dir. - now it works w/o problem - as before - probably, > > simply inconsistency w/ updated software config.s. > > Mmm... I tend to do an "apt-get -f install" (and also "purge") from > time to time in my wheezy system and I remember Gconf was removed > since time ago. Anyway, I can't see a direct relation between having > the package installed (along with older configuration files) and the > above errors :-? And that I do also - I'm HDD space hungry always and also do not like vain waste! > > But I wanted to help to hunt a possible bug here - therefore would > > to make a report. But do not worry, if no idea which package. > > I can't really tell. If it really was due to old/residual > configuration files is even harder to find the real culprit :-) > > In such cases, what it helps for debugging the problem is "sux -ing" > to a different user and test from there to discard something in the > home profile. And that what gave the idea - that Gconf could be the problem - I tried, occasionally to run an app. from another "clean" user. When I first read Your "sux -ing" I understood it as $ sux -ing :o) OK. Doesn't matter. Let's finish here. Thanks for Your help always OR willingness to help! Sthu. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/503e4ed6.4608cc0a.3482.4...@mx.google.com
Re: sux: "cannot open display: :0".
On Wed, 29 Aug 2012 01:37:17 +0700, Sthu Deus wrote: >> This can sound a bit odd but have you tried with a system restart? > > It happened right after restart! :o) Ouch! I suggested because you seemed to have many X related packages udpated and it could be that Xorg needed to be power-cycled. > But I have already solved the problem for me - removing all seemed > Gconf-related config. garbage accumulated over time in the sux-ed user > home dir. - now it works w/o problem - as before - probably, simply > inconsistency w/ updated software config.s. Mmm... I tend to do an "apt-get -f install" (and also "purge") from time to time in my wheezy system and I remember Gconf was removed since time ago. Anyway, I can't see a direct relation between having the package installed (along with older configuration files) and the above errors :-? > But I wanted to help to hunt a possible bug here - therefore would to > make a report. But do not worry, if no idea which package. I can't really tell. If it really was due to old/residual configuration files is even harder to find the real culprit :-) In such cases, what it helps for debugging the problem is "sux -ing" to a different user and test from there to discard something in the home profile. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k1l6j9$koe$4...@ger.gmane.org
Re: sux: "cannot open display: :0".
Good time of the day, Camaleón. Thank You for Your time and answer, again. You wrote: > This can sound a bit odd but have you tried with a system restart? It happened right after restart! :o) But I have already solved the problem for me - removing all seemed Gconf-related config. garbage accumulated over time in the sux-ed user home dir. - now it works w/o problem - as before - probably, simply inconsistency w/ updated software config.s. But I wanted to help to hunt a possible bug here - therefore would to make a report. But do not worry, if no idea which package. Sthu. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/503d0fe5.a290980a.5b44.5...@mx.google.com
Re: sux: "cannot open display: :0".
On Tue, 28 Aug 2012 18:46:30 +0700, Sthu Deus wrote: > On wheezy, after upgrade of: > > kmod:amd64 8-2 -> 9-1 > libgl1-mesa-dri:amd64 8.0.4-1 -> 8.0.4-2 > libgl1-mesa-dri:i386 8.0.4-1 -> 8.0.4-2 > libgl1-mesa-glx:amd64 8.0.4-1 -> 8.0.4-2 > libgl1-mesa-glx:i386 8.0.4-1 -> 8.0.4-2 > libglapi-mesa:amd64 8.0.4-1 -> 8.0.4-2 > libglapi-mesa:i386 8.0.4-1 -> 8.0.4-2 > libglu1-mesa:amd64 8.0.4-1 -> 8.0.4-2 > libglu1-mesa:i386 8.0.4-1 -> 8.0.4-2 > libkmod2:amd64 8-2 -> 9-1 > libspectre1:amd64 0.2.6-2 -> 0.2.7-2 > module-init-tools:amd64 8-2 -> 9-1 > > I can not run several X app.s from sux-ed user: > > $ chromium > No protocol specified > (chromium:N): Gtk-WARNING **: cannot open display: :0 (...) This can sound a bit odd but have you tried with a system restart? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k1iscd$ik9$1...@ger.gmane.org
sux: "cannot open display: :0".
Good time of the day. On wheezy, after upgrade of: kmod:amd64 8-2 -> 9-1 libgl1-mesa-dri:amd64 8.0.4-1 -> 8.0.4-2 libgl1-mesa-dri:i386 8.0.4-1 -> 8.0.4-2 libgl1-mesa-glx:amd64 8.0.4-1 -> 8.0.4-2 libgl1-mesa-glx:i386 8.0.4-1 -> 8.0.4-2 libglapi-mesa:amd64 8.0.4-1 -> 8.0.4-2 libglapi-mesa:i386 8.0.4-1 -> 8.0.4-2 libglu1-mesa:amd64 8.0.4-1 -> 8.0.4-2 libglu1-mesa:i386 8.0.4-1 -> 8.0.4-2 libkmod2:amd64 8-2 -> 9-1 libspectre1:amd64 0.2.6-2 -> 0.2.7-2 module-init-tools:amd64 8-2 -> 9-1 I can not run several X app.s from sux-ed user: $ chromium No protocol specified (chromium:N): Gtk-WARNING **: cannot open display: :0 $ liferea (liferea:N): GConf-WARNING **: Client failed to connect to the D-BUS daemon: /usr/bin/dbus-launch terminated abnormally with the following error: No protocol specified Autolaunch error: X11 initialization failed. GConf Error: No D-BUS daemon running I'm running LXDE for Your notice. Against which package I should make bug report? Thanks for Your time. Sthu. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/503caf9b.631d700a.381d.4...@mx.google.com
