Version: unspecified OS: Linux kded4 use cpu at 100% WITHOUT ntrack THEN not linked with the bug: https://bugs.kde.org/show_bug.cgi?id=268038 I have attached the process and generated the backtrace: (gdb) thread apply all bt Thread 4 (Thread 0x7f8d24e0d700 (LWP 6212)): #0 0x00007f8d38d1e6c3 in select () from /lib64/libc.so.6 #1 0x00007f8d3a2de35c in ?? () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007f8d3a2104c5 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #3 0x00007f8d39f7dc1a in start_thread () from /lib64/libpthread.so.0 #4 0x00007f8d38d24ebd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f8d1f23f700 (LWP 6248)): #0 0x00007f8d38d1c233 in poll () from /lib64/libc.so.6 #1 0x00007f8d35b21399 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f8d35b21b45 in g_mapped_file_ref () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f8d39f80330 in ?? () from /lib64/libpthread.so.0 #4 0x0000000000001000 in ?? () #5 0x0000000001978090 in ?? () #6 0x00007f8d39f81930 in ?? () from /lib64/libpthread.so.0 #7 0x00007f8d35dec7a0 in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x00007f8d35dec768 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x00007f8d39f80330 in ?? () from /lib64/libpthread.so.0 #10 0x0000000000001000 in ?? () #11 0x00007f8d1f711bb4 in ?? () from /usr/lib64/libgio-2.0.so.0 #12 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f8d1e832700 (LWP 6262)): #0 0x00007f8d38d1c233 in poll () from /lib64/libc.so.6 #1 0x00007f8d35b21399 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f8d35b217ec in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fff7b3b8480 in ?? () #4 0x0000000001742ca0 in ?? () #5 0x00007f8d3a300a92 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007f8d3a300e74 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007f8d3a20d49d in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007f8d3a2e0aa8 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #9 0x00007f8d3a2104c5 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #10 0x00007f8d39f7dc1a in start_thread () from /lib64/libpthread.so.0 #11 0x00007f8d38d24ebd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8d3b6ee760 (LWP 6206)): #0 0x00007f8d39f8256c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f8d3a21108b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007f8d3a210114 in QThread::wait(unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #3 0x00007f8d3a2d3720 in QFileSystemWatcher::~QFileSystemWatcher() () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007f8d3a313c4f in QObjectPrivate::deleteChildren() () from /usr/lib64/qt4/libQtCore.so.4 #5 0x00007f8d3a31b30b in QObject::~QObject() () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007f8d330a27c6 in ?? () from /usr/lib64/libsolid.so.4 #7 0x00007f8d38c87d95 in ?? () from /lib64/libc.so.6 #8 0x00007f8d38c87de5 in exit () from /lib64/libc.so.6 #9 0x00007f8d3950b498 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #10 0x00007f8d3b0ddfc8 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib64/libkdeui.so.5 #11 0x00007f8d3ab7d12e in _XIOError () from /usr/lib64/libX11.so.6 #12 0x00007f8d3ab7c08d in _XEventsQueued () from /usr/lib64/libX11.so.6 #13 0x00007f8d3ab6c28f in XEventsQueued () from /usr/lib64/libX11.so.6 #14 0x00007f8d3954576c in ?? () from /usr/lib64/qt4/libQtGui.so.4 #15 0x00007f8d35b20a09 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #16 0x00007fff00001386 in ?? () #17 0x00007f8d35dec768 in ?? () from /usr/lib64/libglib-2.0.so.0 #18 0x00007f8d35dec7a0 in ?? () from /usr/lib64/libglib-2.0.so.0 #19 0x0000000100000001 in ?? () #20 0x00000000017d1048 in ?? () #21 0x00000000017d1040 in ?? () #22 0x7fffffff00001386 in ?? () #23 0x0000000000000000 in ?? () Reproducible: Sometimes Steps to Reproduce: Na Expected Results: kded4 use cpu at 100% WITHOUT ntrack
Please find the offending kded4 module, as described at http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/ This information is required to address the problem.
What info is missing? I have not time to search the bug, and it's randomly appends.
Hi, I have the same problem for KDE 4.7 after my latest KDE 4.7 update from the Opensuse 11.4 KDE Factory Repository. Everything went smoothly with KDE 4.7 until this latest update. Now "kded4" consumes 100% of one of my cpu cores without any directly identifiable reason. I tried for a new user to exclude any problems with old configuration files for kde apps. This did not help. The hints in http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/ are not very helpful - doing a step by step exclusion of kde modules will be enormously time consuming. For example, I have deinstalled networkmaneger and related modules. This did not help.
OK, it seems to be related to either the present ntrack libs or kdebase4-runtime. When I go from kdebase4-runtime version 4.7.0-8.1 in Opensuses's KDE Factory repository to kdebase4-runtime version 4.7.0-302 in Opensuses's KDE Factory repository the following new libs are installed: libntrack-qt4-1 version 014-4.1 libntrack0 version 014-4.1 ntrack-libnl1 version 014-4.1 With these libraries kded4 runs amok. So for me indeed it is a ntrack problem. Sorry, that I did not see it before.
*** This bug has been marked as a duplicate of bug 217364 ***