"authentication failed" on "switch user" with timed login

[Wouter den Haan]

Firstly, I am using a Hoary -> Breezy -> Dapper dist-upgraded dapper.

I setup a timed login (5 sec.) for a user. When that user is logged in already, the "new login" or "switch user" dialog opens up a new gdm in vt8. Naturally, it tries to do the timed login again (question: is this wanted if this user is logged in already?). It fails to do so with the following error: "Authentication failed. Letters must be typed in the correct case"

I do not know whether the auto-login is supposed to be performed anyway when $user is logged in already. But i do feel that this error-message is the wrong one. Moreover, this results in a failed login every five seconds for me, which looks quite bad in my logfiles :-P

Maybe it is an idea to do a check whether a user for whom the timed login is setup is already logged in? Or to not allow timed-logins on gdm-sessions started with the "switch user" dialog?

[Wouter den Haan (wouterdenhaan)]

The user does not neccessarily have to be logged in already. It appears that the timed login just does not work on a second (or third, ... ) gdm.

[Sebastien Bacher (seb128)]

Thanks for your bug. Could you describe what you do exactly, what happens and what you would expect? The automatic login happens on startup only, if you switch user that's probably not to run the same user again

[Wouter den Haan (wouterdenhaan)]

> Comment:
> Thanks for your bug. Could you describe what you do exactly *(A)*, what
> happens *(B) *and what you would expect* (C)*? The automatic login happens
on
> startup only, if you switch user that's probably not to run the same
> user again *(D)*

(A) I click log-out -> switch user. The timed login is turned on.
(B) This results in a new GDM-login window and tries to autologin, which
fails.
(C) I would expect that the timed login would log me in, or, that the timed
login is not performed on a second GDM. The latter might be the more logical
one. Alternatively, a check could be performed whether the user for which
the timed-login is configured is already logged in.
(D) Your last remark might be correct for an automatic login, it is not for
a timed login. At least the last time I tried.

[Wouter den Haan (wouterdenhaan)]

> Thanks for your bug. Could you describe what you do exactly (A), what happens (B) and what you would expect (C)? The automatic login happens on startup only, if you switch user that's probably not to run the same user again (D)

(A) I click log-out -> switch user. I set-up a timed login to log in my default user after 5 seconds.
(B) This results in a new GDM-login window and tries to autologin (after 5 seconds), which fails and then tries again (and again, ...)
(C) I would expect that the timed login would log me in, or that it is not performed on a second GDM. The latter might be the more logical one. Alternatively, a check could be performed whether the user for which the timed-login is configured is already logged in.
(D) Your last remark might be correct for an automatic login, it is not for a timed login. At least the last time I tried.

[Wouter den Haan (wouterdenhaan)]

Sorry for the double-post.. Didn't think the email-reply would work. :-P

I recommend one only reads the last one. I altered it a bit.

[Sebastien Bacher (seb128)]

Does the message say it will connect your user, or the user "Linux"?

[Wouter den Haan (wouterdenhaan)]

 It says something like "Logging in wouter in X seconds". Where "X" counts
down to zero and "wouter" is my username.

So it says it will connect my user.

[Sebastien Bacher (seb128)]

I've forwarded your issue upstream: http://bugzilla.gnome.org/show_bug.cgi?id=336174

[Wouter den Haan (wouterdenhaan)]

this bug appears to be fixed. When opening a second gdm-session, it does not try to do the timed-login anymore.

[Pedro Villavicencio (pedro)]

Can someone else try to confirm that the bug is fixed now? thanks.

[Bernt (bernt-hullen)]

Wouter den Haan schrieb:
> this bug appears to be fixed. When opening a second gdm-session, it does
> not try to do the timed-login anymore.

This _is_ the bug!

[Wouter den Haan (wouterdenhaan)]

I know what the bug is, since I filed it. :-) And it is definitely fixed..

Things have changed since I reported this bug and the timed-login does _not_ occur on a second GDM anymore. I guess this is the most sensible behaviour..

[Graham C (chckens)]

I tested this in current Intrepid and was unable to reproduce it. Since even the original reporter believes this issue to be long since resolved, marking fixed.