Bug 262474 - nepomuk stub crashed
Summary: nepomuk stub crashed
Status: RESOLVED DUPLICATE of bug 241723
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-08 01:14 UTC by Mark Rooks
Modified: 2011-01-23 17:13 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 Mark Rooks 2011-01-08 01:14:33 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.5.4 (KDE 4.5.4)
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-66.fc13.i686.PAE i686
Distribution: "Fedora release 13 (Goddard)"

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

I had just opened Picasa, which indexed a lot of files as it had not been opened for a long time.

In picasa I selected "Create" --> "Picture Collage.."

At this point (within a blink of an eye), the bug reporting tool was instigated.

I tried to repeat two times unsuccessfully, but something changed as on the third time I tried to open the picasa programme, it also crashed.

I will update this bug after restarting X, the network, and then the whole machine. If the crash re-appears.

Cheers

Mark

The crash can be reproduced some of the time.

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

Thread 2 (Thread 0xb548cb70 (LWP 2632)):
#0  0x00a8f424 in __kernel_vsyscall ()
#1  0x00d3b22c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0x0553f6af in wait (this=0x91d71e4, mutex=0x91d71e0, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#3  QWaitCondition::wait (this=0x91d71e4, mutex=0x91d71e0, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#4  0x023e2812 in ?? () from /usr/lib/kde4/nepomukfilewatch.so
#5  0x0553e74f in QThreadPrivate::start (arg=0x91d71d0) at thread/qthread_unix.cpp:248
#6  0x00d37919 in start_thread () from /lib/libpthread.so.0
#7  0x00c4dd4e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb77e7780 (LWP 2620)):
[KCrash Handler]
#7  0x05643ceb in isSignalConnected (sender=0x91d5730, m=0x23fa6c4, local_signal_index=4, argv=0xbfe2add8) at kernel/qobject_p.h:227
#8  QMetaObject::activate (sender=0x91d5730, m=0x23fa6c4, local_signal_index=4, argv=0xbfe2add8) at kernel/qobject.cpp:3218
#9  0x023e5c44 in ?? () from /usr/lib/kde4/nepomukfilewatch.so
#10 0x023e7037 in ?? () from /usr/lib/kde4/nepomukfilewatch.so
#11 0x023e8f7d in ?? () from /usr/lib/kde4/nepomukfilewatch.so
#12 0x05634bcb in QMetaObject::metacall (object=0x91d5730, cl=QMetaObject::InvokeMetaMethod, idx=18, argv=0xbfe2b198) at kernel/qmetaobject.cpp:237
#13 0x05643a75 in QMetaObject::activate (sender=0x91d2948, m=0x57459f0, local_signal_index=0, argv=0xbfe2b198) at kernel/qobject.cpp:3295
#14 0x0568c794 in QSocketNotifier::activated (this=0x91d2948, _t1=13) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#15 0x0564905f in QSocketNotifier::event (this=0x91d2948, e=0xbfe2b624) at kernel/qsocketnotifier.cpp:317
#16 0x05eed77c in QApplicationPrivate::notify_helper (this=0x90f76f8, receiver=0x91d2948, e=0xbfe2b624) at kernel/qapplication.cpp:4306
#17 0x05ef41d6 in QApplication::notify (this=0xbfe2ba38, receiver=0x91d2948, e=0xbfe2b624) at kernel/qapplication.cpp:3710
#18 0x069d2a1b in KApplication::notify (this=0xbfe2ba38, receiver=0x91d2948, event=0xbfe2b624) at /usr/src/debug/kdelibs-4.5.4/kdeui/kernel/kapplication.cpp:310
#19 0x05630133 in QCoreApplication::notifyInternal (this=0xbfe2ba38, receiver=0x91d2948, event=0xbfe2b624) at kernel/qcoreapplication.cpp:726
#20 0x0565881a in sendEvent (source=0x90fa800) at kernel/qcoreapplication.h:215
#21 socketNotifierSourceDispatch (source=0x90fa800) at kernel/qeventdispatcher_glib.cpp:110
#22 0x00274525 in g_main_dispatch (context=0x90f9a90) at gmain.c:1960
#23 IA__g_main_context_dispatch (context=0x90f9a90) at gmain.c:2513
#24 0x00278268 in g_main_context_iterate (context=0xd3a490, block=1, dispatch=1, self=0x90f6f70) at gmain.c:2591
#25 0x00278449 in IA__g_main_context_iteration (context=0x90f9a90, may_block=1) at gmain.c:2654
#26 0x05658446 in QEventDispatcherGlib::processEvents (this=0x90e3170, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#27 0x05f9c336 in QGuiEventDispatcherGlib::processEvents (this=0x90e3170, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#28 0x0562e80a in QEventLoop::processEvents (this=0xbfe2b8c4, flags=...) at kernel/qeventloop.cpp:149
#29 0x0562eb4a in QEventLoop::exec (this=0xbfe2b8c4, flags=...) at kernel/qeventloop.cpp:201
#30 0x05632807 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#31 0x05eed828 in QApplication::exec () at kernel/qapplication.cpp:3585
#32 0x0804b07e in _start ()

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

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

Reported using DrKonqi
Comment 1 Dario Andres 2011-01-23 17:13:03 UTC
[Comment from a bug triager]
This is indeed very likely to be bug 241723. Merging. Thanks

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