Bug 294987 - Second key pressed is always skipped
Summary: Second key pressed is always skipped
Status: RESOLVED DUPLICATE of bug 280982
Alias: None
Product: kdm
Classification: Miscellaneous
Component: general (show other bugs)
Version: 0.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdm bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-28 10:23 UTC by Christopher Bräuer
Modified: 2013-01-21 23:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Bräuer 2012-02-28 10:23:01 UTC 
Version:           0.1 (using KDE 4.8.0) 
OS:                Linux

When I want to log into kde, the second key I pressed, is always skipped. In my password, the second and third key are the same. If I type it slow, it works.
But if I delete the wrong password or have to put it in again, I can type it fast as usual and it works.
Same on a PC from my friend.

Reproducible: Always

Steps to Reproduce:
Type in the password fast the first time.

Actual Results:  
Login failed.

Expected Results:  
Login should work.

OS: Linux (x86_64) release 3.1.9-1.4-desktop
Compiler: gcc
Comment 1 regi.hops 2012-03-17 14:27:32 UTC 
Hi,
same on my box.
Seems to be an openSUSE related problem:
https://bugzilla.novell.com/show_bug.cgi?id=728554

Hope there will be a solution soon...

Cheers
Regi
Comment 2 Nudge 2012-10-05 16:55:19 UTC 
This bug is also present on Debian Testing (kdm_4.8.4-3_i386.deb)
And it has been there since over months as I remember correctly.

There is something loading after the first key is pressed.
No matter how long I wait before I start to type, my
disk usage LED blinks as soon as I hit the key and I can hear my HDD.
This load somehow defers the update in the password field for some seconds.
If I ignore the load and type on, the password field is filled after the load is over.

My guess is that after this initial keypress, kdm is initializing the user's login
method (LDAP or local shadow or whatever)...
Comment 3 Christopher Bräuer 2013-01-15 19:13:18 UTC 
The bug is still there, after so many month!
Anybody working on it?
Comment 4 Christoph Feck 2013-01-21 23:19:33 UTC 

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