Re: sux: cannot open display: :0.

2012-08-29 Thread Camaleón
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.

Re: sux: cannot open display: :0.

2012-08-29 Thread Sthu Deus
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

sux: cannot open display: :0.

2012-08-28 Thread Sthu Deus
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

Re: sux: cannot open display: :0.

2012-08-28 Thread Camaleón
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

Re: sux: cannot open display: :0.

2012-08-28 Thread Sthu Deus
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