One of our users is having trouble with kded4 going crazy and consuming 100% cpu on coming out of hibernate. Have to kill it with kill -9. With it gone, everything seems fine.
So, what does kded4 do? Can I configure kde not to start it? Any known bugs?
Incomplete bt: #0 0x000000394f40a42d in __pthread_mutex_unlock_usercnt (mutex=<value optimized out>, mutex=<value optimized out>, decr=<value optimized out>) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=<value optimized out>, mutex=<value optimized out>, decr=<value optimized out>) at pthread_mutex_unlock.c:289
#2 0x00000030f3a3a8fe in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x00000030f3a3ace1 in ?? () from /lib64/libglib-2.0.so.0
#4 0x00000030f3a3b20a in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x00000030f4b67936 in QEventDispatcherGlib::processEvents (this=0x2140d90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #6 0x00000030f6821f8e in QGuiEventDispatcherGlib::processEvents (this=0x21749f8, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #7 0x00000030f4b4059f in QCoreApplication::processEvents (flags={i = 1}) at kernel/qcoreapplication.cpp:803 #8 0x0000003908012fd7 in DNSSD::RemoteService::resolve() () from /usr/lib64/libkdnssd.so.4 #9 0x00007f66425f4915 in KUrl::setPath(QString const&) () from /usr/lib64/libmolletnetwork.so.4 #10 0x00007f66425f3b05 in KUrl::setPath(QString const&) () from /usr/lib64/libmolletnetwork.so.4 #11 0x00000030f4b547dc in QMetaObject::activate (sender=0x236b600, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x394f40a400) at kernel/qobject.cpp:3113 #12 0x000000390800ee35 in DNSSD::ServiceBrowser::serviceRemoved(KSharedPtrDNSSD::RemoteService) () from /usr/lib64/libkdnssd.so.4 #13 0x000000390800f804 in ?? () from /usr/lib64/libkdnssd.so.4 #14 0x00000039080103f5 in ?? () from /usr/lib64/libkdnssd.so.4 #15 0x00000030f4b547dc in QMetaObject::activate (sender=0x2423ba0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x394f40a400) at kernel/qobject.cpp:3113 #16 0x000000390801d657 in ?? () from /usr/lib64/libkdnssd.so.4 #17 0x000000390801d909 in ?? () from /usr/lib64/libkdnssd.so.4 #18 0x00000030f5022e54 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=@0x258db70, slotIdx=<value optimized out>) at qdbusintegrator.cpp:891
Orion Poplawski wrote:
One of our users is having trouble with kded4 going crazy and consuming 100% cpu on coming out of hibernate. Have to kill it with kill -9. With it gone, everything seems fine.
So, what does kded4 do? Can I configure kde not to start it? Any known bugs?
kded4 controls most/all of kde's internal services/servers, not practical to try to live without it. It's likely one of those services inducing the problem here.
rpm -q qt kdelibs please
-- Rex
Incomplete bt: #0 0x000000394f40a42d in __pthread_mutex_unlock_usercnt (mutex=<value optimized out>, mutex=<value optimized out>, decr=<value optimized out>) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=<value optimized out>, mutex=<value optimized out>, decr=<value optimized out>) at pthread_mutex_unlock.c:289
#2 0x00000030f3a3a8fe in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x00000030f3a3ace1 in ?? () from /lib64/libglib-2.0.so.0
#4 0x00000030f3a3b20a in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x00000030f4b67936 in QEventDispatcherGlib::processEvents (this=0x2140d90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #6 0x00000030f6821f8e in QGuiEventDispatcherGlib::processEvents (this=0x21749f8, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #7 0x00000030f4b4059f in QCoreApplication::processEvents (flags={i = 1}) at kernel/qcoreapplication.cpp:803 #8 0x0000003908012fd7 in DNSSD::RemoteService::resolve() () from /usr/lib64/libkdnssd.so.4 #9 0x00007f66425f4915 in KUrl::setPath(QString const&) () from /usr/lib64/libmolletnetwork.so.4 #10 0x00007f66425f3b05 in KUrl::setPath(QString const&) () from /usr/lib64/libmolletnetwork.so.4 #11 0x00000030f4b547dc in QMetaObject::activate (sender=0x236b600, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x394f40a400) at kernel/qobject.cpp:3113 #12 0x000000390800ee35 in DNSSD::ServiceBrowser::serviceRemoved(KSharedPtrDNSSD::RemoteService) () from /usr/lib64/libkdnssd.so.4 #13 0x000000390800f804 in ?? () from /usr/lib64/libkdnssd.so.4 #14 0x00000039080103f5 in ?? () from /usr/lib64/libkdnssd.so.4 #15 0x00000030f4b547dc in QMetaObject::activate (sender=0x2423ba0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x394f40a400) at kernel/qobject.cpp:3113 #16 0x000000390801d657 in ?? () from /usr/lib64/libkdnssd.so.4 #17 0x000000390801d909 in ?? () from /usr/lib64/libkdnssd.so.4 #18 0x00000030f5022e54 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=@0x258db70, slotIdx=<value optimized out>) at qdbusintegrator.cpp:891
On 11/03/2009 10:33 AM, Rex Dieter wrote:
Orion Poplawski wrote:
One of our users is having trouble with kded4 going crazy and consuming 100% cpu on coming out of hibernate. Have to kill it with kill -9. With it gone, everything seems fine.
So, what does kded4 do? Can I configure kde not to start it? Any known bugs?
kded4 controls most/all of kde's internal services/servers, not practical to try to live without it. It's likely one of those services inducing the problem here.
I kind of thought it was critical too, but the user finds no trouble with out it. Could be that he hardly makes use of KDE though and just runs in terminals.
rpm -q qt kdelibs please
qt-4.5.2-3.fc11.i586 qt-4.5.2-3.fc11.x86_64 kdelibs-4.3.2-4.fc11.x86_64
Been happening for a little while now.
-
Orion Poplawski -
Rex Dieter