Bug 287231

Summary:	Initial KDM login fails if password typed too fast
Product:	kdm	Reporter:	JC Francois <jc>
Component:	general	Assignee:	kdm bugs tracker <kdm-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	jc, kde
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description JC Francois 2011-11-22 09:17:02 UTC

Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

everytime I boot into KDM and try to access my account the login fails. I type my password, press enter and the background of the login and password field turns light red for a few seconds. The password is cleared, I enter my password again and I can get in.

If you closely watch as you type you will see that the second letter is not accepted unless you wait a couple of seconds first or type your password slowly.


Reproducible: Always

Steps to Reproduce:
1. boot into KDM
2. Type password at normal speed

Actual Results:  
Login fails.

Expected Results:  
Login succeeds.

Comment 1 Kai Uwe Broulik 2011-11-22 12:17:11 UTC

I tend to rapidly enter my 40 letter password right when KDM comes up (system boots in like 5 seconds) and never experienced that.

Comment 2 JC Francois 2011-11-22 12:20:43 UTC

On the linux.suse.opensuse.user mailing list there is a number of people complaining from the same problem experienced in openSUSE 12.1.

Comment 3 Oswald Buddenhagen 2011-12-04 12:44:47 UTC

i don't think that the root cause is really the same, but from kdm's perspective it is pretty much the same.

*** This bug has been marked as a duplicate of bug 70790 ***

Comment 4 JC Francois 2011-12-05 13:59:54 UTC

If this problem was fixed in a release of XFree86 in 2004 (which is what bug 70790 is about) I am sure we would have noticed. I am running openSUSE 12.1 based on xorg-x11-7.6-67.1.4.x86_64

Thanks,

JC

Comment 5 Oswald Buddenhagen 2011-12-05 22:03:37 UTC

great. then's let's just let this linger around for one or two years and then notice that it resolved itself mysteriously despite kde not having fixed anything - because it is no kde bug to start with. did you even read what i wrote?

Comment 6 JC Francois 2011-12-06 09:21:55 UTC

Look, all I am sure of is that marking this bug as a duplicate to a bug from 2004 and closing it will not help getting a fix for it.

I don't know if it is a KDE bug or not but I am looking for a solution and if you want me to go away, give me some hints at where to look for one.

Thanks,

JC

Comment 7 Oswald Buddenhagen 2011-12-06 14:16:21 UTC

and i'm not interested in a fix, because i don't think it is a kde bug, and this is the kde bug tracker. ;)
which makes it your problem. you can try to get help from a user support forum for your distribution. to isolate the problem, you can try different version combinations of kde, qt, xorg and linux kernel, see whether users of other distributions have the same problem, compiling packages yourself, etc.
you are welcome to re-open the report if you collect conclusive evidence that the problem is actually in upstream kde (unlike all similar reports i've seen before).