Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#2514 - KDED is taking 100% CPU on first KWallet access
Attached to Project:
Arch Linux
Opened by Nathan Adams (syphoon) - Thursday, 07 April 2005, 00:14 GMT
Last edited by Judd Vinet (judd) - Thursday, 07 April 2005, 20:34 GMT
Opened by Nathan Adams (syphoon) - Thursday, 07 April 2005, 00:14 GMT
Last edited by Judd Vinet (judd) - Thursday, 07 April 2005, 20:34 GMT
|
DetailsUpon resuming a KDE 3.4 session several apps request KWallet access. They hang, but the rest of the desktop is usable. But the moment I try to type something into Konqueror, system freezes.
Dropping to console reveals the kded process is taking 100% CPU. Only a kill -9 is able to resume the session. If upon resuming the KDE session (after start-up) kwallet is closed straight away and all requests for passwords denied, the CPU stays idle. |
This task depends upon
Comment by Tobias Powalowski (tpowa) -
Saturday, 04 June 2005, 07:52 GMT
Is this still valid in kde 3.4.1?
Comment by Jan Huelsbergen (afoo) -
Sunday, 05 June 2005, 18:53 GMT
At least I wasn't able to reproduce it using 3.4.1.