retitle 252326 xdm: user cannot log in
tag 252326 + moreinfo unreproducible
thanks
On Wed, Jun 02, 2004 at 08:56:17PM +0200, Andreas Messer wrote:
> Package: xdm
> Version: 4.3.0.dfsg.1-1
>
> Hello,
> i am not able to login local using xdm. With kdm everything works fine. I
> think there ist some problem verifying the passwort, because
> my /var/log/auth.log says:
>
> Jun 2 19:19:03 hermes : (pam_unix) authentication failure; logname=
> uid=0 euid=0 tty=:0 ruser= rhost= user=satura
The above is probably a red herring. xdm fine works for me, and I
always get lines like this in auth.log myself.
> I have also completely purged and reinstalled the xdm Package but this
> did'nt solve the problem.
I wonder if the session is just exiting normally because it has nothing
to do. See the Debian X FAQ:
/usr/share/doc/xfree86-commom/FAQ.gz
http://necrotic.deadbeast.net/xsf/XFree86/trunk/debian/local/FAQ
*) How can I tell if it's the X server crashing, or my X session exiting
abnormally?
Generally, when the X server has no more clients to manage, it will exit
immediately. This can look a lot like a "crash" to the uninitiated, especially
when the clients themselves crash.
It's easy to determine whether the X server itself works. As root, simply run
the command "X". If that brings up the little root window weave and the X
cursor, then *you do not have a fatal X server configuration problem*. The X
server is working. Use CTRL-ALT-BACKSPACE to kill it.
Alternatively, if you're using a display manager and you can see the greeter
(login screen), then the X server is running: *you do not have a fatal X server
configuration problem*. Most failures after that point are client-side
problems. (Yes, there are bugs in the X server that can cause it spontaneously
crash, but if the X server "crashes" immediately upon logging in to your X
session, it's probably a client side problem.)
If the X server doesn't start with the command "X", but you get a message like
"Server already active for display 0", then you're probably already running X
somewhere. See the "The X server log says there was an error opening my 'core
pointer'..." question above for more information on how to deal with this.
Alternatively, if you're using a display manager and you can see the
greeter (login screen), then the X server is running: *you do not have a
fatal X server configuration problem*. Most failures after that point
are client-side problems. (Yes, there are bugs in the X server that can
cause it spontaneously crash, but if the X server "crashes" immediately
upon logging in to your X session, it's probably a client side problem.)
--
G. Branden Robinson | That's the saving grace of humor:
Debian GNU/Linux | if you fail, no one is laughing at
branden@debian.org | you.
http://people.debian.org/~branden/ | -- A. Whitney Brown
Attachment:
signature.asc
Description: Digital signature