Bug 314257 - nepomukservicestub crashes very regularly on two 4.9.98 systems
Summary: nepomukservicestub crashes very regularly on two 4.9.98 systems
Status: RESOLVED DUPLICATE of bug 310777
Alias: None
Product: nepomuk
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Nepomuk Bugs Coordination
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-01 16:58 UTC by Kenny Fairweather
Modified: 2013-02-08 00:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kenny Fairweather 2013-02-01 16:58:08 UTC
Application: nepomukservicestub (0.1.0)
KDE Platform Version: 4.9.98
Qt Version: 4.8.3
Operating System: Linux 3.5.0-22-generic x86_64
Distribution: Ubuntu 12.10

-- Information about the crash:
- What I was doing when the application crashed:
nepomukservicestub crashes regularly even when machines are idle (not on standby but no user interaction for a lengthy period).

The crash can be reproduced some of the time.

-- Backtrace:
Application: Nepomuk Service Stub (nepomukservicestub), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ffda5aa7780 (LWP 26775))]

Thread 2 (Thread 0x7ffd9c353700 (LWP 26776)):
#0  0x00007ffdab294303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007ffdaa6bcd84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffdaa6bcea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffdad73dc16 in QEventDispatcherGlib::processEvents (this=0x7ffd940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007ffdad70e2bf in QEventLoop::processEvents (this=this@entry=0x7ffd9c352dc0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffdad70e548 in QEventLoop::exec (this=0x7ffd9c352dc0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffdad60fb10 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007ffdad6f0478 in QDnotifySignalThread::run (this=0x251a450) at io/qfilesystemwatcher_dnotify.cpp:179
#8  0x00007ffdad612aec in QThreadPrivate::start (arg=0x251a450) at thread/qthread_unix.cpp:338
#9  0x00007ffdaaf96e9a in start_thread (arg=0x7ffd9c353700) at pthread_create.c:308
#10 0x00007ffdab29fcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ffda5aa7780 (LWP 26775)):
[KCrash Handler]
#6  0x00007ffdab1e2425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007ffdab1e5b8b in __GI_abort () at abort.c:91
#8  0x00007ffdab22039e in __libc_message (do_abort=2, fmt=0x7ffdab327e5f "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
#9  0x00007ffdab2b682c in __GI___fortify_fail (msg=<optimized out>) at fortify_fail.c:38
#10 0x00007ffdab2b5700 in __GI___chk_fail () at chk_fail.c:29
#11 0x00007ffdab2b67be in __fdelt_chk (d=<optimized out>) at fdelt_chk.c:26
#12 0x00007ffdad6ea854 in QProcessPrivate::waitForStarted (this=0x47588e0, msecs=30000) at io/qprocess_unix.cpp:1038
#13 0x00007ffdad6a4f53 in QProcess::waitForFinished (this=0x4750220, msecs=30000) at io/qprocess.cpp:1752
#14 0x00007ffd9c9846d6 in ?? () from /usr/lib/kde4/nepomukfileindexer.so
#15 0x00007ffdad724f5f in QMetaObject::activate (sender=0x45fae10, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#16 0x00007ffdad72426c in QObject::event (this=0x45fae10, e=<optimized out>) at kernel/qobject.cpp:1157
#17 0x00007ffdaba39e9c in QApplicationPrivate::notify_helper (this=this@entry=0x229c570, receiver=receiver@entry=0x45fae10, e=e@entry=0x7fffe5c535d0) at kernel/qapplication.cpp:4562
#18 0x00007ffdaba3e30a in QApplication::notify (this=0x7fffe5c53a60, receiver=0x45fae10, e=0x7fffe5c535d0) at kernel/qapplication.cpp:4423
#19 0x00007ffdaca3f636 in KApplication::notify (this=0x7fffe5c53a60, receiver=0x45fae10, event=0x7fffe5c535d0) at ../../kdeui/kernel/kapplication.cpp:311
#20 0x00007ffdad70f56e in QCoreApplication::notifyInternal (this=0x7fffe5c53a60, receiver=0x45fae10, event=0x7fffe5c535d0) at kernel/qcoreapplication.cpp:915
#21 0x00007ffdad740462 in sendEvent (event=0x7fffe5c535d0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#22 QTimerInfoList::activateTimers (this=0x22a8660) at kernel/qeventdispatcher_unix.cpp:611
#23 0x00007ffdad73d584 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#24 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#25 0x00007ffdaa6bcab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007ffdaa6bcde8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007ffdaa6bcea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007ffdad73dbf6 in QEventDispatcherGlib::processEvents (this=0x2278c20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#29 0x00007ffdabadec1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x00007ffdad70e2bf in QEventLoop::processEvents (this=this@entry=0x7fffe5c53840, flags=...) at kernel/qeventloop.cpp:149
#31 0x00007ffdad70e548 in QEventLoop::exec (this=0x7fffe5c53840, flags=...) at kernel/qeventloop.cpp:204
#32 0x00007ffdad713708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#33 0x0000000000403dd0 in ?? ()
#34 0x00007ffdab1cd76d in __libc_start_main (main=0x4034d0, argc=2, ubp_av=0x7fffe5c53ca8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffe5c53c98) at libc-start.c:226
#35 0x00000000004040f1 in _start ()

Possible duplicates by query: bug 314085, bug 313721, bug 313713, bug 313552, bug 313361.

Reported using DrKonqi
Comment 1 Christoph Feck 2013-02-08 00:31:09 UTC

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