[NCLUG] gdm funkiness

[Darren Smith]

I haven't seen your specific problem and don't know if this applies, but I 
did have to let startx regenerate a .Xauthority file once that wasn't getting 
created properly with kdm.

You can get out of the X login screen by switching to runlevel 3 (or maybe 
gdm has a button for this?). Then have MYUSER login, remove the corrupt file 
and run startx.

-Darren

On Thursday 13 December 2001 05:27 pm, you wrote:
>  Ok, pain in the tuckus time. RedHat(KRUD) 7.1 machines, 2 seperate
> machines setup identically and user is unable to login on the gdm-powered
> X console login screen on either. Dumps him back out to the gdm screen.
> User's home dir is automounted via NFS/autofs. Was working great, user
> logged out to reset something and couldn't log back in.
>
> /var/log/messages has the following:
>
> ------------------------------------------
> Dec 13 16:04:08 zuma gdm(pam_unix)[2425]: session opened for user MYUSER by
> (uid=0) Dec 13 16:04:09 zuma gdm[2425]: gdm_slave_session_start: MYUSER on
> :0 Dec 13 16:04:09 zuma gdm(pam_unix)[2425]: session closed for user MYUSER
> Dec 13 16:04:09 zuma gdm[2425]: gdm_auth_user_remove: /lsi/home/MYUSER is
> not owned by uid 0. Dec 13 16:04:09 zuma gdm[2425]: gdm_auth_user_remove:
> Ignoring suspiciously looking cookie file /lsi/home/MYUSER/.Xauthority
> ------------------------------------------
>
>  Bad grammar aside, any clue? A search on google resulted in the question
> asked many times but never answered. We've removed the .Xauthority file
> only to have the beaviour repeated and the file recreated.