Re: gdm: first login fails, second one suceeds: why?

["John P. Verel" <jverel optonline net>]

As suggested, here's what ~./xsession-errors looks like.

Here is immediately after the failed login:

XIM DEBUG: _IceTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_IceTransMakeAllCOTSServerListeners: server already running

** WARNING **: Cannot establish any listening sockets

(After the failed login, I toggled to console 1, logged in as root and
copied ~/.xsession-errors to another name.)

Here's what ~.xsession-errors looked like after the second (successful)
login:

XIM DEBUG: SESSION_MANAGER=local/Verdi:/tmp/.ICE-unix/1311
Message: Successfully registered `OAFIID:nautilus_factory:bd1e1862-92d7-4391-963e-37583f0daef3'

Gtk-WARNING **: gtk_signal_disconnect_by_data(): could not find handler containing data (0x8189520)
xalf: timeout launching /bin/sh

This means....?

Thanks.

John

>On 12/12/01, 01:18:01PM -0500, Havoc Pennington wrote:
> 
> "John P. Verel" <jverel optonline net> writes:
> > This is a repost, forgive me.
> > 
> > It sometimes happens that upon first login to gdm,  
> > gdm-2.2.3.1-20, that with user and password correct, I screen blanks,
> > gdm comes back.  Second login works.
> > 
> > Tonight I found and cleaned out a mess of files in ~/.gnome like this:
> > 
> > -rw-------    1 john     john            2 Dec 11 21:59 /home/john/.gnome/.gnome-smproxy-t4yKsZ
> > 
> > They were up to a month old.
> > 
> > After deleting them, the problem seemed to go away.
> > 
> > Am I on the right track on this?
> 
> Maybe, I don't see an obvious reason those files matter though.
> 
> Have you tried looking in ~/.xsession-errors after the failed login?
> (before logging in again?)
> 
> Havoc

-- 
John P. Verel
Living Proof That Low Tech Beats High Tech!