1) What script(s) is KDM running when it authenticates a user.
2) What log files should I look in for problems?
startx works find, loading KDE (3.3) without a problem.
Thanks
David
--
gento...@gentoo.org mailing list
errors go into ~/.xsession-errors
--myk
---begin---
Xlib: connection to ":0.0" refused by server
Xlib: Protocol not supported by server
xset: unable to open display ":0"
Xlib: connection to ":0.0" refused by server
Xlib: Protocol not supported by server
xset: unable to open display ":0"
Xlib: connection to ":0.0" refused by server
Xlib: Protocol not supported by server
xset: unable to open display ":0"
Xlib: connection to ":0.0" refused by server
Xlib: Protocol not supported by server
xsetroot: unable to open display ':0'
startkde: Starting up...
Xlib: connection to ":0.0" refused by server
Xlib: Protocol not supported by server
[ There's more, but it all comes down to the display not being accessible.]
---end---
Any suggestions?
David
On Saturday 09 April 2005 07:04 pm, Myk Taylor wrote:
> All the scripts that kdm runs are in /usr/kde/3.3/share/config/kdm.
> Perhaps you need to look at Xsession, since that's what is run after kdm
> authenticates your password.
>
> errors go into ~/.xsession-errors
>
> --myk
>
> David Corbin wrote:
> > Some time back after an emerge, I found out that logging into KDM would
> > always fail. That is authentication appears to pass, the screen turns
> > black, and then it brings me back to the KDM login screen.
--
gento...@gentoo.org mailing list
http://forums.suselinuxsupport.de/lofiversion/index.php/t3241.html
Short answer: get rid of the pertinent ~/.{x,X}* files
Google is your friend.
--myk
David Corbin wrote:
> Thanks. Here's what my .xsession-errors has.
>
> ---begin---
> Xlib: connection to ":0.0" refused by server
> Xlib: Protocol not supported by server
...
--
gento...@gentoo.org mailing list
A phrase I often use myself. I guess I got in the an "email dependency rut".
That did it, btw. Thanks. I think it was the .Xauthority file.