Bug 314589

Summary:	Nepomuk crashes when enabled after kde update and after database deleted
Product:	[Unmaintained] nepomuk	Reporter:	Andreas <hohenegger>
Component:	general	Assignee:	Nepomuk Bugs Coordination <nepomuk-bugs>
Status:	RESOLVED FIXED
Severity:	crash	CC:	aaron.zakhrov, ajrlegits, aminesay, aniello.barletta, asala, benoit.leffray.kde, berlin567, crgridley, damien.porquet, denis_rudnei, dimkard, hohenegger, hrvoje.senjan, jfcook267, lindsay.mathieson, m.wege, me, mirza.dervisevic, nepomuk-bugs, philippe.roubach, rrrperson, snowhg, st-adm, stephan.diestelhorst, thiago.holmes, thing1138
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:	http://commits.kde.org/nepomuk-core/b94e9f73bd86593928988e5626511acea805b7be	Version Fixed In:	4.10.1
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi

Description Andreas 2013-02-07 10:26:51 UTC

Application: nepomukservicestub (0.1.0)
KDE Platform Version: 4.10.00
Qt Version: 4.8.3
Operating System: Linux 3.7.0-7-generic i686
Distribution: Ubuntu 12.10

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

I enabled Nepomuk in the systemsettings dialog. It keeps restarting and each time it crashes again.

- Custom settings of the application:

After KDE update to 4.10 I ran the new Nepomuk database cleaner to remove duplicates etc. After that and resolving troubles with Akonadi by completely setting it up from scratch (Akonadi trouble could have been related or not). Nepomuk was taking too much resources [zynic comment about Nepomuk removed], so I switched it off and deleted the database $KDEHOME/share/apps/nepomuk (as I had to do several times before in older KDE versions). Then I rebooted and switched Nepomuk on again.

-- Backtrace:
Application: Nepomuk-Dienst (nepomukservicestub), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  0xb2469bd0 in Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x93cb5d0) at ../../../services/fileindexer/indexscheduler.cpp:385
#8  0xb246b95e in Nepomuk2::IndexScheduler::slotCleaningDone (this=this@entry=0x93cb5d0) at ../../../services/fileindexer/indexscheduler.cpp:234
#9  0xb246bda4 in qt_static_metacall (_a=0xbfd41e88, _id=19, _o=0x93cb5d0, _c=<optimized out>) at ./indexscheduler.moc:114
#10 Nepomuk2::IndexScheduler::qt_static_metacall (_o=0x93cb5d0, _c=QMetaObject::InvokeMetaMethod, _id=19, _a=0xbfd41e88) at ./indexscheduler.moc:89
#11 0xb7613ed6 in QMetaObject::activate (sender=0x93cfce8, m=0xb73f948c <KJob::staticMetaObject>, local_signal_index=0, argv=0xbfd41e88) at kernel/qobject.cpp:3547
#12 0xb72419a5 in KJob::finished (this=this@entry=0x93cfce8, _t1=_t1@entry=0x93cfce8) at ./kjob.moc:187
#13 0xb7241cac in KJob::emitResult (this=0x93cfce8) at ../../kdecore/jobs/kjob.cpp:316
#14 0xb24709a5 in Nepomuk2::IndexCleaner::clearNextBatch (this=this@entry=0x93cfce8) at ../../../services/fileindexer/indexcleaner.cpp:295
#15 0xb2472d87 in Nepomuk2::IndexCleaner::start (this=0x93cfce8) at ../../../services/fileindexer/indexcleaner.cpp:253
#16 0xb246a0d5 in Nepomuk2::IndexScheduler::IndexScheduler (this=0x93cb5d0, parent=0x92b8f28) at ../../../services/fileindexer/indexscheduler.cpp:56
#17 0xb2467bce in Nepomuk2::FileIndexer::FileIndexer (this=0x92b8f28, parent=0x92ba078) at ../../../services/fileindexer/fileindexer.cpp:43
#18 0xb246964a in KPluginFactory::createInstance<Nepomuk2::FileIndexer, QObject> (parentWidget=0x0, parent=0x92ba078, args=...) at /usr/include/kpluginfactory.h:477
#19 0xb733c73e in KPluginFactory::create (this=0x92ba488, iface=0xb6cc35a0 <qt_meta_stringdata_Nepomuk2__Service> "Nepomuk2::Service", parentWidget=0x0, parent=0x92ba078, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:203
#20 0x0804c236 in create<Nepomuk2::Service> (args=..., keyword=..., parent=0x92ba078, parentWidget=0x0, this=<optimized out>) at /usr/include/kpluginfactory.h:531
#21 createInstance<Nepomuk2::Service> (error=0xbfd42244, args=..., parent=0x92ba078, parentWidget=0x0, this=0x9261658) at /usr/include/KDE/../kservice.h:559
#22 createInstance<Nepomuk2::Service> (error=0xbfd42244, args=..., parent=0x92ba078, this=0x9261658) at /usr/include/KDE/../kservice.h:536
#23 Nepomuk2::ServiceControl::start (this=this@entry=0x92ba078) at ../../servicestub/servicecontrol.cpp:92
#24 0x0804c8dc in qt_static_metacall (_a=0x92e10f8, _id=1, _o=0x92ba078, _c=<optimized out>) at ./servicecontrol.moc:62
#25 Nepomuk2::ServiceControl::qt_static_metacall (_o=0x92ba078, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x92e10f8) at ./servicecontrol.moc:55
#26 0xb760d9aa in QMetaCallEvent::placeMetaCall (this=0x92df560, object=0x92ba078) at kernel/qobject.cpp:525
#27 0xb7611eeb in QObject::event (this=0x92ba078, e=0x92df560) at kernel/qobject.cpp:1195
#28 0xb625e39c in QApplicationPrivate::notify_helper (this=0x91b2910, receiver=0x92ba078, e=0x92df560) at kernel/qapplication.cpp:4562
#29 0xb6262daf in QApplication::notify (this=0x92df560, receiver=0x92ba078, e=0x92df560) at kernel/qapplication.cpp:3944
#30 0xb6ee1321 in KApplication::notify (this=0xbfd42b38, receiver=0x92ba078, event=0x92df560) at ../../kdeui/kernel/kapplication.cpp:311
#31 0xb75fb78e in QCoreApplication::notifyInternal (this=0xbfd42b38, receiver=0x92ba078, event=0x92df560) at kernel/qcoreapplication.cpp:915
#32 0xb75ff97d in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#33 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9191a38) at kernel/qcoreapplication.cpp:1539
#34 0xb75ffc0c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1432
#35 0xb762d804 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#36 postEventSourceDispatch (s=0x91a8a00) at kernel/qeventdispatcher_glib.cpp:279
#37 0xb5d969e3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#38 0xb5d96d80 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#39 0xb5d96e61 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#40 0xb762d981 in QEventDispatcherGlib::processEvents (this=0x91927e8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#41 0xb63149aa in QGuiEventDispatcherGlib::processEvents (this=0x91927e8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#42 0xb75fa26c in QEventLoop::processEvents (this=this@entry=0xbfd42a18, flags=...) at kernel/qeventloop.cpp:149
#43 0xb75fa561 in QEventLoop::exec (this=0xbfd42a18, flags=...) at kernel/qeventloop.cpp:204
#44 0xb75ffcba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#45 0xb625bfc4 in QApplication::exec () at kernel/qapplication.cpp:3823
#46 0x0804b27d in main (argc=2, argv=0xbfd42cd4) at ../../servicestub/main.cpp:180

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

Possible duplicates by query: bug 314556, bug 313969.

Reported using DrKonqi

Comment 1 Rudy Raab 2013-02-07 15:20:28 UTC

Created attachment 76981 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4

- What I was doing when the application crashed:
Same thing as reported here. I had just upgraded OpenSUSE 12.2 to KDE 4.10, and deleted ~/.kde4/share/apps/nepomuk (I figured a fresh start was better). 

- Unusual behavior I noticed:
I also saw it restart and crash many times.

-- Backtrace (Reduced):
#6  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x1abb9b0) at /usr/src/debug/nepomuk-core-4.10.0/services/fileindexer/indexscheduler.cpp:385
#7  0x00007fe2e428e60c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x1abb9b0) at /usr/src/debug/nepomuk-core-4.10.0/services/fileindexer/indexscheduler.cpp:234
#8  0x00007fe2e428e945 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at /usr/src/debug/nepomuk-core-4.10.0/build/services/fileindexer/indexscheduler.moc:114
#9  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/nepomuk-core-4.10.0/build/services/fileindexer/indexscheduler.moc:89
[...]
#11 0x00007fe2f2f1789f in KJob::finished (this=this@entry=0x1abba90, _t1=_t1@entry=0x1abba90) at /usr/src/debug/kdelibs-4.10.0/build/kdecore/kjob.moc:187

Comment 2 Jekyll Wu 2013-02-07 18:21:16 UTC

*** Bug 313969 has been marked as a duplicate of this bug. ***

Comment 3 Jekyll Wu 2013-02-07 18:21:27 UTC

*** Bug 314556 has been marked as a duplicate of this bug. ***

Comment 4 Benoit Leffray 2013-02-07 20:55:31 UTC

Created attachment 76990 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.3

- What I was doing when the application crashed:

I had just rebooted my PC and logged in again. Then I saw this crash.

-- Backtrace (Reduced):
#6  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x1745ba0) at ../../../services/fileindexer/indexscheduler.cpp:385
#7  0x00007fb2d9399c9c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x1745ba0) at ../../../services/fileindexer/indexscheduler.cpp:234
#8  0x00007fb2d9399fd5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#9  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#11 0x00007fb2f6c80d2f in KJob::finished (this=this@entry=0x1745cc0, _t1=_t1@entry=0x1745cc0) at ./kjob.moc:187

Comment 5 Benoit Leffray 2013-02-07 21:11:12 UTC

Created attachment 76991 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.3

- What I was doing when the application crashed:

Rebooted my PC, then logged in again. I then saw this crash.

-- Backtrace (Reduced):
#6  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0xf170a0) at ../../../services/fileindexer/indexscheduler.cpp:385
#7  0x00007fd484b2cc9c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0xf170a0) at ../../../services/fileindexer/indexscheduler.cpp:234
#8  0x00007fd484b2cfd5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#9  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#11 0x00007fd4a23c7d2f in KJob::finished (this=this@entry=0xf17180, _t1=_t1@entry=0xf17180) at ./kjob.moc:187

Comment 6 A. Sala 2013-02-08 00:08:46 UTC

Created attachment 76996 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.3

- What I was doing when the application crashed:
I deleted the .kde/share/apps/nepomuk folder, logged out and logged in to KDE again.
- Unusual behavior I noticed:
Upgraded to 4.10, and nepomuk was activated in systemsettings but indexing was not working...

-- Backtrace (Reduced):
#6  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x10e99b0) at ../../../services/fileindexer/indexscheduler.cpp:385
#7  0x00007f0719c4dc9c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x10e99b0) at ../../../services/fileindexer/indexscheduler.cpp:234
#8  0x00007f0719c4dfd5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#9  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#11 0x00007f072a709d2f in KJob::finished (this=this@entry=0x1119080, _t1=_t1@entry=0x1119080) at ./kjob.moc:187

Comment 7 Hrvoje Senjan 2013-02-09 15:33:25 UTC

Fixed with b94e9f73bd86593928988e5626511acea805b7be, yes?

Comment 8 Carl Gridley 2013-02-09 17:30:48 UTC

Created attachment 77056 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.3

- What I was doing when the application crashed:

Just logged in after having removed the database for a fresh start.

-- Backtrace (Reduced):
#5  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x25b8cb0) at ../../../services/fileindexer/indexscheduler.cpp:385
#6  0x00007fc2f161cc9c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x25b8cb0) at ../../../services/fileindexer/indexscheduler.cpp:234
#7  0x00007fc2f161cfd5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#8  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#10 0x00007fc301bbcd2f in KJob::finished(KJob*) () from /usr/lib/libkdecore.so.5

Comment 9 m.wege 2013-02-10 09:57:00 UTC

Created attachment 77085 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.3

- What I was doing when the application crashed:
I did exactly what the original reporter did: After Nepomuk-Cleaner was not doing well (crashing on fixing duplicate contacts), I deleted the Nepomuk database by renaming its folder (before I disabled Nepomuk). Then I restarted and since then there are frequent crashes.

-- Backtrace (Reduced):
#6  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x1666520) at ../../../services/fileindexer/indexscheduler.cpp:385
#7  0x00007fbda66ddc9c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x1666520) at ../../../services/fileindexer/indexscheduler.cpp:234
#8  0x00007fbda66ddfd5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#9  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#11 0x00007fbdb6e9ed2f in KJob::finished (this=this@entry=0x1665610, _t1=_t1@entry=0x1665610) at ./kjob.moc:187

Comment 10 Hrvoje Senjan 2013-02-10 17:11:29 UTC

*** Bug 314742 has been marked as a duplicate of this bug. ***

Comment 11 Benoit Leffray 2013-02-10 19:33:39 UTC

Created attachment 77104 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.3

- What I was doing when the application crashed:

Rebooted my PC then logged in again. The crashed occurred after the logging

-- Backtrace (Reduced):
#6  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x11abe90) at ../../../services/fileindexer/indexscheduler.cpp:385
#7  0x00007f4d7b3c0c9c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x11abe90) at ../../../services/fileindexer/indexscheduler.cpp:234
#8  0x00007f4d7b3c0fd5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#9  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#11 0x00007f4d9cce6d2f in KJob::finished (this=this@entry=0x10cdcf0, _t1=_t1@entry=0x10cdcf0) at ./kjob.moc:187

Comment 12 Dimitris Kardarakos 2013-02-10 21:42:23 UTC

Created attachment 77115 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.2

- What I was doing when the application crashed:

1. Upgraded to kde 4.10

2. Saw that nepomuk indexer was not indexing anything

3. Removed .kde/share/apps/nepomuk folder after stopping nepomuk and killing related processes

4. Restarted

-- Backtrace (Reduced):
#7  0xb25c904f in Nepomuk2::IndexScheduler::slotScheduleIndexing (this=0x8517908) at ../../../services/fileindexer/indexscheduler.cpp:385
#8  0xb25ca131 in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x8517908) at ../../../services/fileindexer/indexscheduler.cpp:234
#9  0xb25cb1a8 in qt_static_metacall (_a=0xbf838248, _id=19, _o=0x8517908, _c=<optimized out>) at ./indexscheduler.moc:114
#10 Nepomuk2::IndexScheduler::qt_static_metacall (_o=0x8517908, _c=QMetaObject::InvokeMetaMethod, _id=19, _a=0xbf838248) at ./indexscheduler.moc:89
[...]
#12 0xb7203925 in KJob::finished(KJob*) () from /usr/lib/libkdecore.so.5

Comment 13 Philippe ROUBACH 2013-02-11 14:11:30 UTC

Created attachment 77134 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4

- What I was doing when the application crashed:

i update opensuse 12.2 kde 4.8.5 to kde 4.10
then
i restart my pc
then
 i open a session
then
in nepomuk settings i activated the indexer
then
nepomuk crashes
then
i restart nepomuk
then
nepomuk crashes
theni restart nepomuk
then
nepomuk crashes
then
i restart nepomuk
then
no more crash message

each time i open a kde session then i have these 3 crashes

-- Backtrace (Reduced):
#5  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x1a491e0) at /usr/src/debug/nepomuk-core-4.10.0/services/fileindexer/indexscheduler.cpp:385
#6  0x00007f91adc3951c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x1a491e0) at /usr/src/debug/nepomuk-core-4.10.0/services/fileindexer/indexscheduler.cpp:234
#7  0x00007f91adc39855 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at /usr/src/debug/nepomuk-core-4.10.0/build/services/fileindexer/indexscheduler.moc:114
#8  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/nepomuk-core-4.10.0/build/services/fileindexer/indexscheduler.moc:89
[...]
#10 0x00007f91bc83589f in KJob::finished (this=this@entry=0x1a32ea0, _t1=_t1@entry=0x1a32ea0) at /usr/src/debug/kdelibs-4.10.0/build/kdecore/kjob.moc:187

Comment 14 Vishesh Handa 2013-02-11 14:35:51 UTC

I wish this had been caught during the RC testings. It's such a stupid bug.

Comment 15 m.wege 2013-02-11 14:54:55 UTC

Is there a workaround apart from turning Nepomuk of until the relase is made.

May be next time the testing scenario for Nepomuk should be more detailed, so that this kind of bug could have been found. I just stumpled on it after I had decided to delete my old database. I guess most tester just worked with an existing one.
https://community.kde.org/Getinvolved/Quality/Beta/4.10/AreasToTest#Nepomuk

Comment 16 Vishesh Handa 2013-02-11 17:21:56 UTC

(In reply to comment #15)
> Is there a workaround apart from turning Nepomuk of until the relase is made.

Unfortunately, no :( Sorry.

> 
> May be next time the testing scenario for Nepomuk should be more detailed,
> so that this kind of bug could have been found. I just stumpled on it after
> I had decided to delete my old database. I guess most tester just worked
> with an existing one.
> https://community.kde.org/Getinvolved/Quality/Beta/4.10/AreasToTest#Nepomuk

Will do. I plan to add a lot more testing guidelines.

Comment 17 Legits 2013-02-13 05:44:43 UTC

Created attachment 77236 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.3

- What I was doing when the application crashed: Had just logged into my account.

- Unusual behavior I noticed: Nothing in particular. Nepomuk just crashes for no apparent reason.

- Custom settings of the application: None. All settings are default.

-- Backtrace (Reduced):
#5  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x221b9a0) at ../../../services/fileindexer/indexscheduler.cpp:385
#6  0x00007f51fb32cbbc in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x221b9a0) at ../../../services/fileindexer/indexscheduler.cpp:234
#7  0x00007f51fb32cef5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#8  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#10 0x00007f520b8bdd2f in KJob::finished(KJob*) () from /usr/lib/libkdecore.so.5

Comment 18 Vishesh Handa 2013-02-13 09:03:00 UTC

*** Bug 315036 has been marked as a duplicate of this bug. ***

Comment 19 Vishesh Handa 2013-02-13 09:06:53 UTC

*** Bug 315034 has been marked as a duplicate of this bug. ***

Comment 20 Yaroslav Tsarko 2013-02-14 08:09:09 UTC

Created attachment 77278 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.2

I logged into system didn`t do anything yet.

-- Backtrace (Reduced):
#6  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=0x1ea88b0) at ../../../services/fileindexer/indexscheduler.cpp:385
#7  0x00007f40f054f73f in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x1ea88b0) at ../../../services/fileindexer/indexscheduler.cpp:234
#8  0x00007f40f0550515 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#9  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#11 0x00007f4100ae22bf in KJob::finished (this=<optimized out>, _t1=0x1e86fc0) at ./kjob.moc:187

Comment 21 Philippe ROUBACH 2013-02-14 17:54:31 UTC

opensuse supplies since yesterday a fixed nepomuk
thre is ni more pb in my case

Comment 22 m.wege 2013-02-14 20:33:34 UTC

Kubuntu also provided new Nepomuk packages yesterday. I do not know if they contained the patch. If so, my system is still crashing when I reactivate Nepomuk.

Comment 23 m.wege 2013-02-15 21:18:50 UTC

Kubuntu just updated Nepomuk again. Do not know if the patch is included, but if so it is still crashing:
Application: Nepomuk-Dienst (nepomukservicestub), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x15575f0) at ../../../services/fileindexer/indexscheduler.cpp:385
#7  0x00007f80751c3bbc in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x15575f0) at ../../../services/fileindexer/indexscheduler.cpp:234
#8  0x00007f80751c3ef5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#9  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
#10 0x00007f808612df5f in QMetaObject::activate (sender=0x15566d0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffc6a90e60) at kernel/qobject.cpp:3547
#11 0x00007f808598ad2f in KJob::finished (this=this@entry=0x15566d0, _t1=_t1@entry=0x15566d0) at ./kjob.moc:187
#12 0x00007f808598af75 in KJob::emitResult (this=0x15566d0) at ../../kdecore/jobs/kjob.cpp:316
#13 0x00007f80751c7b5b in Nepomuk2::IndexCleaner::clearNextBatch (this=this@entry=0x15566d0) at ../../../services/fileindexer/indexcleaner.cpp:295
#14 0x00007f80751c9ce3 in Nepomuk2::IndexCleaner::start (this=0x15566d0) at ../../../services/fileindexer/indexcleaner.cpp:253
#15 0x00007f80751c2717 in Nepomuk2::IndexScheduler::IndexScheduler (this=0x15575f0, parent=<optimized out>) at ../../../services/fileindexer/indexscheduler.cpp:56
#16 0x00007f80751c0ac7 in Nepomuk2::FileIndexer::FileIndexer (this=0x150f730, parent=<optimized out>) at ../../../services/fileindexer/fileindexer.cpp:43
#17 0x00007f80751c1f37 in KPluginFactory::createInstance<Nepomuk2::FileIndexer, QObject> (parentWidget=<optimized out>, parent=<optimized out>, args=...) at /usr/include/kpluginfactory.h:477
#18 0x00007f8085a69f65 in KPluginFactory::create (this=0x1403ef0, iface=0x7f8084fe5be0 <qt_meta_stringdata_Nepomuk2__Service> "Nepomuk2::Service", parentWidget=0x0, parent=0x14107f0, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:203
#19 0x0000000000404c93 in create<Nepomuk2::Service> (args=..., keyword=..., parent=0x14107f0, parentWidget=0x0, this=0x1403ef0) at /usr/include/kpluginfactory.h:531
#20 createInstance<Nepomuk2::Service> (error=0x7fffc6a91420, args=..., parent=0x14107f0, parentWidget=0x0, this=0x149c520) at /usr/include/KDE/../kservice.h:559
#21 createInstance<Nepomuk2::Service> (error=0x7fffc6a91420, args=..., parent=0x14107f0, this=0x149c520) at /usr/include/KDE/../kservice.h:536
#22 Nepomuk2::ServiceControl::start (this=0x14107f0) at ../../servicestub/servicecontrol.cpp:92
#23 0x000000000040529d in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./servicecontrol.moc:62
#24 Nepomuk2::ServiceControl::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./servicecontrol.moc:55
#25 0x00007f808612d43e in QObject::event (this=0x14107f0, e=<optimized out>) at kernel/qobject.cpp:1195
#26 0x00007f8084442e9c in QApplicationPrivate::notify_helper (this=this@entry=0x12824b0, receiver=receiver@entry=0x14107f0, e=e@entry=0x149d890) at kernel/qapplication.cpp:4562
#27 0x00007f808444730a in QApplication::notify (this=0x7fffc6a92070, receiver=0x14107f0, e=0x149d890) at kernel/qapplication.cpp:4423
#28 0x00007f8085448636 in KApplication::notify (this=0x7fffc6a92070, receiver=0x14107f0, event=0x149d890) at ../../kdeui/kernel/kapplication.cpp:311
#29 0x00007f808611856e in QCoreApplication::notifyInternal (this=0x7fffc6a92070, receiver=receiver@entry=0x14107f0, event=event@entry=0x149d890) at kernel/qcoreapplication.cpp:915
#30 0x00007f808611c3f1 in sendEvent (event=0x149d890, receiver=0x14107f0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x125b2f0) at kernel/qcoreapplication.cpp:1539
#32 0x00007f8086146a63 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#33 postEventSourceDispatch (s=s@entry=0x1284250) at kernel/qeventdispatcher_glib.cpp:279
#34 0x00007f80830c5ab5 in g_main_dispatch (context=0x128a720) at /build/buildd/glib2.0-2.34.1/./glib/gmain.c:2715
#35 g_main_context_dispatch (context=context@entry=0x128a720) at /build/buildd/glib2.0-2.34.1/./glib/gmain.c:3219
#36 0x00007f80830c5de8 in g_main_context_iterate (context=context@entry=0x128a720, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.34.1/./glib/gmain.c:3290
#37 0x00007f80830c5ea4 in g_main_context_iteration (context=0x128a720, may_block=1) at /build/buildd/glib2.0-2.34.1/./glib/gmain.c:3351
#38 0x00007f8086146bf6 in QEventDispatcherGlib::processEvents (this=0x125cc20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#39 0x00007f80844e7c1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#40 0x00007f80861172bf in QEventLoop::processEvents (this=this@entry=0x7fffc6a91e50, flags=...) at kernel/qeventloop.cpp:149
#41 0x00007f8086117548 in QEventLoop::exec (this=0x7fffc6a91e50, flags=...) at kernel/qeventloop.cpp:204
#42 0x00007f808611c708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#43 0x0000000000403dd0 in main (argc=<optimized out>, argv=0x7fffc6a922b8) at ../../servicestub/main.cpp:180

Comment 24 Vishesh Handa 2013-02-15 21:38:07 UTC

*** Bug 315238 has been marked as a duplicate of this bug. ***

Comment 25 Blackpaw 2013-02-15 21:53:30 UTC

Created attachment 77346 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.4

- What I was doing when the application crashed:

Stopped nepomuk & akonadi, erased both databases. Now cannot start nepomuserver at all.
NB - I was getting erratic nepomuk crashes before this.

-- Backtrace (Reduced):
#5  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x1ec9260) at ../../../services/fileindexer/indexscheduler.cpp:385
#6  0x00007f3a83174e6c in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x1ec9260) at ../../../services/fileindexer/indexscheduler.cpp:234
#7  0x00007f3a83175635 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#8  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#10 0x00007f3a9372ac7f in KJob::finished(KJob*) () from /usr/lib/libkdecore.so.5

Comment 26 Hrvoje Senjan 2013-02-15 22:03:47 UTC

People, bug is *fixed*, ask your distribution to include the fix, or compile it yourself. No need for new(rather the same) backtraces.
Thanks :-)

Comment 27 Blackpaw 2013-02-15 22:09:10 UTC

Exact same problem in latest kubuntu raring. And we have to wait a month plus for 4.10.1 for a fix? Seriously? the flagship feature of kde and all its dependant modules are unusable because of one buggy module?

Highlights why the deep integration of nepomuk was a bad idea. How many years has it been? and still not reliable or even usuable.

Comment 28 Stephan Diestelhorst 2013-02-17 09:32:48 UTC

Also broken for me on latest Kubuntu 12.04.2 with 4.10 repositories enabled.  Not fixed.

Comment 29 Jekyll Wu 2013-02-17 10:09:47 UTC

(In reply to comment #28)
> Also broken for me on latest Kubuntu 12.04.2 with 4.10 repositories enabled.
> Not fixed.

because it is fixed in 4 .10.1

Comment 30 Stephan Diestelhorst 2013-02-17 17:55:49 UTC

I didn't feel like waiting for a month for 4.10.1 to be release, so I went ahead and built the package myself.  On Kubuntu this is rather simple:

sudo apt-get build-dep nepomuk-core
sudo apt-get install fakeroot
apt-get source nepomuk-core
cd nepomuk-core-4.10.0
wget "https://projects.kde.org/projects/kde/kdelibs/nepomuk-core/repository/revisions/b94e9f73bd86593928988e5626511acea805b7be/diff/services/fileindexer/indexscheduler.cpp?format=diff" -O indexscheduler.diff
patch -p1 < indexscheduler.diff
dpkg-buildpackage -us -uc -nc
cd ..
dpkg -i nepomuk*.deb

Thanks for patching this upstream, guys!

Comment 31 Stephan Diestelhorst 2013-02-17 17:58:24 UTC

(In reply to comment #29)
> (In reply to comment #28)
> > Also broken for me on latest Kubuntu 12.04.2 with 4.10 repositories enabled.
> > Not fixed.
> 
> because it is fixed in 4 .10.1

Which is to be relased March 5th [1], so there is no point in blaming the distros for not building the packages quick enough.

[1] http://techbase.kde.org/Schedules/KDE4/4.10_Release_Schedule#Tuesday.2C_March_5.2C_2013:_KDE_SC_4.10.1_release

Comment 32 st-adm 2013-02-19 18:26:40 UTC

Created attachment 77442 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.4

Just updated to  KDE 4.10, withg -Os fixes for qt-core

-- Backtrace (Reduced):
#6  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=0x1561c80) at /var/tmp/portage/kde-base/nepomuk-core-4.10.0-r1/work/nepomuk-core-4.10.0/services/fileindexer/indexscheduler.cpp:385
#7  0x00007fa2bb05591d in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x1561c80) at /var/tmp/portage/kde-base/nepomuk-core-4.10.0-r1/work/nepomuk-core-4.10.0/services/fileindexer/indexscheduler.cpp:234
#8  0x00007fa2bb0566f5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at /var/tmp/portage/kde-base/nepomuk-core-4.10.0-r1/work/nepomuk-core-4.10.0_build/services/fileindexer/indexscheduler.moc:114
#9  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /var/tmp/portage/kde-base/nepomuk-core-4.10.0-r1/work/nepomuk-core-4.10.0_build/services/fileindexer/indexscheduler.moc:89
[...]
#11 0x00007fa2bfaa1adf in KJob::finished(KJob*) () from /usr/lib64/libkdecore.so.5

Comment 33 Jeff 2013-02-24 21:16:17 UTC

Created attachment 77555 [details]
New crash information added by DrKonqi

nepomukservicestub (0.1.0) on KDE Platform 4.10.00 using Qt 4.8.3

- What I was doing when the application crashed:

Happens everytime that I login.  I try and click restart applicaton and it does the same thing.  I have to close it.

-- Backtrace (Reduced):
#5  Nepomuk2::IndexScheduler::slotScheduleIndexing (this=this@entry=0x1feb940) at ../../../services/fileindexer/indexscheduler.cpp:385
#6  0x00007fcc9e666bbc in Nepomuk2::IndexScheduler::slotCleaningDone (this=0x1feb940) at ../../../services/fileindexer/indexscheduler.cpp:234
#7  0x00007fcc9e666ef5 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./indexscheduler.moc:114
#8  Nepomuk2::IndexScheduler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./indexscheduler.moc:89
[...]
#10 0x00007fccaebd0d2f in KJob::finished(KJob*) () from /usr/lib/libkdecore.so.5

Comment 34 Jekyll Wu 2013-02-28 11:27:00 UTC

*** Bug 315893 has been marked as a duplicate of this bug. ***

Comment 35 Jekyll Wu 2013-03-02 11:47:27 UTC

*** Bug 316007 has been marked as a duplicate of this bug. ***

Comment 36 Jekyll Wu 2013-03-02 11:47:29 UTC

*** Bug 315997 has been marked as a duplicate of this bug. ***

Comment 37 Jekyll Wu 2013-03-03 23:18:03 UTC

*** Bug 316096 has been marked as a duplicate of this bug. ***

Comment 38 thing1138 2013-03-28 17:39:31 UTC

I can confirm that this bug is still present in nepomuk 4.10.1 as it is still crashing after reboot + login for me as well.

Comment 39 m.wege 2013-04-01 07:09:32 UTC

(In reply to comment #38)
> I can confirm that this bug is still present in nepomuk 4.10.1 as it is
> still crashing after reboot + login for me as well.
Since it is supposed to be fixed and you are the first who claims it still happens in 4.10.1 I suggest you add a backtrace here. I may be just a different bug.