https://bugzilla.novell.com/show_bug.cgi?id=728554
https://bugzilla.novell.com/show_bug.cgi?id=728554#c39
--- Comment #39 from Roland Hughes
Same issue, but (for me at least) it's clearly a timing thing. When I start typing the password on first login, the first char is accepted (dot appears) and then several more are not (no dots). Then of course the login fails. If I wait a few seconds after typing the first char of the password, I have no such problems.
SuSE 12.1 x86_84 clean install, standard KDE environment. /home is on a separate LUKS partition, in case that matters. Waiting after boot-up before starting to type anything does not help. I do see the message from Comment #9 but it comes right after booting, not when I try to login, so I don't think it's that. It has to be something that gets triggered with the first character I type, and then takes some time before more input is accepted.
Your description makes it sound like someone has a focusInEvent() handler which goes out and verifies the network connection after the first keystroke. http://developer.qt.nokia.com/doc/qt-4.8/qlineedit.html If they aren't using Qt, something equivalent happening when field gains focus by first character entered. Network verification would make sense. ALTHOUGH, When a person starts Libre Office to edit an existing document, a very similar thing happens. The document is displayed, but it is several seconds before you can type anything without the characters being eaten. This might be related to the file selection box lag problem if what is really happening after the first character gets entered is the opening of the UAF so the password and user can be more quickly verified. Sorry, don't know Linux name for User Authorization File. For those who are into doing clean installs...do one more. This time make both your root and home partitions EXT3 instead of the default EXT4. See if the problem persists. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.