Bug#560968: gdm: seems to have incorrect startup dependencies and stops too early
joss at debian.org
Mon Dec 14 13:32:30 UTC 2009
Le lundi 14 décembre 2009 à 13:30 +0100, Bas Wijnen a écrit :
> > I’d appreciate if you could have a look at your logs (auth.log
> > and syslog) and see if anything goes wrong at login time.
> Dec 14 09:34:00 vlam gdm: pam_unix(gdm:auth): authentication
> failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=shevek
> So appearantly there is an "authentication failure", but I don't know
> what it is. Is there a way to get more information in the logs? I'd
> happily send that to you as well.
Just to be sure: are you using a dependency-based init? If so, please
list the services that are started later than GDM. Are you using
something else than plain Unix passwd files (said otherwise, does
nsswitch.conf reference anything else)?
I’d also appreciate if you could test by disabling pam_ck_connector. It
should do nothing, but I guess it could fail if ConsoleKit’s autospawn
doesn’t work correctly.
You can also try with removing pam_gnome_keyring, but I don’t think it’s
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Ceci est une partie de message num?riquement sign?e
More information about the pkg-gnome-maintainers