GDM auto-logging "logs-out" & forces to relogin...

[Dimitri John Ledkov]

Binary package hint: gdm

I'm using maverick uptodate.

I have automatic login enabled.

The computer boots up and shortly after plymouth I get to my desktop. My startup applications start to load up (e.g. chromium web-browser, indicators etc.).

I'm then presented with the "The keyring was not unlocked at login...." dialog as usual. After typing my password and clicking unlock the whole desktop disappears and I'm presented with GDM login screen, althougth I should see it at all.

Alright I login, no "unlock keyring message appears". Use desktop normally. Upon logout I get "One application is still running..." which lists PolicyKit authentication daemon. Hmmm? Possibly the unlock keyring dialog which got stuck in the previous "auto-login-ghost-session"?

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gdm 2.30.5-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Mon Aug 30 12:06:12 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: gdm

[Sebastien Bacher (seb128)]

Thank you for your bug report, could you switch to vt1 and see if there is your password on any input there?

[Sebastien Bacher (seb128)]

seems similar to bug #626723, could you get the gdm debug log as well?

[Sebastien Bacher (seb128)]

could you check you have a /var/run/gdm/firstserver.stamp as well?

[Dimitri John Ledkov (xnox)]

Thank you for your comments. I'll try to do all of this now.

[Dimitri John Ledkov (xnox)]

I do have /var/run/gdm/firstserver.stamp.

on the vt1 there are definatly some strange input. After some boot messages there are 3 weird looking sequences:

6^Y^T^X^X^X%^R^H intemixed with multiple ***** and "asci dimond symbols"

It's not clear text password, but it might as well be since I've never ever seen that before.

I'm inclined to believe this bug is similar to bug #626723, because the delay between desktop appearing and the jump to "gdm" again is similar with and without autologin.

[Sebastien Bacher (seb128)]

the log indicates it's a duplicate