Summary: | kwalletd drains CPU while waiting for password input | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Thilo-Alexander Ginkel <thilo> |
Component: | kwallet | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | lemma |
Priority: | NOR | ||
Version: | 4.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | strace for kwalletd |
Description
Thilo-Alexander Ginkel
2008-10-02 08:43:30 UTC
Created attachment 27651 [details]
strace for kwalletd
Attaching strace to the CPU-consuming kwalletd process shows heavy polling activity...
Does this only happen if kopete asks for the password or for other applications (eg. konqueror, dolphin, kmail) as well? That said I can't reproduce this using my kopete from 4.1.2. If possible, please upgrade to the new version and retry. The problem still occurs with KDE 4.1.2. I will later (most likely on Thursday) test whether the issue also applies to other applications that use kwalletd. It took a few days more than expected, but I now verified that the CPU usage also spikes when the display of the KDE wallet password entry dialog was triggered by another application such as konqueror. I also just did a distribution upgrade from Ubuntu Hardy to Intrepid (resetting my .kde profile), which unfortunately did not improve the situation. Thanks for providing some more information. Unfortunately I still can't reproduce but I have a slight idea what might happen there. If I'm right this might already be fixed in the current trunk. If I'm wrong I'm pretty much clueless about how this bug happens. Please recheck when you've upgraded to KDE 4.2. I tested this with the current KDE 4.2 nightly packages (Kubuntu Neon) and the problem actually seems to be solved in that branch. Is there any chance of getting this fix downported into the 4.1.x branch or do you think it's not worth the effort? Unfortunately backporting is not possible due to two reasons: 1) I don't know exactly what fixed it. 2) If it is what I expect it to have fixed it it doesn't qualify for backporting. Sorry. |