Bug 315733 - nepomukservicestub crash upon resume
Summary: nepomukservicestub crash upon resume
Status: RESOLVED DUPLICATE of bug 310777
Alias: None
Product: nepomuk
Classification: Miscellaneous
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-24 23:01 UTC by Jason Dobson
Modified: 2013-02-25 01:07 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 Jason Dobson 2013-02-24 23:01:09 UTC
Application: nepomukservicestub (0.1.0)
KDE Platform Version: 4.10.00
Qt Version: 4.8.2
Operating System: Linux 3.2.0-38-generic x86_64
Distribution: Ubuntu 12.04.2 LTS

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

Resuming from sleep/suspend on a desktop machine, almost every time this nepomukservicestub crash occurs.

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 0x7fb056842780 (LWP 3066))]

Thread 2 (Thread 0x7fb044ae3700 (LWP 3072)):
#0  0x00007fb053e1f303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fb05324a036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fb05324a164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fb05633a926 in QEventDispatcherGlib::processEvents (this=0x7fb0400008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007fb056309e62 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fb05630a0b7 in QEventLoop::exec (this=0x7fb044ae2dd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fb056209077 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007fb0562e9b6f in QInotifyFileSystemWatcherEngine::run (this=0xec3e00) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fb05620c09b in QThreadPrivate::start (arg=0xec3e00) at thread/qthread_unix.cpp:307
#9  0x00007fb053b21e9a in start_thread (arg=0x7fb044ae3700) at pthread_create.c:308
#10 0x00007fb053e2acbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fb056842780 (LWP 3066)):
[KCrash Handler]
#6  0x00007fb053d6d425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fb053d70b8b in __GI_abort () at abort.c:91
#8  0x00007fb053dab39e in __libc_message (do_abort=2, fmt=0x7fb053eb2e3f "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
#9  0x00007fb053e41807 in __GI___fortify_fail (msg=0x7fb053eb2dd6 "buffer overflow detected") at fortify_fail.c:32
#10 0x00007fb053e40700 in __GI___chk_fail () at chk_fail.c:29
#11 0x00007fb053e417be in __fdelt_chk (d=<optimized out>) at fdelt_chk.c:26
#12 0x00007fb0562e5644 in QProcessPrivate::waitForStarted (this=0x3192fd0, msecs=30000) at io/qprocess_unix.cpp:1038
#13 0x00007fb0562a0663 in QProcess::waitForFinished (this=0x30744e0, msecs=30000) at io/qprocess.cpp:1752
#14 0x00007fb045114db6 in ?? () from /usr/lib/kde4/nepomukfileindexer.so
#15 0x00007fb05631f781 in QMetaObject::activate (sender=0x2f3d680, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#16 0x00007fb056324679 in QObject::event (this=0x2f3d680, e=<optimized out>) at kernel/qobject.cpp:1157
#17 0x00007fb0545c17b4 in notify_helper (e=0x7fffc20ec620, receiver=0x2f3d680, this=0xc5e2c0) at kernel/qapplication.cpp:4556
#18 QApplicationPrivate::notify_helper (this=0xc5e2c0, receiver=0x2f3d680, e=0x7fffc20ec620) at kernel/qapplication.cpp:4528
#19 0x00007fb0545c6583 in QApplication::notify (this=0x7fffc20eca10, receiver=0x2f3d680, e=0x7fffc20ec620) at kernel/qapplication.cpp:4417
#20 0x00007fb055606b76 in KApplication::notify (this=0x7fffc20eca10, receiver=0x2f3d680, event=0x7fffc20ec620) at ../../kdeui/kernel/kapplication.cpp:311
#21 0x00007fb05630b32c in QCoreApplication::notifyInternal (this=0x7fffc20eca10, receiver=0x2f3d680, event=0x7fffc20ec620) at kernel/qcoreapplication.cpp:915
#22 0x00007fb05633c6f2 in sendEvent (event=0x7fffc20ec620, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#23 QTimerInfoList::activateTimers (this=0xc5b550) at kernel/qeventdispatcher_unix.cpp:611
#24 0x00007fb05633a10d in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#25 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#26 0x00007fb053249d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007fb05324a0a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007fb05324a164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007fb05633a8bf in QEventDispatcherGlib::processEvents (this=0xc2ac20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#30 0x00007fb054669cde in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x00007fb056309e62 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#32 0x00007fb05630a0b7 in QEventLoop::exec (this=0x7fffc20ec880, flags=...) at kernel/qeventloop.cpp:204
#33 0x00007fb05630f407 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#34 0x0000000000403de0 in ?? ()
#35 0x00007fb053d5876d in __libc_start_main (main=0x403470, argc=2, ubp_av=0x7fffc20eced8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffc20ecec8) at libc-start.c:226
#36 0x0000000000404109 in _start ()

Possible duplicates by query: bug 315589, bug 315532, bug 315342, bug 315257, bug 315236.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-02-25 01:07:13 UTC

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