Summary: | kded eats CPU to a crawl. Is it proxy to blame? | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | apodtele |
Component: | kded | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
apodtele
2005-09-26 23:15:50 UTC
I'm running KDE 3.4.2 in Mandriva 2006, AMD64 version (x86_64). As soon as KDE starts, kded runs up the cpu to 70-90% in cycles. Apps start very slowly. I have plenty of memory and virtually no swap is used. Doing a "dcop kded" I get: KDebug KDirNotify-1 KDirNotify-2 KDirNotify-3 KDirNotify-4 MainApplication-Interface dnssdwatcher katd kbuildsycoca kded ksycoca kwalletd kwrited mdvdirnotify mediamanager networkstatus qt/kded remotedirnotify systemdirnotify I have the equivalent system (same kde version and services running) on my Pentium M laptop but kded is well-behaved on it. "katd" is the culprit. Disable it, uninstall it or upgrade to a version that doesn't consume that much CPU. Mandriva should never have shipped it in pre-alpha stage. This is CRAP. Comment #1 just highjacked my original bug with something which has NOTHING to do with my problem, then comment #2 happily "resolved" the irrelevant issue. kded still hogs CPU with PROXY connections... I don't know how, I doubt that it should. |