Comment 13 for bug 431147

Revision history for this message
Neal Landry (neal-landry) wrote :

This bug is affecting me as well on Karmic....

[503]$> gdmsetup
** (gdmsetup:3564): DEBUG: init delay=30
** (gdmsetup:3564): DEBUG: GdmUserManager: skipping shell /bin/false
** (gdmsetup:3564): DEBUG: GdmUserManager: Found current seat: /org/freedesktop/ConsoleKit/Seat1
** (gdmsetup:3564): DEBUG: GdmUserManager: running 'ck-history --frequent --seat='Seat1' --session-type='''
** (gdmsetup:3564): DEBUG: GdmUserManager: explicitly skipping user: nobody
** (gdmsetup:3564): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3564): DEBUG: adding monitor for '/home/nealio/.face'
** (gdmsetup:3564): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3564): DEBUG: adding monitor for '/home/sarah/.face'
** (gdmsetup:3564): DEBUG: Getting list of sessions for user 1001
** (gdmsetup:3564): DEBUG: Found 0 sessions for user sarah
** (gdmsetup:3564): DEBUG: Getting list of sessions for user 1000
** (gdmsetup:3564): DEBUG: Found 1 sessions for user nealio
** (gdmsetup:3564): DEBUG: GdmUser: adding session /org/freedesktop/ConsoleKit/Session3
** (gdmsetup:3564): DEBUG: GdmUserManager: sessions changed user=nealio num=1
** (gdmsetup:3564): DEBUG: GdmUserManager: added session for user: nealio

** (ck-history:3567): WARNING **: Unable to parse session removed event: seat-id='S1260773304.157 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0

** (gdmsetup:3564): DEBUG: GdmUserManager: history output: mythtv 866

** (gdmsetup:3564): DEBUG: GdmUserManager: excluding user 'mythtv'
** (gdmsetup:3564): DEBUG: GdmUserManager: history output: nealio 167

** (gdmsetup:3564): DEBUG: GdmUserManager: history output: sarah 24

** (gdmsetup:3564): DEBUG: GdmUserManager: history output: nobody 7

** (gdmsetup:3564): DEBUG: GdmUserManager: excluding user 'nobody'
** (gdmsetup:3564): DEBUG: Login freq 1=24 2=167
** (gdmsetup:3564): DEBUG: init user='nealio' auto=False

As of this writing my system is up-to-date in terms of package updates via the Update Manager. Happy to provide any further information as it is important for me to be able to setup auto-login. I also disagree with Sebastien's comment on 2009-11-01 at this being only a corner case affecting one person. I wouldn't imagine the Login Screen dialog to be an often-accessed feature by most average users and therefore the bug would not get as much exposure as, say, a bug in Firefox.