rd problem on a 2008.1 system. I run kde. suddenly I will discover that
none of my X programs (Mozilla, gnome-terminal,..) open, and when I try to
open them from the commandline one one of the terminals already open on the
desktop, the error comes back that it cannot open the display :0.0, which
is my main display. Yesterday when this happened, it suddenly cleared up
again after about 5 min.

What in the world is going on? Any clues? Any thing I can look for next
time it happens?

Unfortunately I did not save the exact error messages.

On Saturday 19 July 2008 18:15, someone identifying as *Bill Unruh* wrote
in /alt.os.linux.mandriva:/

> rd problem on a 2008.1 system. I run kde. suddenly I will discover that
> none of my X programs (Mozilla, gnome-terminal,..) open, and when I try to
> open them from the commandline one one of the terminals already open on
> the desktop, the error comes back that it cannot open the display :0.0,
> which is my main display. Yesterday when this happened, it suddenly
> cleared up again after about 5 min.
>
> What in the world is going on? Any clues? Any thing I can look for next
> time it happens?

My guess is that it's a matter of bad permissions on the display.
With /udev/ now being somewhat of a standard way of organizing device
files, it's a lot easier for programs to alter permissions on device
special files.

> Unfortunately I did not save the exact error messages.

And I'm just making a wild guess, but hopefully that could help you on your
way to solving this. Have you checked the /syslog/ yet?

--
*Aragorn*
(registered GNU/Linux user #223157)

Aragorn <aragorn@chatfactory.invalid> writes:

>On Saturday 19 July 2008 18:15, someone identifying as *Bill Unruh* wrote
>in /alt.os.linux.mandriva:/

>> rd problem on a 2008.1 system. I run kde. suddenly I will discover that
>> none of my X programs (Mozilla, gnome-terminal,..) open, and when I try to
>> open them from the commandline one one of the terminals already open on
>> the desktop, the error comes back that it cannot open the display :0.0,
>> which is my main display. Yesterday when this happened, it suddenly
>> cleared up again after about 5 min.
>>
>> What in the world is going on? Any clues? Any thing I can look for next
>> time it happens?

>My guess is that it's a matter of bad permissions on the display.
>With /udev/ now being somewhat of a standard way of organizing device
>files, it's a lot easier for programs to alter permissions on device
>special files.

What /dev/ would the display be?



>> Unfortunately I did not save the exact error messages.

>And I'm just making a wild guess, but hopefully that could help you on your
>way to solving this. Have you checked the /syslog/ yet?

>--
>*Aragorn*
>(registered GNU/Linux user #223157)

On Sunday 20 July 2008 02:05, someone identifying as *Unruh* wrote
in /alt.os.linux.mandriva:/

> Aragorn <aragorn@chatfactory.invalid> writes:
>
>>On Saturday 19 July 2008 18:15, someone identifying as *Bill Unruh* wrote
>>in /alt.os.linux.mandriva:/
>
>>> rd problem on a 2008.1 system. I run kde. suddenly I will discover that
>>> none of my X programs (Mozilla, gnome-terminal,..) open, and when I try
>>> to open them from the commandline one one of the terminals already open
>>> on the desktop, the error comes back that it cannot open the display
>>> :0.0, which is my main display. Yesterday when this happened, it
>>> suddenly cleared up again after about 5 min.
>>>
>>> What in the world is going on? Any clues? Any thing I can look for next
>>> time it happens?
>
>>My guess is that it's a matter of bad permissions on the display.
>>With /udev/ now being somewhat of a standard way of organizing device
>>files, it's a lot easier for programs to alter permissions on device
>>special files.
>
> What /dev/ would the display be?

On this one here - Mandrake 10.0 - I have a whole series of device special
files labeled /nvidiaN/ - where "N" is a number from 0 to way over 200 -
and a device special file /nvidiactl./ I remember this because I've
installed Google Earth a while ago and it wouldn't run unless I changed the
permissions on /nvidia0/ and /nvidiactl./

I don't know whether this is the actual display device, though. Might just
be registers on the nVidia adapter, and even if they are pointers to the
display, then I don't know what it would be called for adapters from other
manufacturers.

But then again, it may also be */dev/console.* Normally the ownership of
that device special file is changed to the user logging in at the console,
or at least, that used to be the case with Mandrake up until this version
here. Perhaps some process running with root privileges changed that
ownership.

But again, if you have the right time of the failure, I would check your
system logger and see what it says about what happened around then.

--
*Aragorn*
(registered GNU/Linux user #223157)

On Sat, 19 Jul 2008 20:05:41 -0400, Unruh <unruh-spam@physics.ubc.ca> wrote:

>>> rd problem on a 2008.1 system. I run kde. suddenly I will discover that
>>> none of my X programs (Mozilla, gnome-terminal,..) open, and when I try to
>>> open them from the commandline one one of the terminals already open on
>>> the desktop, the error comes back that it cannot open the display :0.0,

I don't think it's a /dev entry. I suspect there's a problem with the
ownership or permissions of the sockets in /tmp/.ICE-unix/, or /tmp.X11-unix/,
or one of the files ~/.xauth????, ~/.DCOPserver??????, ~/.ICEauthority,
~/.Xauthority.

I know I always get the error if I'm in a chroot environment, to another one
of my installs.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)