[Bug 186724] New: Password dialogs consume 100% CPU and drop input

David icydog at bellsouth.net
Tue Mar 10 04:46:28 GMT 2009


https://bugs.kde.org/show_bug.cgi?id=186724

           Summary: Password dialogs consume 100% CPU and drop input
           Product: kde
           Version: unspecified
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: icydog at bellsouth.net


Version:            (using KDE 4.2.1)
Compiler:          gcc 4.3 
OS:                Linux
Installed from:    Fedora RPMs

Whenever a password dialog is displayed, e.g. from kwallet due to Kopete, or
Kontact, or the networkmanager plasmoid, CPU usage jumps to 100%. Hitting keys
on the keyboard causes *'s to show up in the password field, but sometimes they
lag by up to several seconds, and sometimes keys will be completely dropped.
This causes me to have to type my password character-by-character to make sure
my keystrokes are accepted, or else it will drop some randomly and I'll have to
enter it again.

Steps to reproduce:

1. Cause KDE to ask for a password (e.g. the screensaver lock, kwallet, or run
kdepasswd).
2. Observe that CPU usage is at 100% (for me, 70% by X and about 17% by kded4
or kdepasswd or whatever's asking for the password). Also observe that *'s take
a while to show up, and sometimes get dropped (i.e. it's as if you didn't type
them).

Expected results:
CPU usage is low. Keyboard presses are accepted and show up on the screen
instantly.

This happens on both my Dell Inspiron 1420 and Inspiron Mini 9. They are
running Fedora 10 and SuSE 11.1, with KDE 4.2.1 from kde-redhat repository and
OpenSUSE Factory. This was also present in KDE 4.2.0 on both machines. Both
machines have Intel integrated graphics -- I think this is relevant. Both
machines suffer from this bug identically.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list