Bug 202416 - kded4 crash kded broken
Summary: kded4 crash kded broken
Status: RESOLVED DUPLICATE of bug 190394
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-03 18:44 UTC by Chris Hills
Modified: 2009-08-04 02:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Hills 2009-08-03 18:44:50 UTC
Application that crashed: kded4
Version of the application: $Id: kded.cpp 944898 2009-03-26 13:01:25Z dfaure $
KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3)) "release 150"
Qt Version: 4.5.2
Operating System: Linux 2.6.30-53-default i686

 -- Backtrace:
Application: KDE Daemon (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5f6c700 (LWP 21850))]

Thread 2 (Thread 0xaeac7b90 (LWP 21988)):
#0  0xb653f3da in clock_gettime () from /lib/librt.so.1
#1  0xb7f6d62b in QTimerInfoList::getTime (this=0x821109c, t=@0x82110c0) at kernel/qeventdispatcher_unix.cpp:339
#2  0xb7f6d801 in QTimerInfoList::updateCurrentTime (this=0x821109c) at kernel/qeventdispatcher_unix.cpp:297
#3  0xb7f6f02c in QTimerInfoList::timerWait (this=0x821109c, tm=@0xaeac7134) at kernel/qeventdispatcher_unix.cpp:420
#4  0xb7f6bab8 in timerSourcePrepare (source=0xb6543ff4, timeout=0xaeac7188) at kernel/qeventdispatcher_glib.cpp:141
#5  0xb64b28da in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#6  0xb64b2d6a in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb64b3241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#8  0xb7f6b8f7 in QEventDispatcherGlib::processEvents (this=0x82497e0, flags={i = -1364430216}) at kernel/qeventdispatcher_glib.cpp:329
#9  0xb7f3e78a in QEventLoop::processEvents (this=0xaeac72f0, flags={i = -1364430152}) at kernel/qeventloop.cpp:149
#10 0xb7f3ebd2 in QEventLoop::exec (this=0xaeac72f0, flags={i = -1364430088}) at kernel/qeventloop.cpp:201
#11 0xb7e48229 in QThread::exec (this=0x8252360) at thread/qthread.cpp:487
#12 0xb7f2155b in QInotifyFileSystemWatcherEngine::run (this=0x8252360) at io/qfilesystemwatcher_inotify.cpp:214
#13 0xb7e4b572 in QThreadPrivate::start (arg=0x8252360) at thread/qthread_unix.cpp:188
#14 0xb7de91b5 in start_thread () from /lib/libpthread.so.0
#15 0xb66323be in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5f6c700 (LWP 21850)):
[KCrash Handler]
#6  KCookieJar::setDomainAdvice (this=0x8178f38, _domain=@0x8118ecc, _advice=KCookieAccept) at /usr/include/QtCore/qatomic_i386.h:120
#7  0xae2b5389 in KCookieServer::setDomainAdvice (this=0x825d058, url=@0x8218890, advice=@0x81ee600) at /usr/src/debug/kdelibs-4.2.98/kioslave/http/kcookiejar/kcookieserver.cpp:509
#8  0xae2bf807 in KCookieServerAdaptor::qt_metacall (this=0x81f8990, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbfa1ea7c)
    at /usr/src/debug/kdelibs-4.2.98/build/kioslave/http/kcookiejar/kcookieserveradaptor.cpp:129
#9  0xb71ec873 in QDBusConnectionPrivate::deliverCall (this=0x8097f70, object=0x81f8990, msg=@0x82109a0, metaTypes=@0xbfa1eb38, slotIdx=19) at qdbusintegrator.cpp:891
#10 0xb71ed832 in QDBusConnectionPrivate::activateCall (this=0x8097f70, object=0x81f8990, flags=497, msg=@0x82109a0) at qdbusintegrator.cpp:796
#11 0xb71edda1 in QDBusConnectionPrivate::activateObject (this=0x8097f70, node=@0x821098c, msg=@0x82109a0, pathStartPos=19) at qdbusintegrator.cpp:1370
#12 0xb71ee29a in QDBusActivateObjectEvent::placeMetaCall (this=0x8210960) at qdbusintegrator.cpp:1464
#13 0xb7f50970 in QObject::event (this=0x825d058, e=0x8210960) at kernel/qobject.cpp:1111
#14 0xb690a7fc in QApplicationPrivate::notify_helper (this=0x80941a8, receiver=0x825d058, e=0x8210960) at kernel/qapplication.cpp:4056
#15 0xb6912aee in QApplication::notify (this=0xbfa1f33c, receiver=0x825d058, e=0x8210960) at kernel/qapplication.cpp:3603
#16 0xb73fc27d in KApplication::notify (this=0xbfa1f33c, receiver=0x825d058, event=0x8210960) at /usr/src/debug/kdelibs-4.2.98/kdeui/kernel/kapplication.cpp:302
#17 0xb7f4016b in QCoreApplication::notifyInternal (this=0xbfa1f33c, receiver=0x825d058, event=0x8210960) at kernel/qcoreapplication.cpp:610
#18 0xb7f40db5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x805a5a0) at kernel/qcoreapplication.h:213
#19 0xb7f40fad in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#20 0xb7f6bc8f in postEventSourceDispatch (s=0x8096310) at kernel/qcoreapplication.h:218
#21 0xb64af9c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb64b3083 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb64b3241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb7f6b8d8 in QEventDispatcherGlib::processEvents (this=0x805c028, flags={i = -1079905832}) at kernel/qeventdispatcher_glib.cpp:327
#25 0xb69aace5 in QGuiEventDispatcherGlib::processEvents (this=0x805c028, flags={i = -1079905784}) at kernel/qguieventdispatcher_glib.cpp:202
#26 0xb7f3e78a in QEventLoop::processEvents (this=0xbfa1f280, flags={i = -1079905720}) at kernel/qeventloop.cpp:149
#27 0xb7f3ebd2 in QEventLoop::exec (this=0xbfa1f280, flags={i = -1079905656}) at kernel/qeventloop.cpp:201
#28 0xb7f41079 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0xb690a677 in QApplication::exec () at kernel/qapplication.cpp:3525
#30 0xb5c1dda0 in kdemain (argc=1, argv=0x8089908) at /usr/src/debug/kdelibs-4.2.98/kded/kded.cpp:938
#31 0x0804e505 in launch (argc=1, _name=0x8051775 "kded4", args=0x0, cwd=0x0, envc=0, envs=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8051649 "0")
    at /usr/src/debug/kdelibs-4.2.98/kinit/kinit.cpp:705
#32 0x080500dd in main (argc=4, argv=0xbfa1fa54, envp=0xbfa1fa68) at /usr/src/debug/kdelibs-4.2.98/kinit/kinit.cpp:1768

This bug may be a duplicate of or related to bug 198454

Reported using DrKonqi
Comment 1 Chris Hills 2009-08-03 18:47:31 UTC
Sorry for the useless bug title. I thought it was going to be posted along with the related bug, not a new bug, and I cannot figure out how to change it.
Comment 2 Chris Hills 2009-08-03 18:48:44 UTC
After looking in more depth at the other bug, it does not appear to be related.
Comment 3 Dario Andres 2009-08-04 02:23:15 UTC
This is reported at bug 190394, and fixed already. Thanks

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