Bug 188519 - SIGSEGV crash in kded for no reason
Summary: SIGSEGV crash in kded for no reason
Status: RESOLVED DUPLICATE of bug 165548
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-31 05:22 UTC by Joe Nahmias
Modified: 2009-03-31 07:06 UTC (History)
1 user (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 Joe Nahmias 2009-03-31 05:22:05 UTC
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Running KDE 4.2.1 as packaged in Debian; all of a sudden, for no apparent reason, I got the following crash:

Application: KDE Daemon (kded4), signal SIGSEGV

Thread 1 (Thread 0xb61a2700 (LWP 6254)):
[KCrash Handler]
#6  0xb7d0cf65 in QString::operator== (this=0x8d8d598, other=@0xbf9512cc) at ../../include/QtCore/../../src/corelib/tools/qstring.h:100
#7  0xb7561179 in KDirWatchPrivate::inotifyEventReceived (this=0x8cd0e78) at ../../kio/kio/kdirwatch.cpp:298
#8  0xb756145b in KDirWatchPrivate::qt_metacall (this=0x8cd0e78, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf95140c) at ./kdirwatch_p.moc:74
#9  0xb7dcfbe0 in QMetaObject::activate (sender=0x8ca3910, from_signal_index=4, to_signal_index=4, argv=0xbf95140c) at kernel/qobject.cpp:3031
#10 0xb7dd0962 in QMetaObject::activate (sender=0x8ca3910, m=0xb7e9e070, local_signal_index=0, argv=0xbf95140c) at kernel/qobject.cpp:3101
#11 0xb7e0a6f3 in QSocketNotifier::activated (this=0x8ca3910, _t1=10) at .moc/release-shared/moc_qsocketnotifier.cpp:81
#12 0xb7dd57b7 in QSocketNotifier::event (this=0x8ca3910, e=0xbf9517d0) at kernel/qsocketnotifier.cpp:320
#13 0xb6b0279c in QApplicationPrivate::notify_helper (this=0x8c04868, receiver=0x8ca3910, e=0xbf9517d0) at kernel/qapplication.cpp:3803
#14 0xb6b0a61e in QApplication::notify (this=0xbf951a8c, receiver=0x8ca3910, e=0xbf9517d0) at kernel/qapplication.cpp:3393
#15 0xb789a94d in KApplication::notify (this=0xbf951a8c, receiver=0x8ca3910, event=0xbf9517d0) at ../../kdeui/kernel/kapplication.cpp:307
#16 0xb7dbb0e1 in QCoreApplication::notifyInternal (this=0xbf951a8c, receiver=0x8ca3910, event=0xbf9517d0) at kernel/qcoreapplication.cpp:587
#17 0xb7de587a in socketNotifierSourceDispatch (source=0x8c0ab00) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209
#18 0xb6839718 in IA__g_main_context_dispatch (context=0x8c09e90) at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gmain.c:1814
#19 0xb683cc7b in g_main_context_iterate (context=0x8c09e90, block=1, dispatch=1, self=0x8bfdfd0) at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gmain.c:2448
#20 0xb683cdf8 in IA__g_main_context_iteration (context=0x8c09e90, may_block=1) at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gmain.c:2511
#21 0xb7de55e8 in QEventDispatcherGlib::processEvents (this=0x8c04938, flags={i = -1080747736}) at kernel/qeventdispatcher_glib.cpp:319
#22 0xb6b9bd75 in QGuiEventDispatcherGlib::processEvents (this=0x8c04938, flags={i = -1080747688}) at kernel/qguieventdispatcher_glib.cpp:198
#23 0xb7db97aa in QEventLoop::processEvents (this=0xbf9519d0, flags={i = -1080747624}) at kernel/qeventloop.cpp:143
#24 0xb7db996a in QEventLoop::exec (this=0xbf9519d0, flags={i = -1080747560}) at kernel/qeventloop.cpp:194
#25 0xb7dbc025 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#26 0xb6b02617 in QApplication::exec () at kernel/qapplication.cpp:3331
#27 0xb800cec0 in kdemain (argc=1, argv=0xbf951c94) at ../../kded/kded.cpp:937
#28 0x08048582 in main (argc=148956016, argv=0x720) at kded4_dummy.cpp:3
Comment 1 Christoph Feck 2009-03-31 07:06:36 UTC

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