[techtalk] gdm returning error mesgs

Kristin Ziel zoop at sound.scc.net
Mon Apr 2 13:12:00 EST 2001


Hi all--

I rebooted my machine the other day, and now gdm returns error messages
and won't start.  

Here's what I've tracked down so far.

-The X server starts

-I get error messages <follows> stating that the client is not authorized
to connect to the Xserver
<snip>
AUDIT: Mon Apr  2 01:08:55 2001: 4531 X: client 1 rejected from local host
Xlib: connection to ":0.0" refused by server^M
Xlib: Client is not authorized to connect to Server^M
</snip>

-The problem seems to be within xauth; when I run 'xauth generate :0' I
get similar error messages.
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
xauth: (argv):1:  unable to open display ":0".

-Strace from 'xauth generate :0' gives me the following.  I have only
included what I feel is the pertinent section....
<snip>
link("/root/.Xauthority-c", "/root/.Xauthority-l") = 0
access("/root/.Xauthority", F_OK)       = 0
access("/root/.Xauthority", W_OK)       = 0
umask(077)                              = 022
open("/root/.Xauthority", O_RDONLY)     = 4
read(4, "", 2)                          = 0
close(4)                                = 0
uname({sys="Linux", node="sass.scc.net", ...}) = 0
socket(PF_UNIX, SOCK_STREAM, 0)         = 4
uname({sys="Linux", node="sassi.scc.net", ...}) = 0
uname({sys="Linux", node="sassi.scc.net", ...}) = 0
connect(4, {sun_family=AF_UNIX, sun_path="/tmp/.X11-unix/X0"}, 19) = 0
uname({sys="Linux", node="sassi.scc.net", ...}) = 0
fcntl(4, F_SETFD, FD_CLOEXEC)           = 0
access("/root/.Xauthority", R_OK)       = 0
brk(0x8051000)                          = 0x8051000
open("/root/.Xauthority", O_RDONLY)     = 5
read(5, "", 2)                          = 0
close(5)                                = 0
writev(4, [{"l\0\v\0\0\0\0\0\0\0\0\0", 12}], 1) = 12
fcntl(4, F_SETFL, O_RDONLY|O_NONBLOCK)  = 0
read(4, "\0-\v\0\0\0\f\0", 8)           = 8
read(4, "Client is not authorized to conn"..., 48) = 48
write(2, "Xlib: connection to \":0.0\" ref"..., 52) = 52
write(2, "Client is not authorized to conn"..., 45) = 45
write(2, "\r\n", 2)                     = 2
shutdown(4, 2 /* send and receive */)   = 0
close(4)                                = 0
write(2, "xauth: (argv):1:  ", 18)      = 18
write(2, "unable to open display \":0\".\n"..., 29) = 29
unlink("/root/.Xauthority-c")           = 0
unlink("/root/.Xauthority-l")           = 0
umask(022)                              = 077
_exit(1)                                = ?
</snip>

-I reinstalled gdm to make sure that one of those package files didn't get
corrupted, and also did a verify check on the package <before and after>.

I am at a bit of a loss making sure that I understand everything in the
strace output.  There were no -1 values returned, and preliminary digging
as to where to start hasn't really given me any good leads.  

One thing that I am curious about is my :0.log output that states unable
to connect to "local host"...wondering if it should be "localhost" and
there is a problem with that?

I am not positive, but I think that the only packages that I have
installed since the last reboot were glibc 2.1.3 and java 1.3.  My
searching on the web led to a lot of references to regernate the xauth
file, and checking the gdm.conf...at that point, I'd already tried the
xauth route, and I haven't touched the gdm.conf file..but checked it
anyway, and everything seems to look OK.

One of the references I found on the web was a question as to a problem
with glibc 2.1.3 and gdm? <this is partly why I reinstalled gdm> Has
anyone else run across this? I haven't played with file permissions at
all, but I am wondering if this might be a problem as well....I have
deleted my previous magic cookie files and the xauth:0 file </var/gdm> to
make sure that they were regenerated, and that didn't fix the issue
either.

oh, before i forget... I'm running redhat 6.0 ..

i can't think of any other facts to include..if i've missed something,
please let me know....

kristin





More information about the Techtalk mailing list