Bug 288632

Summary: nepomouk crash when connecting a external harddisk
Product: [Unmaintained] nepomuk Reporter: willihope <willihope>
Component: generalAssignee: Sebastian Trueg <sebastian>
Status: RESOLVED DUPLICATE    
Severity: crash CC: me, trueg
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description willihope 2011-12-10 08:34:09 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-13-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

i connect a usb-harddisk und nepomuk crash contuniosly.
in the control modul the nepomuk service is running!?

The crash can be reproduced every time.

-- Backtrace:
Application: Nepomuk-Dienst (nepomukservicestub), signal: Aborted
[Current thread is 1 (Thread 0xb76f6710 (LWP 14996))]

Thread 3 (Thread 0xb650bb70 (LWP 14998)):
#0  0x00110416 in __kernel_vsyscall ()
#1  0x002dda5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x0395dcfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0x00d18cc0 in wait (time=4294967295, this=0x9abeeb0) at thread/qwaitcondition_unix.cpp:88
#4  QWaitCondition::wait (this=0x9abc524, mutex=0x9abc520, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#5  0x024fa62a in Nepomuk::MetadataMover::run (this=0x9abc510) at ../../../../nepomuk/services/filewatch/metadatamover.cpp:142
#6  0x00d187b3 in QThreadPrivate::start (arg=0x9abc510) at thread/qthread_unix.cpp:331
#7  0x002d9d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x039500ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 2 (Thread 0xb5d0ab70 (LWP 14999)):
#0  0x00110416 in __kernel_vsyscall ()
#1  0x0395e063 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0x038f2135 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb76f6710 (LWP 14996)):
[KCrash Handler]
#7  0x00110416 in __kernel_vsyscall ()
#8  0x038abc8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0x038af2b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0x038e1dfc in ?? () from /lib/i386-linux-gnu/libc.so.6
#11 0x038ecbc2 in ?? () from /lib/i386-linux-gnu/libc.so.6
#12 0x038eec45 in ?? () from /lib/i386-linux-gnu/libc.so.6
#13 0x038f0498 in malloc () from /lib/i386-linux-gnu/libc.so.6
#14 0x00d11e0b in qMalloc (size=40) at global/qmalloc.cpp:55
#15 0x00d1a95a in QByteArray::realloc (this=0xbfeada70, alloc=20) at tools/qbytearray.cpp:1428
#16 0x00d1ba72 in QByteArray::append (this=0xbfeada70, ch=47 '/') at tools/qbytearray.cpp:1660
#17 0x02500b3b in (anonymous namespace)::concatPath (p1=<optimized out>, p2=...) at ../../../../nepomuk/services/filewatch/kinotify.cpp:58
#18 0x02504b3b in addWatchesRecursively (path=..., this=0x9abf1c0) at ../../../../nepomuk/services/filewatch/kinotify.cpp:166
#19 KInotify::Private::_k_addWatches (this=0x9abf1c0) at ../../../../nepomuk/services/filewatch/kinotify.cpp:198
#20 0x02503e2f in KInotify::qt_metacall (this=0x9a704f0, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0x9ae09d8) at ./kinotify.moc:119
#21 0x00e19b7d in metacall (argv=0x9ae09d8, idx=19, cl=QMetaObject::InvokeMetaMethod, object=0x9a704f0) at kernel/qmetaobject.cpp:237
#22 QMetaObject::metacall (object=0x9a704f0, cl=QMetaObject::InvokeMetaMethod, idx=19, argv=0x9ae09d8) at kernel/qmetaobject.cpp:232
#23 0x00e24685 in QMetaCallEvent::placeMetaCall (this=0x9afc540, object=0x9a704f0) at kernel/qobject.cpp:535
#24 0x00e2bb52 in QObject::event (this=0x9a704f0, e=0x9afc540) at kernel/qobject.cpp:1217
#25 0x010a5d54 in notify_helper (e=0x9afc540, receiver=0x9a704f0, this=0x98f3580) at kernel/qapplication.cpp:4486
#26 QApplicationPrivate::notify_helper (this=0x98f3580, receiver=0x9a704f0, e=0x9afc540) at kernel/qapplication.cpp:4458
#27 0x010ab103 in QApplication::notify (this=0x9afc540, receiver=0x9a704f0, e=0x9afc540) at kernel/qapplication.cpp:3886
#28 0x00930681 in KApplication::notify (this=0xbfeae2e4, receiver=0x9a704f0, event=0x9afc540) at ../../kdeui/kernel/kapplication.cpp:311
#29 0x00e1319e in QCoreApplication::notifyInternal (this=0xbfeae2e4, receiver=0x9a704f0, event=0x9afc540) at kernel/qcoreapplication.cpp:787
#30 0x00e16f93 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x98dacb0) at kernel/qcoreapplication.cpp:1428
#32 0x00e170ec in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1321
#33 0x00e416a4 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#34 postEventSourceDispatch (s=0x98f4690) at kernel/qeventdispatcher_glib.cpp:277
#35 0x00bc525f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#36 0x00bc5990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#37 0x00bc5c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#38 0x00e41ada in QEventDispatcherGlib::processEvents (this=0x98db9d8, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#39 0x0115de3a in QGuiEventDispatcherGlib::processEvents (this=0x98db9d8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#40 0x00e121dd in QEventLoop::processEvents (this=0xbfeae154, flags=...) at kernel/qeventloop.cpp:149
#41 0x00e12421 in QEventLoop::exec (this=0xbfeae154, flags=...) at kernel/qeventloop.cpp:201
#42 0x00e1719d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#43 0x010a38f4 in QApplication::exec () at kernel/qapplication.cpp:3760
#44 0x0804ae35 in main (argc=) at ../../../nepomuk/servicestub/main.cpp:167

Possible duplicates by query: bug 284009, bug 282260, bug 267728, bug 264586.

Reported using DrKonqi
Comment 1 Sebastian Trueg 2011-12-12 10:06:50 UTC

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