Bug 314712 - Nepomuk crashed when logging in.
Summary: Nepomuk crashed when logging in.
Status: RESOLVED FIXED
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:
: 314754 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-02-08 20:38 UTC by Benoit Leffray
Modified: 2013-02-12 07:26 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benoit Leffray 2013-02-08 20:38:47 UTC
Application: nepomukservicestub (0.1.0)
KDE Platform Version: 4.10.00
Qt Version: 4.8.3
Operating System: Linux 3.5.0-24-generic x86_64
Distribution: Ubuntu 12.10

-- Information about the crash:
- What I was doing when the application crashed:
I had launched an software update which required to reboot the PC.
So did I, and then I saw this as I logged in again.

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

Thread 2 (Thread 0x7f27f18e3700 (LWP 3013)):
#0  0x00007f2802f32313 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f280235ad84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f280235b1e2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f27f823d4a6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007f280237e645 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f2802c34e9a in start_thread (arg=0x7f27f18e3700) at pthread_create.c:308
#6  0x00007f2802f3dccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f27fd745780 (LWP 3002)):
[KCrash Handler]
#6  Nepomuk2::IndexingQueue::suspend (this=0x6c) at ../../../services/fileindexer/indexingqueue.cpp:61
#7  0x00007f27e33bf48d in Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x172a680) at ../../../services/fileindexer/indexscheduler.cpp:389
#8  0x00007f27e33c0c9c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x172a680) at ../../../services/fileindexer/indexscheduler.cpp:234
#9  0x00007f27e33c0fd5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#10 Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
#11 0x00007f28053c2f5f in QMetaObject::activate (sender=0x17b3f60, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff4766e390) at kernel/qobject.cpp:3547
#12 0x00007f2804c1fd2f in KJob::finished (this=this@entry=0x17b3f60, _t1=_t1@entry=0x17b3f60) at ./kjob.moc:187
#13 0x00007f2804c1ff75 in KJob::emitResult (this=0x17b3f60) at ../../kdecore/jobs/kjob.cpp:316
#14 0x00007f27e33c513b in Nepomuk2::IndexCleaner::clearNextBatch (this=this@entry=0x17b3f60) at ../../../services/fileindexer/indexcleaner.cpp:295
#15 0x00007f27e33c72c3 in Nepomuk2::IndexCleaner::start (this=0x17b3f60) at ../../../services/fileindexer/indexcleaner.cpp:253
#16 0x00007f27e33bf7f7 in Nepomuk2::IndexScheduler::IndexScheduler (this=0x172a680, parent=<optimized out>) at ../../../services/fileindexer/indexscheduler.cpp:56
#17 0x00007f27e33bdba7 in Nepomuk2::FileIndexer::FileIndexer (this=0x177a410, parent=<optimized out>) at ../../../services/fileindexer/fileindexer.cpp:43
#18 0x00007f27e33bf017 in KPluginFactory::createInstance<Nepomuk2::FileIndexer, QObject> (parentWidget=<optimized out>, parent=<optimized out>, args=...) at /usr/include/kpluginfactory.h:477
#19 0x00007f2804cfef65 in KPluginFactory::create (this=0x16c4b50, iface=0x7f280427abe0 <qt_meta_stringdata_Nepomuk2__Service> "Nepomuk2::Service", parentWidget=0x0, parent=0x16e4770, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:203
#20 0x0000000000404c93 in create<Nepomuk2::Service> (args=..., keyword=..., parent=0x16e4770, parentWidget=0x0, this=0x16c4b50) at /usr/include/kpluginfactory.h:531
#21 createInstance<Nepomuk2::Service> (error=0x7fff4766e950, args=..., parent=0x16e4770, parentWidget=0x0, this=0x16c2180) at /usr/include/KDE/../kservice.h:559
#22 createInstance<Nepomuk2::Service> (error=0x7fff4766e950, args=..., parent=0x16e4770, this=0x16c2180) at /usr/include/KDE/../kservice.h:536
#23 Nepomuk2::ServiceControl::start (this=0x16e4770) at ../../servicestub/servicecontrol.cpp:92
#24 0x000000000040529d in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./servicecontrol.moc:62
#25 Nepomuk2::ServiceControl::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./servicecontrol.moc:55
#26 0x00007f28053c243e in QObject::event (this=0x16e4770, e=<optimized out>) at kernel/qobject.cpp:1195
#27 0x00007f28036d7e9c in QApplicationPrivate::notify_helper (this=this@entry=0x1388a30, receiver=receiver@entry=0x16e4770, e=e@entry=0x16c0f60) at kernel/qapplication.cpp:4562
#28 0x00007f28036dc30a in QApplication::notify (this=0x7fff4766f5a0, receiver=0x16e4770, e=0x16c0f60) at kernel/qapplication.cpp:4423
#29 0x00007f28046dd636 in KApplication::notify (this=0x7fff4766f5a0, receiver=0x16e4770, event=0x16c0f60) at ../../kdeui/kernel/kapplication.cpp:311
#30 0x00007f28053ad56e in QCoreApplication::notifyInternal (this=0x7fff4766f5a0, receiver=receiver@entry=0x16e4770, event=event@entry=0x16c0f60) at kernel/qcoreapplication.cpp:915
#31 0x00007f28053b13f1 in sendEvent (event=0x16c0f60, receiver=0x16e4770) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#32 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x13632f0) at kernel/qcoreapplication.cpp:1539
#33 0x00007f28053dba63 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#34 postEventSourceDispatch (s=0x13954d0) at kernel/qeventdispatcher_glib.cpp:279
#35 0x00007f280235aab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007f280235ade8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007f280235aea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#38 0x00007f28053dbbf6 in QEventDispatcherGlib::processEvents (this=0x13892e0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#39 0x00007f280377cc1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#40 0x00007f28053ac2bf in QEventLoop::processEvents (this=this@entry=0x7fff4766f380, flags=...) at kernel/qeventloop.cpp:149
#41 0x00007f28053ac548 in QEventLoop::exec (this=0x7fff4766f380, flags=...) at kernel/qeventloop.cpp:204
#42 0x00007f28053b1708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#43 0x0000000000403dd0 in main (argc=<optimized out>, argv=0x7fff4766f7e8) at ../../servicestub/main.cpp:180

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

Possible duplicates by query: bug 314556.

Reported using DrKonqi
Comment 1 Simeon Bird 2013-02-12 02:57:31 UTC
*** Bug 314754 has been marked as a duplicate of this bug. ***
Comment 2 Simeon Bird 2013-02-12 07:07:39 UTC
This appears to be a crash when setting a member variable of m_basicIQ - perhaps due to some sort of memory corruption?

I find it a bit suspicious that in both duplicates, the pointer to m_basicIQ is set to the same value, (0x6c).

All I can find that is significant about that is that in decimal 0x6c == 108, the value of UNIX_PATH_MAX.
Comment 3 Simeon Bird 2013-02-12 07:25:35 UTC
Ah, no - it is calling Nepomuk2::IndexCleaner::start at line 56 of ./../../services/fileindexer/indexscheduler.cpp, which means it is the bug that was fixed by commit: 

commit b94e9f73bd86593928988e5626511acea805b7be
Author: Edward Toroshchin <kde@hades.name>
Date:   Sun Feb 3 17:57:23 2013 +0100

    fileindexer: initialize objects in correct order
    
    The IndexCleaner job created in IndexScheduler could complete before
    m_eventMonitor is initialized, which leads to crash in slotCleaningDone.
    
    REVIEW: 108754

Sorry, I thought this fix got into 4.10, but it seems it did not. Nuts.