Bug 261253 - Nepomuk crashes right after start
Summary: Nepomuk crashes right after start
Status: RESOLVED DUPLICATE of bug 239842
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-25 22:44 UTC by Michał Zając
Modified: 2010-12-25 23:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Valgrind memory log (47.76 KB, text/x-log)
2010-12-25 22:45 UTC, Michał Zając
Details
Test Patch (1.07 KB, patch)
2010-12-25 23:47 UTC, Vishesh Handa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Zając 2010-12-25 22:44:45 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.5.90 (4.6 RC1)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-11-generic x86_64
Distribution: Ubuntu natty (development branch)

-- Information about the crash:
Simply enabling it in System Settings causes it to crash constantly, thus rendering the semantic desktop useless (using KDE 4.6 RC1)

The crash can be reproduced every time.

-- Backtrace:
Application: Tymczasowa usługa Nepomuka (nepomukservicestub), signal: Aborted
[Current thread is 1 (Thread 0x7fce6284c780 (LWP 3290))]

Thread 2 (Thread 0x7fce51544700 (LWP 3306)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fce622500eb in wait (this=<value optimized out>, mutex=0x1fb0c10, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x1fb0c10, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00007fce5175671d in Nepomuk::MetadataMover::run (this=0x1fb0bf0) at ../../../../nepomuk/services/filewatch/metadatamover.cpp:165
#4  0x00007fce6224fa2e in QThreadPrivate::start (arg=0x1fb0bf0) at thread/qthread_unix.cpp:285
#5  0x00007fce5fc1cd8c in start_thread (arg=0x7fce51544700) at pthread_create.c:304
#6  0x00007fce5ff1461d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fce6284c780 (LWP 3290)):
[KCrash Handler]
#6  0x00007fce5fe67ba5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fce5fe6b4f6 in abort () at abort.c:92
#8  0x00007fce5fea06bb in __libc_message (do_abort=2, fmt=0x7fce5ff77bf0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9  0x00007fce5feacbb4 in malloc_printerr (mem=0x2107080, caller=<value optimized out>) at malloc.c:6283
#10 free_check (mem=0x2107080, caller=<value optimized out>) at hooks.c:284
#11 0x00007fce5175f43d in addWatchesRecursively (this=0x2097290) at ../../../../nepomuk/services/filewatch/kinotify.cpp:178
#12 KInotify::Private::_k_addWatches (this=0x2097290) at ../../../../nepomuk/services/filewatch/kinotify.cpp:198
#13 0x00007fce5175e3e1 in KInotify::qt_metacall (this=0x20971c0, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0x207f960) at ./kinotify.moc:119
#14 0x00007fce6234af2a in QObject::event (this=0x20971c0, e=<value optimized out>) at kernel/qobject.cpp:1219
#15 0x00007fce60677b44 in QApplicationPrivate::notify_helper (this=0x1eb0cc0, receiver=0x20971c0, e=0x2100090) at kernel/qapplication.cpp:4445
#16 0x00007fce6067c47a in QApplication::notify (this=<value optimized out>, receiver=0x20971c0, e=0x2100090) at kernel/qapplication.cpp:4324
#17 0x00007fce61677d56 in KApplication::notify (this=0x7fffdd4672a0, receiver=0x20971c0, event=0x2100090) at ../../kdeui/kernel/kapplication.cpp:311
#18 0x00007fce62336f7c in QCoreApplication::notifyInternal (this=0x7fffdd4672a0, receiver=0x20971c0, event=0x2100090) at kernel/qcoreapplication.cpp:732
#19 0x00007fce6233a715 in sendEvent (receiver=0x0, event_type=0, data=0x1e99a30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1e99a30) at kernel/qcoreapplication.cpp:1373
#21 0x00007fce62361d33 in sendPostedEvents (s=0x1eb4930) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#22 postEventSourceDispatch (s=0x1eb4930) at kernel/qeventdispatcher_glib.cpp:277
#23 0x00007fce5f143c4d in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x00007fce5f144438 in ?? () from /lib/libglib-2.0.so.0
#25 0x00007fce5f1446c9 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x00007fce62361ecf in QEventDispatcherGlib::processEvents (this=0x1e990e0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#27 0x00007fce6071d9fe in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#28 0x00007fce62336362 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#29 0x00007fce6233659c in QEventLoop::exec (this=0x7fffdd4670b0, flags=...) at kernel/qeventloop.cpp:201
#30 0x00007fce6233a9bb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#31 0x0000000000403c3f in main (argc=2, argv=<value optimized out>) at ../../../nepomuk/servicestub/main.cpp:165

Reported using DrKonqi
Comment 1 Michał Zając 2010-12-25 22:45:59 UTC
Created attachment 55241 [details]
Valgrind memory log

This contatins valgrind memory log, however I'm not sure if it was done properlly.
Comment 2 Vishesh Handa 2010-12-25 23:47:38 UTC
Created attachment 55245 [details]
Test Patch

I really doubt this will work, but if you can, please try it out. It should get applied at 'KDE/kdebase/runtime/nepomuk/services/filewatch/'

I just can't see anything wrong with the code. :/
Comment 3 Vishesh Handa 2010-12-25 23:53:13 UTC

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