Bug 314556

Summary: Nepomuk crashed when enabled
Product: [Unmaintained] nepomuk Reporter: Mirza <mirza.dervisevic>
Component: generalAssignee: Nepomuk Bugs Coordination <nepomuk-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: nepomuk-bugs
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mirza 2013-02-06 20:56:10 UTC
Application: nepomukservicestub (0.1.0)
KDE Platform Version: 4.10.00
Qt Version: 4.8.2
Operating System: Linux 3.2.0-37-generic i686
Distribution: Ubuntu 12.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed: I just start nepomuk indexing, and previously I deleted content of ~/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/

-- Backtrace:
Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  0x022297b4 in Nepomuk2::IndexingQueue::suspend (this=0x660000) at ../../../services/fileindexer/indexingqueue.cpp:61
#8  0x0222710e in Nepomuk2::IndexScheduler::slotScheduleIndexing (this=0x844ea68) at ../../../services/fileindexer/indexscheduler.cpp:389
#9  0x02228131 in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x844ea68) at ../../../services/fileindexer/indexscheduler.cpp:234
#10 0x022291a8 in qt_static_metacall (_a=0xbf9cc5e8, _id=19, _o=0x844ea68, _c=<optimized out>) at ./indexscheduler.moc:114
#11 Nepomuk2::IndexScheduler::qt_static_metacall (_o=0x844ea68, _c=QMetaObject::InvokeMetaMethod, _id=19, _a=0xbf9cc5e8) at ./indexscheduler.moc:89
#12 0x002a3b81 in QMetaObject::activate (sender=0x844ad30, m=0x7b648c, local_signal_index=0, argv=0xbf9cc5e8) at kernel/qobject.cpp:3547
#13 0x00601925 in KJob::finished (this=0x844ad30, _t1=0x844ad30) at ./kjob.moc:187
#14 0x00601c0c in KJob::emitResult (this=0x844ad30) at ../../kdecore/jobs/kjob.cpp:316
#15 0x0222f224 in Nepomuk2::IndexCleaner::clearNextBatch (this=0x844ad30) at ../../../services/fileindexer/indexcleaner.cpp:295
#16 0x02230369 in Nepomuk2::IndexCleaner::start (this=0x844ad30) at ../../../services/fileindexer/indexcleaner.cpp:253
#17 0x02227535 in Nepomuk2::IndexScheduler::IndexScheduler (this=0x844ea68, parent=0x83e3ea8) at ../../../services/fileindexer/indexscheduler.cpp:56
#18 0x02224bce in Nepomuk2::FileIndexer::FileIndexer (this=0x83e3ea8, parent=0x83ceed0) at ../../../services/fileindexer/fileindexer.cpp:43
#19 0x022265fa in KPluginFactory::createInstance<Nepomuk2::FileIndexer, QObject> (parentWidget=0x0, parent=0x83ceed0, args=...) at /usr/include/kpluginfactory.h:477
#20 0x007096ae in KPluginFactory::create (this=0x83cd6a8, iface=0xce27a0 "Nepomuk2::Service", parentWidget=0x0, parent=0x83ceed0, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:203
#21 0x0804c1d0 in create<Nepomuk2::Service> (parent=0x83ceed0, this=0x83cd6a8, args=..., keyword=..., parentWidget=0x0) at /usr/include/kpluginfactory.h:531
#22 createInstance<Nepomuk2::Service> (error=0xbf9ccabc, args=..., parent=0x83ceed0, parentWidget=0x0, this=0x83c0958) at /usr/include/KDE/../kservice.h:559
#23 createInstance<Nepomuk2::Service> (error=0xbf9ccabc, args=..., parent=0x83ceed0, this=0x83c0958) at /usr/include/KDE/../kservice.h:536
#24 Nepomuk2::ServiceControl::start (this=0x83ceed0) at ../../servicestub/servicecontrol.cpp:92
#25 0x0804c8c0 in qt_static_metacall (_a=0x83bfe38, _id=1, _o=0x83ceed0, _c=<optimized out>) at ./servicecontrol.moc:62
#26 Nepomuk2::ServiceControl::qt_static_metacall (_o=0x83ceed0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x83bfe38) at ./servicecontrol.moc:55
#27 0x0029f0d1 in QMetaCallEvent::placeMetaCall (this=0x83c03b0, object=0x83ceed0) at kernel/qobject.cpp:525
#28 0x002a814b in QObject::event (this=0x83ceed0, e=0x83c03b0) at kernel/qobject.cpp:1195
#29 0x00e86df4 in notify_helper (e=0x83c03b0, receiver=0x83ceed0, this=0x826cc78) at kernel/qapplication.cpp:4556
#30 QApplicationPrivate::notify_helper (this=0x826cc78, receiver=0x83ceed0, e=0x83c03b0) at kernel/qapplication.cpp:4528
#31 0x00e8c15d in QApplication::notify (this=0x83c03b0, receiver=0x83ceed0, e=0x83c03b0) at kernel/qapplication.cpp:4285
#32 0x009ab9a1 in KApplication::notify (this=0xbf9cd42c, receiver=0x83ceed0, event=0x83c03b0) at ../../kdeui/kernel/kapplication.cpp:311
#33 0x0028cdde in QCoreApplication::notifyInternal (this=0xbf9cd42c, receiver=0x83ceed0, event=0x83c03b0) at kernel/qcoreapplication.cpp:915
#34 0x00290f38 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#35 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x824fa38) at kernel/qcoreapplication.cpp:1539
#36 0x0029126c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1432
#37 0x002bf964 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#38 postEventSourceDispatch (s=0x8266a60) at kernel/qeventdispatcher_glib.cpp:279
#39 0x06db9d86 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#40 0x06dba125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#41 0x06dba201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#42 0x002bfd57 in QEventDispatcherGlib::processEvents (this=0x82507e8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#43 0x00f3fa1a in QGuiEventDispatcherGlib::processEvents (this=0x82507e8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#44 0x0028b67d in QEventLoop::processEvents (this=0xbf9cd294, flags=...) at kernel/qeventloop.cpp:149
#45 0x0028b919 in QEventLoop::exec (this=0xbf9cd294, flags=...) at kernel/qeventloop.cpp:204
#46 0x0029131a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#47 0x00e849c4 in QApplication::exec () at kernel/qapplication.cpp:3817
#48 0x0804b17b in main (argc=-1073741824, argv=0x6108319b) at ../../servicestub/main.cpp:180

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-02-07 18:21:27 UTC

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