Bug 274739 - kded takes up to 50% of CPU
Summary: kded takes up to 50% of CPU
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kded (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2011-06-02 10:54 UTC by Tom Kijas
Modified: 2018-10-27 04:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Kijas 2011-06-02 10:54:34 UTC 
Version:           unspecified (using KDE 4.6.3) 
OS:                Linux

Hi, I have this problem:
I use laptop Toshiba Satellite A210 and KDE4.6.3 in Kubuntu 11.04 64-bit.
I wanted to look why my KDE is so slow and realised (using system monitor) that kded takes up to 50% of CPU after resume from suspend-to-RAM.
If I open gnome-system-monitor instead of kde system monitor, kded takes up to 100%!!

Quite a strange, what can I do with it?

Reproducible: Always

Steps to Reproduce:
Login, resume from suspend to RAM (may be not necesary), open system monitor to look at it.

Actual Results:  
kded4 takes up to 50%

Expected Results:  
to work properly

Thanks
Comment 1 Tom Kijas 2011-06-02 11:06:30 UTC 
And when I open system settings -> Service manager, it says it "Cannot get in contact with KDED" (translation from czech).
Comment 2 Christoph Feck 2011-06-02 13:19:04 UTC 
Could you check if it is a duplicate of bug 272527 ? Bug 272527 comment #35 explains which file needs to be removed to prevent kded4 from loading the networkstatus module.
Comment 3 Christoph Feck 2011-06-06 15:22:32 UTC 
If you can provide the information requested in comment #2, please add a comment.
Comment 4 Andrew Crouthamel 2018-09-22 02:07:34 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 04:16:33 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!