Bug 265137

Summary:	Nepomuk Service Stub segfault in Nepomuk::MetadataMover::run
Product:	[Unmaintained] nepomuk	Reporter:	Martin Nyhus <bugs.kde.org>
Component:	filewatch	Assignee:	Sebastian Trueg <sebastian>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	me, trueg
Priority:	NOR
Version First Reported In:	4.5
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Martin Nyhus 2011-02-01 22:45:13 UTC

Application: nepomukservicestub (0.2)
KDE Platform Version: 4.5.5 (KDE 4.5.5)
Qt Version: 4.7.1
Operating System: Linux 2.6.35.10-74.fc14.x86_64 x86_64
Distribution: "Fedora release 14 (Laughlin)"

-- Information about the crash:
- What I was doing when the application crashed:
Switched to a virtual desktop with Dolphin on it, while the system was extremely unresponsive due to swapping

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

Thread 2 (Thread 0x7f7ae397e700 (LWP 2154)):
#0  0x0000003c38c0b8c4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x0000003752e72ddb in wait (this=<value optimized out>, mutex=0xae1280, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0xae1280, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00007f7ae398afe1 in Nepomuk::MetadataMover::run (this=0xae1260) at /usr/src/debug/kdebase-runtime-4.5.5/nepomuk/services/filewatch/metadatamover.cpp:164
#4  0x0000003752e726ee in QThreadPrivate::start (arg=0xae1260) at thread/qthread_unix.cpp:285
#5  0x0000003c38c06d5b in start_thread () from /lib64/libpthread.so.0
#6  0x0000003c380e4a7d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7aeefd4840 (LWP 2118)):
[KCrash Handler]
#6  count (sender=0xae5510, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff7d900da0) at ../../src/corelib/tools/qvector.h:246
#7  QMetaObject::activate (sender=0xae5510, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff7d900da0) at kernel/qobject.cpp:3220
#8  0x00007f7ae398f175 in KInotify::created (this=<value optimized out>, _t1=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.5.5/x86_64-redhat-linux-gnu/nepomuk/services/filewatch/kinotify.moc:159
#9  0x00007f7ae398fb40 in KInotify::slotEvent (this=0xae5510, socket=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.5.5/nepomuk/services/filewatch/kinotify.cpp:345
#10 0x00007f7ae39910af in KInotify::qt_metacall (this=0xae5510, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x7fff7d901360) at /usr/src/debug/kdebase-runtime-4.5.5/x86_64-redhat-linux-gnu/nepomuk/services/filewatch/kinotify.moc:118
#11 0x0000003752f7004f in QMetaObject::activate (sender=0xae97c0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff7d901360) at kernel/qobject.cpp:3272
#12 0x0000003752fb882e in QSocketNotifier::activated (this=<value optimized out>, _t1=13) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#13 0x0000003752f766cb in QSocketNotifier::event (this=0xae97c0, e=0x7fff7d901a10) at kernel/qsocketnotifier.cpp:317
#14 0x0000003060db78c4 in QApplicationPrivate::notify_helper (this=0x9b8470, receiver=0xae97c0, e=0x7fff7d901a10) at kernel/qapplication.cpp:4445
#15 0x0000003060dbc3da in QApplication::notify (this=<value optimized out>, receiver=0xae97c0, e=0x7fff7d901a10) at kernel/qapplication.cpp:4324
#16 0x0000003062420596 in KApplication::notify (this=0x7fff7d901e80, receiver=0xae97c0, event=0x7fff7d901a10) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#17 0x0000003752f5b7ac in QCoreApplication::notifyInternal (this=0x7fff7d901e80, receiver=0xae97c0, event=0x7fff7d901a10) at kernel/qcoreapplication.cpp:732
#18 0x0000003752f86289 in sendEvent (source=0x9bc0a0) at kernel/qcoreapplication.h:215
#19 socketNotifierSourceDispatch (source=0x9bc0a0) at kernel/qeventdispatcher_glib.cpp:110
#20 0x0000003c3a041e33 in g_main_dispatch (context=0x9bb120) at gmain.c:2149
#21 g_main_context_dispatch (context=0x9bb120) at gmain.c:2702
#22 0x0000003c3a042610 in g_main_context_iterate (context=0x9bb120, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#23 0x0000003c3a0428ad in g_main_context_iteration (context=0x9bb120, may_block=1) at gmain.c:2843
#24 0x0000003752f868bf in QEventDispatcherGlib::processEvents (this=0x9a0fb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#25 0x0000003060e5c59e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:207
#26 0x0000003752f5ab42 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x0000003752f5ad8c in QEventLoop::exec (this=0x7fff7d901c50, flags=...) at kernel/qeventloop.cpp:201
#28 0x0000003752f5f24b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#29 0x0000000000403c32 in main (argc=2, argv=0x7fff7d9022d8) 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 263180.

Reported using DrKonqi

Comment 1 Sebastian Trueg 2011-09-19 08:54:31 UTC

is this still reproducible with kde 4.7?

Comment 2 Vishesh Handa 2012-07-24 11:34:12 UTC

Marking as RESOLVED -> INVALID.

The KDE version is really old, and the code base has changed substantially.