Version: (using KDE 3.5.9) Installed from: Ubuntu Packages OS: Linux I just upgraded from KDE 3.5.8 to KDE 3.5.9, and the desktop became unusable... Konqueror does not start up anymore. It gets stuck here: (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb7cf9c53 in read () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7221c1e in _kde_IceTransSocketRead (ciptr=0x8088e20, buf=0x808cc80 "\002\003", size=8) at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/Xtranssock.c:1710 #3 0xb72218cf in _kde_IceTransRead (ciptr=0x8088e20, buf=0x808cc80 "\002\003", size=8) at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/Xtrans.c:845 #4 0xb721b71f in _kde_IceRead (iceConn=0x8086ef8, nbytes=8, ptr=0x808cc80 "\002\003") at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/misc.c:249 #5 0xb721ff1f in KDE_IceProcessMessages (iceConn=0x8086ef8, replyWait=0xbf8cfb38, replyReadyRet=0xbf8cfb88) at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/process.c:153 #6 0xb720b679 in DCOPClient::callInternal (this=0x808c920, remApp=@0xbf8cfd3c, remObjId=@0xbf8cfd44, remFun=@0xbf8cfcc4, data=@0xbf8cfd8c, replyStruct=0xbf8cfbe4, useEventLoop=false, timeout=-1, minor_opcode=2) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:1934 #7 0xb720b95d in DCOPClient::callInternal (this=0x808c920, remApp=@0xbf8cfd3c, remObjId=@0xbf8cfd44, remFun=@0xbf8cfcc4, data=@0xbf8cfd8c, replyType=@0xbf8cfd78, replyData=@0xbf8cfd70, useEventLoop=false, timeout=-1, minor_opcode=2) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:1824 #8 0xb72103a7 in DCOPClient::call (this=0x808c920, remApp=@0xbf8cfd3c, remObjId=@0xbf8cfd44, remFun=@0xbf8cfcc4, data=@0xbf8cfd8c, replyType=@0xbf8cfd78, replyData=@0xbf8cfd70, useEventLoop=false, timeout=-1) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:1768 #9 0xb72132b6 in DCOPRef::callInternal (this=0xbf8cfd3c, fun=@0xbf8cfdac, args=@0xbf8cfd94, data=@0xbf8cfd8c, useEventLoop=NoEventLoop, timeout=-1) at /build/buildd/kdelibs-3.5.9/./dcop/dcopref.cpp:77 #10 0xb72133ce in DCOPRef::callInternal (this=0xbf8cfd3c, fun=@0xbf8cfdac, args=@0xbf8cfd94, data=@0xbf8cfd8c) at /build/buildd/kdelibs-3.5.9/./dcop/dcopref.cpp:52 #11 0xb799c72b in KMimeType::favIconForURL (url=@0xbf8d0008) at /build/buildd/kdelibs-3.5.9/./dcop/dcopref.h:464 #12 0xb5dc8f11 in SearchBarPlugin::setIcon () from /usr/lib/kde3/libsearchbarplugin.so #13 0xb5dc9efe in SearchBarPlugin::configurationChanged () from /usr/lib/kde3/libsearchbarplugin.so #14 0xb5dca69f in SearchBarPlugin::SearchBarPlugin () from /usr/lib/kde3/libsearchbarplugin.so #15 0xb5dcceb2 in KGenericFactory<SearchBarPlugin, QObject>::createObject () from /usr/lib/kde3/libsearchbarplugin.so #16 0xb731eaa1 in KLibFactory::create (this=0x82022e0, parent=0x80ab110, name=0x81fd948 "libsearchbarplugin", classname=0xb7b45c78 "KParts::Plugin", args=@0xbf8d0418) at /build/buildd/kdelibs-3.5.9/./kdecore/klibloader.cpp:83 #17 0xb7b34429 in KParts::Plugin::loadPlugin (parent=0x80ab110, libname=0x81fd948 "libsearchbarplugin") at /build/buildd/kdelibs-3.5.9/./kparts/../kparts/componentfactory.h:67 #18 0xb7b3dca3 in KParts::Plugin::loadPlugins (parent=0x80ab110, parentGUIClient=0x80ab3e0, instance=0xbf8d0c90, enableNewPluginsByDefault=true) at /build/buildd/kdelibs-3.5.9/./kparts/plugin.cpp:301 #19 0xb7b3de54 in KParts::PartBase::loadPlugins (this=0x80ab3ec, parent=0x80ab110, parentGUIClient=0x80ab3e0, instance=0xbf8d0c90) at /build/buildd/kdelibs-3.5.9/./kparts/part.cpp:125 #20 0xb7b3eb9c in KParts::PartBase::setInstance (this=0x80ab3ec, inst=0xbf8d0c90, bLoadPlugins=true) at /build/buildd/kdelibs-3.5.9/./kparts/part.cpp:119 #21 0xb7b27d40 in KParts::PartBase::setInstance (this=0x80ab3ec, inst=0xbf8d0c90) at /build/buildd/kdelibs-3.5.9/./kparts/part.cpp:107 #22 0xb7f4a030 in KonqMainWindow::KonqMainWindow () from /usr/lib/libkdeinit_konqueror.so #23 0xb7f4e74b in KonqMisc::createBrowserWindowFromProfile () from /usr/lib/libkdeinit_konqueror.so #24 0xb7f564dd in kdemain () from /usr/lib/libkdeinit_konqueror.so #25 0x080484b2 in ?? () #26 0x00000001 in ?? () #27 0xbf8d0de4 in ?? () #28 0xbf8d0d58 in ?? () #29 0x080484e9 in ?? () #30 0xb7fb0800 in ?? () from /lib/ld-linux.so.2 #31 0xbf8d0d60 in ?? () #32 0xbf8d0db8 in ?? () #33 0xb7c4c050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 ---Type <return> to continue, or q <return> to quit--- Backtrace stopped: frame did not save the PC Amarok starts up, but freezes after a few seconds. Its backtrace looks similar: (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb672ac7b in read () from /lib/tls/i686/cmov/libc.so.6 #2 0xb5e06c1e in _kde_IceTransSocketRead (ciptr=0x80c6158, buf=0x80bf660 "\002\001", size=8) at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/Xtranssock.c:1710 #3 0xb5e068cf in _kde_IceTransRead (ciptr=0x80c6158, buf=0x80bf660 "\002\001", size=8) at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/Xtrans.c:845 #4 0xb5e0071f in _kde_IceRead (iceConn=0x80c3d40, nbytes=8, ptr=0x80bf660 "\002\001") at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/misc.c:249 #5 0xb5e04f1f in KDE_IceProcessMessages (iceConn=0x80c3d40, replyWait=0xbfd9c408, replyReadyRet=0xbfd9c458) at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/process.c:153 #6 0xb5df0679 in DCOPClient::callInternal (this=0x80c3398, remApp=@0xbfd9c654, remObjId=@0xbfd9c64c, remFun=@0xbfd9c644, data=@0xbfd9c634, replyStruct=0xbfd9c4b4, useEventLoop=false, timeout=-1, minor_opcode=2) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:1934 #7 0xb5df095d in DCOPClient::callInternal (this=0x80c3398, remApp=@0xbfd9c654, remObjId=@0xbfd9c64c, remFun=@0xbfd9c644, data=@0xbfd9c634, replyType=@0xbfd9c624, replyData=@0xbfd9c62c, useEventLoop=false, timeout=-1, minor_opcode=2) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:1824 #8 0xb5df53a7 in DCOPClient::call (this=0x80c3398, remApp=@0xbfd9c654, remObjId=@0xbfd9c64c, remFun=@0xbfd9c644, data=@0xbfd9c634, replyType=@0xbfd9c624, replyData=@0xbfd9c62c, useEventLoop=false, timeout=-1) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:1768 #9 0xb5df5407 in DCOPClient::call (this=0x80c3398, remApp=@0xbfd9c654, remObjId=@0xbfd9c64c, remFun=@0xbfd9c644, data=@0xbfd9c634, replyType=@0xbfd9c624, replyData=@0xbfd9c62c, useEventLoop=false) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:1733 #10 0xb7be0545 in DeviceManager::getDeviceStringList () from /usr/lib/libamarok.so.0 #11 0xb7be08cf in DeviceManager::getDeviceList () from /usr/lib/libamarok.so.0 #12 0xb7c46e4b in MediaDeviceManager::reinitDevices () from /usr/lib/libamarok.so.0 #13 0xb7c4783b in MediaDeviceManager::qt_invoke () from /usr/lib/libamarok.so.0 #14 0xb618c893 in QObject::activate_signal (this=0x8222de0, clist=0x8222f48, o=0xbfd9c7a8) at kernel/qobject.cpp:2356 #15 0xb65188ec in QSignal::signal (this=0x8222de0, t0=@0x8222e08) at .moc/debug-shared-mt/moc_qsignal.cpp:100 #16 0xb61ac842 in QSignal::activate (this=0x8222de0) at kernel/qsignal.cpp:212 #17 0xb61b4258 in QSingleShotTimer::event (this=0x8222db8) at kernel/qtimer.cpp:286 #18 0xb6123af0 in QApplication::internalNotify (this=0xbfd9cd70, receiver=0x8222db8, e=0xbfd9caf8) at kernel/qapplication.cpp:2635 #19 0xb612591f in QApplication::notify (this=0xbfd9cd70, receiver=0x8222db8, e=0xbfd9caf8) at kernel/qapplication.cpp:2358 #20 0xb7244a32 in KApplication::notify (this=0xbfd9cd70, receiver=0x8222db8, event=0xbfd9caf8) at /build/buildd/kdelibs-3.5.9/./kdecore/kapplication.cpp:550 #21 0xb60b6209 in QApplication::sendEvent (receiver=0x8222db8, event=0xbfd9caf8) at ../include/qapplication.h:520 #22 0xb611653b in QEventLoop::activateTimers (this=0x80b0ee0) at kernel/qeventloop_unix.cpp:556 #23 0xb60cad49 in QEventLoop::processEvents (this=0x80b0ee0, flags=4) at kernel/qeventloop_x11.cpp:389 #24 0xb613e1ce in QEventLoop::enterLoop (this=0x80b0ee0) at kernel/qeventloop.cpp:198 #25 0xb613dfde in QEventLoop::exec (this=0x80b0ee0) at kernel/qeventloop.cpp:145 #26 0xb6125699 in QApplication::exec (this=0xbfd9cd70) at kernel/qapplication.cpp:2758 #27 0x0804bfa2 in ?? () #28 0xbfd9cd70 in ?? () #29 0xbfd9cf04 in ?? () #30 0x0806a806 in ?? () #31 0x0806a7f5 in ?? () #32 0x00000000 in ?? () Sometimes, the whole desktop freezes: the applications keep running (e.g., the System Monitor applet keeps repainting itself), but nothing responds to mouse or keyboard events - not even the window manager. I tried logging out and logging in a few times - no difference.
when I killed Konqueror and Amarok, I saw that I had two instances of kded running, each using up almost 100% of my two CPUs. They had identical stack traces (except for 0x... addresses): #0 QValueListPrivate<int>::contains (this=0x828fd78, x=@0xbfda25f8) at /usr/share/qt3/include/qvaluelist.h:115 #1 0xb639c423 in HomeDirNotify::init () from /usr/lib/kde3/kded_homedirnotify.so #2 0xb639ca7f in HomeDirNotify::toHomeURLList () from /usr/lib/kde3/kded_homedirnotify.so #3 0xb639d250 in HomeDirNotify::FilesRemoved () from /usr/lib/kde3/kded_homedirnotify.so #4 0xb639cf7e in HomeDirNotify::process () from /usr/lib/kde3/kded_homedirnotify.so #5 0xb6a6b0d7 in DCOPClient::receive (this=0x8088458, objId=@0xbfda29cc, fun=@0xbfda29c4, data=@0xbfda29bc, replyType=@0xbfda29b4, replyData=@0xbfda29ac) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:1643 #6 0xb6a6c82b in DCOPProcessInternal (d=0x80a5fd0, opcode=1, key=1, dataReceived=@0xbfda2a88, canPost=true) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:520 #7 0xb6a6cf55 in DCOPProcessMessage (iceConn=0x809e680, clientObject=0x80a5fd0, opcode=1, length=229, replyWait=0x0, replyWaitRet=0xbfda2af4) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:432 #8 0xb6a7d280 in KDE_IceProcessMessages (iceConn=0x809e680, replyWait=0x0, replyReadyRet=0x0) at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/process.c:326 #9 0xb6a635c3 in DCOPClient::processSocketData (this=0x8088458, fd=3) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:2014 #10 0xb6a6cb59 in DCOPClient::qt_invoke (this=0x8088458, _id=2, _o=0xbfda2c98) at ./dcopclient.moc:176 #11 0xb7224893 in QObject::activate_signal (this=0x80ab5d0, clist=0x80bba28, o=0xbfda2c98) at kernel/qobject.cpp:2356 #12 0xb72251aa in QObject::activate_signal (this=0x80ab5d0, signal=2, param=3) at kernel/qobject.cpp:2449 #13 0xb75b1683 in QSocketNotifier::activated (this=0x80ab5d0, t0=3) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85 #14 0xb724746e in QSocketNotifier::event (this=0x80ab5d0, e=0xbfda2fc8) at kernel/qsocketnotifier.cpp:258 #15 0xb71bbaf0 in QApplication::internalNotify (this=0xbfda3384, receiver=0x80ab5d0, e=0xbfda2fc8) at kernel/qapplication.cpp:2635 #16 0xb71bd91f in QApplication::notify (this=0xbfda3384, receiver=0x80ab5d0, e=0xbfda2fc8) at kernel/qapplication.cpp:2358 #17 0xb78a9a32 in KApplication::notify (this=0xbfda3384, receiver=0x80ab5d0, event=0xbfda2fc8) at /build/buildd/kdelibs-3.5.9/./kdecore/kapplication.cpp:550 #18 0xb714e209 in QApplication::sendEvent (receiver=0x80ab5d0, event=0xbfda2fc8) at ../include/qapplication.h:520 #19 0xb71adee9 in QEventLoop::activateSocketNotifiers (this=0x80ae4d8) at kernel/qeventloop_unix.cpp:578 #20 0xb7162d2b in QEventLoop::processEvents (this=0x80ae4d8, flags=4) at kernel/qeventloop_x11.cpp:383 #21 0xb71d61ce in QEventLoop::enterLoop (this=0x80ae4d8) at kernel/qeventloop.cpp:198 #22 0xb71d5fde in QEventLoop::exec (this=0x80ae4d8) at kernel/qeventloop.cpp:145 #23 0xb71bd699 in QApplication::exec (this=0xbfda3384) at kernel/qapplication.cpp:2758 #24 0xb66d2a38 in kdemain (argc=2, argv=0x8082510) at /build/buildd/kdelibs-3.5.9/./kded/kded.cpp:961 #25 0xb7f56454 in kdeinitmain (argc=2, argv=0x8082510) at kded_dummy.cpp:3 #26 0x0804e6ff in launch (argc=2, _name=0x80510b9 "kded", args=0x80510dc "", cwd=0x0, envc=0, envs=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8051034 "0") at /build/buildd/kdelibs-3.5.9/./kinit/kinit.cpp:673 #27 0x08050497 in main (argc=5, argv=0xbfda3844, envp=0xbfda385c) at /build/buildd/kdelibs-3.5.9/./kinit/kinit.cpp:1855 #28 0xb7cb4050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #29 0x0804bba1 in _start ()
Oops, sorry, didn't realize that I picked a Kopete-specific component. I should also add - it started working fine after killing kded.
I upgraded to KDE 4.1 - and it's even worse. I have to kill kded every time I start KDE, and even then, it doesn't always help.
Any news on this ? Also, KDE4 doesn't use DCOP but DBUS. You were probably experiencing a different bug. Thanks
Marking as NEEDSINF
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 mark the bug 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!
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!