kded crashes in KWallet (forgotten KMail password)

Bug #86168 reported by Rocco Stanzione
14
Affects Status Importance Assigned to Milestone
kdelibs
Invalid
Medium
kdelibs (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: kdelibs

Kded crashes randomly but frequently (about once per day). The problem began in Edgy but persists in Feisty. I was finally able to capture a backtrace. It usually crashes silently, and I only know it's happened because kmail doesn't know my passwords.

Revision history for this message
Rocco Stanzione (trappist) wrote :
Revision history for this message
Marco Maini (maini10) wrote :

This bug is very similar to a KDE bugs currently unpatched. However a similar bug was reported and fixed in Debian as n° 407272.

Changed in kdelibs:
status: Unconfirmed → Confirmed
Changed in kdelibs:
status: Unknown → Confirmed
Revision history for this message
Paco Orozco (pakusland) wrote :

I can confirm this bug on Feisty. Moreover It usually works bad when I first use KwalletManager.

1) I start my KDE
2) Open Kmail
3) KwalletManager prompts for password. I supply it
4) kded eats 100% of CPU. Kmail freezes.

The only way to continue working is killing kded.

If I kill kded, launch kwalletmanager, open a wallet and then open Kmail.. .all woirks great.

I hope you can help us.

Revision history for this message
Rich Johnson (nixternal) wrote :

kded hit 1.3% at the most here and KMail and KWallet stay open for roughly 12 to 18 hours a day on this machine.

Revision history for this message
Stephen Beynon (stephen-octopus-technologies) wrote :

I sometimes see this problem as well. Kded uses high (95%+) cpu, and all konqueror windows updates stop.

I only see it shortly after I login to kde. I have a large number of konqueror windows, kopete, kontact etc that automatically open and want access to kwallet for passwords. The problem with kded will happen about 20% of the time when I enter the wallet password for the first time. The problem happens as soon as I enter the password. I have waited with the wallet password prompt up for 5 mins to check this.

I have only seen the problem shortly after kde login, I have never seen it after hours or days of using kde when I have to re-open a wallet.

Regards

Stephen

Revision history for this message
Marc Carson (baggageclaim) wrote :

Stephen, I had the same problem. I fixed it by following this advice:

http://ubuntuforums.org/showpost.php?p=2567873&postcount=2

I deleted kwalletrc and logged in again, and no more problem.

Revision history for this message
hunger (hunger) wrote :

I am seeing exactly the same problem in hardy.

KDE has a bugreport: http://bugs.kde.org/show_bug.cgi?id=64671 that is resolved. Maybe there is a regression in Qt in hardy?

Revision history for this message
Risto H. Kurppa (risto.kurppa) wrote :

Confirm this on Gutsy w. 3.5.9 (but I've had it on 3.5.8 as well, maybe even 3.5.7, not sure).

Log in
KWallet asks for password (for Kopete)
Type in password
-> KDED starts eating 100% of processor power, all KDE applications stop (akregator, kopete, konqueror..)

Killing the kded process solves this.

Looks like that kded likes to eat some resources:
https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/115739
https://bugs.launchpad.net/ubuntu/+source/kdelibs/+bug/194474
https://bugs.launchpad.net/ubuntu/+source/kdelibs/+bug/196005
(Maybe not duplicates but in all of them 100% of processor resources are used because of 'different reasons')

Funny enough, the KDE bugrep is from year 2003..

Changed in kdelibs:
status: Confirmed → Invalid
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fixed in KDE 4.1 according to the upstream report.

Changed in kdelibs:
status: Confirmed → Fix Released
Changed in kdelibs:
status: Invalid → Unknown
Changed in kdelibs:
importance: Unknown → Medium
Changed in kdelibs:
status: Unknown → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.