Bug 187163 - kded crashed in inotify backend
Summary: kded crashed in inotify backend
Status: RESOLVED DUPLICATE of bug 165548
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: 4.2
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-14 17:36 UTC by Andrey Borzenkov
Modified: 2009-03-14 18:51 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 Andrey Borzenkov 2009-03-14 17:36:35 UTC
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    Mandriva RPMs

4.2.1/Qt4.5. There was no activity except RPM installation and kmail running in background. Next time I came to notebook I saw crash handler window.

Приложение: СлÑжба KDE (kded4), сигнал SIGSEGV
[Current thread is 1 (Thread 0xb60076d0 (LWP 4663))]

Thread 1 (Thread 0xb60076d0 (LWP 4663)):
[KCrash Handler]
#6  0xb7d5e788 in QString::operator== (this=0x890ff68, other=@0xbf8b1658) at ../../src/corelib/tools/qstring.h:104
#7  0xb74f9f72 in KDirWatchPrivate::inotifyEventReceived (this=0x887f820) at /usr/src/debug/kdelibs-4.2.1/kio/kio/kdirwatch.cpp:298
#8  0xb74fa608 in KDirWatchPrivate::qt_metacall (this=0x887f820, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf8b2790) at /usr/src/debug/kdelibs-4.2.1/build/kio/kdirwatch_p.moc:75
#9  0xb7e2a185 in QMetaObject::activate (sender=0x875d800, from_signal_index=4, to_signal_index=4, argv=0xbf8b2790) at kernel/qobject.cpp:3060
#10 0xb7e2ba25 in QMetaObject::activate (sender=0x875d800, m=0xb7f0a8b0, local_signal_index=0, argv=0xbf8b2790) at kernel/qobject.cpp:3134
#11 0xb7e66f25 in QSocketNotifier::activated (this=0x875d800, _t1=9) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#12 0xb7e2f05f in QSocketNotifier::event (this=0x875d800, e=0xbf8b2b20) at kernel/qsocketnotifier.cpp:316
#13 0xb697c27c in QApplicationPrivate::notify_helper (this=0x876b3f0, receiver=0x875d800, e=0xbf8b2b20) at kernel/qapplication.cpp:4084
#14 0xb69849b6 in QApplication::notify (this=0xbf8b2da4, receiver=0x875d800, e=0xbf8b2b20) at kernel/qapplication.cpp:3631
#15 0xb7852620 in KApplication::notify (this=0xbf8b2da4, receiver=0x875d800, event=0xbf8b2b20) at /usr/src/debug/kdelibs-4.2.1/kdeui/kernel/kapplication.cpp:307
#16 0xb7e1367e in QCoreApplication::notifyInternal (this=0xbf8b2da4, receiver=0x875d800, event=0xbf8b2b20) at kernel/qcoreapplication.cpp:602
#17 0xb7e407c8 in socketNotifierSourceDispatch (source=0x876ef68) at kernel/qcoreapplication.h:213
#18 0xb66acc0a in IA__g_main_context_dispatch (context=0x876ce60) at gmain.c:1814
#19 0xb66b0274 in g_main_context_iterate (context=0x876ce60, block=1, dispatch=1, self=0x876b520) at gmain.c:2448
#20 0xb66b03ff in IA__g_main_context_iteration (context=0x876ce60, may_block=1) at gmain.c:2511
#21 0xb7e4051a in QEventDispatcherGlib::processEvents (this=0x876b3d0, flags={i = -1081398168}) at kernel/qeventdispatcher_glib.cpp:323
#22 0xb6a2075a in QGuiEventDispatcherGlib::processEvents (this=0x876b3d0, flags={i = -1081398120}) at kernel/qguieventdispatcher_glib.cpp:202
#23 0xb7e11c43 in QEventLoop::processEvents (this=0xbf8b2d10, flags={i = -1081398056}) at kernel/qeventloop.cpp:149
#24 0xb7e12091 in QEventLoop::exec (this=0xbf8b2d10, flags={i = -1081397992}) at kernel/qeventloop.cpp:200
#25 0xb7e145f6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#26 0xb697c0e4 in QApplication::exec () at kernel/qapplication.cpp:3553
#27 0xb8068cf9 in kdemain (argc=1, argv=0xbf8b2ef4) at /usr/src/debug/kdelibs-4.2.1/kded/kded.cpp:937
#28 0x0804856f in main (argc=143451800, argv=0x50) at /usr/src/debug/kdelibs-4.2.1/build/kded/kded4_dummy.cpp:3
Comment 1 Frank Reininghaus 2009-03-14 18:51:32 UTC
Thanks for the bug report! This issue is known already, I'll mark it as a duplicate.

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