Bug 192963

Summary: kded crashed suddenly
Product: [Unmaintained] kdelibs Reporter: Anselmo L. S. Melo (anselmolsm) <anselmolsm>
Component: kdedAssignee: David Faure <faure>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: kded4 crash backtrace

Description Anselmo L. S. Melo (anselmolsm) 2009-05-17 05:54:38 UTC
Application that crashed: kded4
Version of the application: $Id: kded.cpp 944898 2009-03-26 13:01:25Z dfaure $
KDE Version: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514))
Qt Version: 4.5.1
Operating System: Linux 2.6.29-tuxonice-r1 i686

 -- Backtrace:
Application: KDE Daemon (kdeinit), signal: Segmentation fault
[KCrash Handler]
#6  0xb7eeb236 in qHash (key=@0xbfe785c8) at tools/qhash.cpp:84
#7  0xb1dedbf0 in QHash<QString, KHttpCookieList*>::findNode (this=0x8d9c098, akey=@0xbfe785c8, ahp=0x0) at /usr/include/qt4/QtCore/qhash.h:858
#8  0xb1de6b45 in KCookieJar::setDomainAdvice (this=0x8d9c090, _domain=@0x888e844, _advice=KCookieAccept) at /usr/include/qt4/QtCore/qhash.h:592
#9  0xb1defbff in KCookieServer::setDomainAdvice (this=0x8a9c610, url=@0x8d8e158, advice=@0x8a4c7d0)
    at /var/tmp/portage/kde-base/kdelibs-9999-r1/work/kdelibs-9999/kioslave/http/kcookiejar/kcookieserver.cpp:509
#10 0xb1dfa05f in KCookieServerAdaptor::qt_metacall (this=0x890ec00, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbfe78720)
    at /var/tmp/portage/kde-base/kdelibs-9999-r1/work/kdelibs-9999_build/kioslave/http/kcookiejar/kcookieserveradaptor.cpp:129
#11 0xb734bed7 in QDBusConnectionPrivate::deliverCall (this=0x8845990, object=0x890ec00, msg=@0x8e31520, metaTypes=@0xbfe78858, slotIdx=19) at qdbusintegrator.cpp:891
#12 0xb734cc51 in QDBusConnectionPrivate::activateCall (this=0x8845990, object=0x890ec00, flags=497, msg=@0x8e31520) at qdbusintegrator.cpp:796
#13 0xb734d017 in QDBusConnectionPrivate::activateObject (this=0x8845990, node=@0x8e3150c, msg=@0x8e31520, pathStartPos=19) at qdbusintegrator.cpp:1375
#14 0xb734d4ba in QDBusActivateObjectEvent::placeMetaCall (this=0x8e314e0) at qdbusintegrator.cpp:1469
#15 0xb7fbc450 in QObject::event (this=0x8a9c610, e=0x8e314e0) at kernel/qobject.cpp:1115
#16 0xb6bf655c in QApplicationPrivate::notify_helper (this=0x8871518, receiver=0x8a9c610, e=0x8e314e0) at kernel/qapplication.cpp:4057
#17 0xb6bff053 in QApplication::notify (this=0xbfe7903c, receiver=0x8a9c610, e=0x8e314e0) at kernel/qapplication.cpp:3604
#18 0xb754bfce in KApplication::notify (this=0xbfe7903c, receiver=0x8a9c610, event=0x8e314e0) at /var/tmp/portage/kde-base/kdelibs-9999-r1/work/kdelibs-9999/kdeui/kernel/kapplication.cpp:307
#19 0xb7facc02 in QCoreApplication::notifyInternal (this=0xbfe7903c, receiver=0x8a9c610, event=0x8e314e0) at kernel/qcoreapplication.cpp:606
#20 0xb7fad542 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x87fda00) at kernel/qcoreapplication.h:213
#21 0xb7fad6de in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#22 0xb7fd4e40 in postEventSourceDispatch (s=0x8873700) at kernel/qcoreapplication.h:218
#23 0xb67ac95b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0x0887367c in ?? ()
#25 0x08873700 in ?? ()
#26 0xb684b398 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0xb684b3c0 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0xb7fd4e10 in ?? () from /usr/lib/qt4/libQtCore.so.4
#29 0x00000000 in ?? ()
Comment 1 Anselmo L. S. Melo (anselmolsm) 2009-05-17 13:49:33 UTC
Created attachment 33761 [details]
kded4 crash backtrace
Comment 2 Anselmo L. S. Melo (anselmolsm) 2009-05-17 13:51:41 UTC
The backtrace in #1 contains glib debug errors. The bug has just happened again and now I can provide what I was doing. In Konqueror, I selected the menu Tools -> HTML Settings, then kded4 crashed.
Comment 3 Dario Andres 2009-05-17 16:12:25 UTC
This looks like bug 190394
Comment 4 Christoph Feck 2009-07-22 17:48:49 UTC

*** This bug has been marked as a duplicate of bug 190394 ***