Summary: | kded4 uses a CPU core on 100% | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Unknown <null> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | cfeck, null |
Priority: | NOR | ||
Version: | 0.0.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Unknown
2011-08-18 10:41:39 UTC
Unfortunately, the backtrace does not show where it hangs, the backtrace from comment #0 just points to the main event loop. Could you check if this is a duplicate of bug 268038? Bug 268038 comment #27 has some openSUSE specific discussion. If ntrack is not the cause, you probably have to follow http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/ to find the kded module that causes the issue. If you can provide the information requested in comment #1, please add it. Sorry for the late answer, I've accidentally archived the notification mail. Up to this date I haven't even known that I have ntrack installed, but zypper said so; and the version is the same (014) as in the linked comment you pointed to. Besides, the blog post was really useful; next time I report a bug against kded4, I'll take care. Now, I close this as a duplicate, and if after an ntrack upgrade I can reproduce this, I'll reopen. *** This bug has been marked as a duplicate of bug 26038 *** *** This bug has been marked as a duplicate of bug 268038 *** |