FS#24370 - Rehibernation requires restarting kded4

Attached to Project: Arch Linux
Opened by Amitav (amitavmohanty01) - Saturday, 21 May 2011, 11:51 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 30 May 2011, 08:10 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After a fresh restart, I can hibernate fine. However, after resuming from hibernation irrespective of my usage when I try to hibernate again, it does not work. Checking with top, I found kded4 taking 50% cpu usage. After sending KILL signal to kded4 and restarting it, I can hibernate.

Also while working after resuming from a hibernation, sometimes dolphin takes too long to open. Killing kded4 opens up dolphin instantly.

Additional info:
* package version(s)
2.6.38-ARCH #1 SMP PREEMPT Fri May 13 09:24:47 CEST 2011 x86_64 Intel(R) Core(TM)2 CPU T5300 @ 1.73GHz GenuineIntel GNU/Linux

KDE version: 4.6.3

I have attached gdb backtrace while attached to kded4 process when it was taking up 50% cpu usage.
   kded.log (23.8 KiB)
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Monday, 30 May 2011, 08:10 GMT
Reason for closing:  Fixed
Additional comments about closing:  ntrack 1:13-2
Comment by Amitav (amitavmohanty01) - Friday, 27 May 2011, 16:18 GMT
A slightly different backtrace that I got when dolphin was taking too long due to kded4.
Comment by Amitav (amitavmohanty01) - Saturday, 28 May 2011, 09:11 GMT
It seems it is an issue with ntrack.

The following bugs from KDE bugzilla have similar backtraces.
https://bugs.kde.org/show_bug.cgi?id=274072
https://bugs.kde.org/show_bug.cgi?id=268038

There is also an ntrack bug filed about this issue.
https://bugs.launchpad.net/ntrack/+bug/755608
Comment by Andrea Scarpino (BaSh) - Saturday, 28 May 2011, 10:51 GMT
I cannot reproduce the bug, please test ntrack 1:13-2
Comment by Amitav (amitavmohanty01) - Monday, 30 May 2011, 05:58 GMT
It seems the bug is fixed in ntrack 1:13-2.

Loading...