Bug 269600

Summary: nepomuk crashes when interupted
Product: nepomuk Reporter: Mark Rooks <rooksy>
Component: generalAssignee: Sebastian Trueg <sebastian>
Severity: crash CC: andresbajotierra, me
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Mark Rooks 2011-03-28 10:37:15 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.5.5 (KDE 4.5.5)
Qt Version: 4.7.1
Operating System: Linux i686
Distribution: "Fedora release 14 (Laughlin)"

-- Information about the crash:
- What I was doing when the application crashed:
I was doing an rsync -avr from an external usb HDD to an on board SATA HDD. 

I then opened a terminal and sudo'd to rm -r the directory that rsync was writing into.

Halfway thru the deletion process I issued CTRL-C  to the terminal running  rm -r.

That is when nepomuk seemed to crash.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault
[Current thread is 1 (Thread 0xb785d780 (LWP 3120))]

Thread 2 (Thread 0xb5657b70 (LWP 3128)):
#0  0x00c4f424 in __kernel_vsyscall ()
#1  0x003b639b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:169
#2  0x023ab567 in wait (this=0x9f82574, mutex=0x9f82570, time=4294967295) at thread/qwaitcondition_unix.cpp:88
#3  QWaitCondition::wait (this=0x9f82574, mutex=0x9f82570, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#4  0x08991c8c in Nepomuk::MetadataMover::run (this=0x9f82560) at /usr/src/debug/kdebase-runtime-4.5.5/nepomuk/services/filewatch/metadatamover.cpp:164
#5  0x023aae6a in QThreadPrivate::start (arg=0x9f82560) at thread/qthread_unix.cpp:285
#6  0x003b1e99 in start_thread (arg=0xb5657b70) at pthread_create.c:301
#7  0x002c4d2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 1 (Thread 0xb785d780 (LWP 3120)):
[KCrash Handler]
#7  0x024b7e96 in isSignalConnected (sender=0x9f89e90, m=0x89ab664, local_signal_index=4, argv=0xbfe37858) at kernel/qobject_p.h:220
#8  QMetaObject::activate (sender=0x9f89e90, m=0x89ab664, local_signal_index=4, argv=0xbfe37858) at kernel/qobject.cpp:3195
#9  0x08996894 in KInotify::created (this=0x9f89e90, _t1=...) at /usr/src/debug/kdebase-runtime-4.5.5/i686-redhat-linux-gnu/nepomuk/services/filewatch/kinotify.moc:159
#10 0x08997427 in KInotify::slotEvent (this=0x9f89e90, socket=15) at /usr/src/debug/kdebase-runtime-4.5.5/nepomuk/services/filewatch/kinotify.cpp:345
#11 0x08998d9f in KInotify::qt_metacall (this=0x9f89e90, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbfe37b68) at /usr/src/debug/kdebase-runtime-4.5.5/i686-redhat-linux-gnu/nepomuk/services/filewatch/kinotify.moc:118
#12 0x024a8beb in QMetaObject::metacall (object=0x9f89e90, cl=QMetaObject::InvokeMetaMethod, idx=18, argv=0xbfe37b68) at kernel/qmetaobject.cpp:237
#13 0x024b80c7 in QMetaObject::activate (sender=0x9f8e0e0, m=0x25dea70, local_signal_index=0, argv=0xbfe37b68) at kernel/qobject.cpp:3272
#14 0x025066a4 in QSocketNotifier::activated (this=0x9f8e0e0, _t1=15) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#15 0x024be8cf in QSocketNotifier::event (this=0x9f8e0e0, e=0xbfe37ff4) at kernel/qsocketnotifier.cpp:317
#16 0x02cdf26c in QApplicationPrivate::notify_helper (this=0x9ea8720, receiver=0x9f8e0e0, e=0xbfe37ff4) at kernel/qapplication.cpp:4445
#17 0x02ce3ed2 in QApplication::notify (this=0xbfe38418, receiver=0x9f8e0e0, e=0xbfe37ff4) at kernel/qapplication.cpp:3845
#18 0x0387cf7b in KApplication::notify (this=0xbfe38418, receiver=0x9f8e0e0, event=0xbfe37ff4) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#19 0x024a23b3 in QCoreApplication::notifyInternal (this=0xbfe38418, receiver=0x9f8e0e0, event=0xbfe37ff4) at kernel/qcoreapplication.cpp:732
#20 0x024cfa2f in sendEvent (source=0x9eab410) at kernel/qcoreapplication.h:215
#21 socketNotifierSourceDispatch (source=0x9eab410) at kernel/qeventdispatcher_glib.cpp:110
#22 0x005bb192 in g_main_dispatch (context=0x9eaaa90) at gmain.c:2149
#23 g_main_context_dispatch (context=0x9eaaa90) at gmain.c:2702
#24 0x005bb978 in g_main_context_iterate (context=0x9eaaa90, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#25 0x005bbc35 in g_main_context_iteration (context=0x9eaaa90, may_block=1) at gmain.c:2843
#26 0x024d00ad in QEventDispatcherGlib::processEvents (this=0x9e94170, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#27 0x02d92406 in QGuiEventDispatcherGlib::processEvents (this=0x9e94170, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#28 0x024a154a in QEventLoop::processEvents (this=0xbfe38274, flags=...) at kernel/qeventloop.cpp:149
#29 0x024a17fa in QEventLoop::exec (this=0xbfe38274, flags=...) at kernel/qeventloop.cpp:201
#30 0x024a63a7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#31 0x02cdd078 in QApplication::exec () at kernel/qapplication.cpp:3719
#32 0x0804b107 in main (argc=) at /usr/src/debug/kdebase-runtime-4.5.5/nepomuk/servicestub/main.cpp:165

This bug may be a duplicate of or related to bug 241723.

Possible duplicates by query: bug 267520, bug 252430, bug 244617, bug 243536, bug 241723.

Reported using DrKonqi
Comment 1 Dario Andres 2011-04-17 00:27:32 UTC
[Comment from a bug triager]
This issue is being tracked at bug 241723, merging.

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