Bug 315236 - Nepomuk crash after system boot and login
Summary: Nepomuk crash after system boot and login
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-15 21:12 UTC by Florian Brunner
Modified: 2013-02-15 21:32 UTC (History)
2 users (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 Florian Brunner 2013-02-15 21:12:49 UTC
Application: nepomukservicestub (0.1.0)
KDE Platform Version: 4.10.00
Qt Version: 4.8.3
Operating System: Linux 3.5.0-23-generic x86_64
Distribution: Ubuntu 12.10

-- Information about the crash:
- What I was doing when the application crashed:
I booted my system and logged in to my account.

No further user interaction.

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

Thread 2 (Thread 0x7f02274f4700 (LWP 2362)):
#0  0x00007f02365448bd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f02359ab15f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f023596e914 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f023596ed22 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f023596eea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f02389efc16 in QEventDispatcherGlib::processEvents (this=0x7f02200008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f02389c02bf in QEventLoop::processEvents (this=this@entry=0x7f02274f3dd0, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f02389c0548 in QEventLoop::exec (this=0x7f02274f3dd0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f02388c1b10 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x00007f02389a09af in QInotifyFileSystemWatcherEngine::run (this=0x226c650) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007f02388c4aec in QThreadPrivate::start (arg=0x226c650) at thread/qthread_unix.cpp:338
#11 0x00007f0236248e9a in start_thread (arg=0x7f02274f4700) at pthread_create.c:308
#12 0x00007f0236551cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f0230d59780 (LWP 2336)):
[KCrash Handler]
#6  0x00007f0236494425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f0236497b8b in __GI_abort () at abort.c:91
#8  0x00007f02364d239e in __libc_message (do_abort=2, fmt=0x7f02365d9e5f "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
#9  0x00007f023656882c in __GI___fortify_fail (msg=<optimized out>) at fortify_fail.c:38
#10 0x00007f0236567700 in __GI___chk_fail () at chk_fail.c:29
#11 0x00007f02365687be in __fdelt_chk (d=<optimized out>) at fdelt_chk.c:26
#12 0x00007f023899c854 in QProcessPrivate::waitForStarted (this=0x3742cb0, msecs=30000) at io/qprocess_unix.cpp:1038
#13 0x00007f0238956f53 in QProcess::waitForFinished (this=0x2651570, msecs=30000) at io/qprocess.cpp:1752
#14 0x00007f0227b25686 in ?? () from /usr/lib/kde4/nepomukfileindexer.so
#15 0x00007f02389d6f5f in QMetaObject::activate (sender=0x3718b50, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#16 0x00007f02389d626c in QObject::event (this=0x3718b50, e=<optimized out>) at kernel/qobject.cpp:1157
#17 0x00007f0236cebe9c in QApplicationPrivate::notify_helper (this=this@entry=0x20455a0, receiver=receiver@entry=0x3718b50, e=e@entry=0x7fffc9f233a0) at kernel/qapplication.cpp:4562
#18 0x00007f0236cf030a in QApplication::notify (this=0x7fffc9f23830, receiver=0x3718b50, e=0x7fffc9f233a0) at kernel/qapplication.cpp:4423
#19 0x00007f0237cf1636 in KApplication::notify (this=0x7fffc9f23830, receiver=0x3718b50, event=0x7fffc9f233a0) at ../../kdeui/kernel/kapplication.cpp:311
#20 0x00007f02389c156e in QCoreApplication::notifyInternal (this=0x7fffc9f23830, receiver=0x3718b50, event=0x7fffc9f233a0) at kernel/qcoreapplication.cpp:915
#21 0x00007f02389f2462 in sendEvent (event=0x7fffc9f233a0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#22 QTimerInfoList::activateTimers (this=0x2044060) at kernel/qeventdispatcher_unix.cpp:611
#23 0x00007f02389ef584 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#24 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#25 0x00007f023596eab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f023596ede8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f023596eea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f02389efc16 in QEventDispatcherGlib::processEvents (this=0x2019c20, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#29 0x00007f0236d90c1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x00007f02389c02bf in QEventLoop::processEvents (this=this@entry=0x7fffc9f23610, flags=...) at kernel/qeventloop.cpp:149
#31 0x00007f02389c0548 in QEventLoop::exec (this=0x7fffc9f23610, flags=...) at kernel/qeventloop.cpp:204
#32 0x00007f02389c5708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#33 0x0000000000403dd0 in ?? ()
#34 0x00007f023647f76d in __libc_start_main (main=0x4034d0, argc=2, ubp_av=0x7fffc9f23a78, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffc9f23a68) at libc-start.c:226
#35 0x00000000004040f1 in _start ()

Possible duplicates by query: bug 315194, bug 315184, bug 314986, bug 314257, bug 314085.

Reported using DrKonqi
Comment 1 Vishesh Handa 2013-02-15 21:32:45 UTC

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