Version: (using KDE 4.3.5) Compiler: gcc version 4.4.1 Using built-in specs. Target: x86_64-manbo-linux-gnu Configured with: ../configure --prefix=/usr --libexecdir=/usr/lib --with-slibdir=/lib64 --with-bugurl=https://qa.mandriva.com/ --mandir=/usr/share/man --infodir=/usr/share/info --enable-checking=release --enable-languages=c,c++,ada,fortran,objc,obj-c++,java --build=x86_64-manbo-linux-gnu --host=x86_64-manbo-linux-gnu --with-cpu=generic --with-system-zlib --enable-threads=posix --enable-shared --enable-objc-gc --enable-long-long --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --enable-java-awt=gtk --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-gtk-cairo --disable-libjava-multilib --enable-ssp --disable-libssp --disable-werror --with-ppl --with-cloog --with-python-dir=/lib/python2.6/site-packages Thread model: posix OS: Linux Installed from: Mandriva RPMs I only noticed this crash when I noticed the core dump file, so I don't know what caused it or how to reproduce it. The back trace seams to be similar to the back trace on report 230687, so this may be a duplicate. https://bugs.kde.org/show_bug.cgi?id=230687 A bit of system and version info is next. $ rpm -q -a | egrep 'nepomuk|kdebase' | sort kdebase4-debug-4.3.5-0.3mdv2010.0 kdebase4-devel-4.3.5-0.3mdv2010.0 kdebase4-runtime-4.3.5-0.6mdv2010.0 kdebase4-runtime-debug-4.3.5-0.6mdv2010.0 kdebase4-workspace-4.3.5-0.11mdv2010.0 kdebase4-workspace-debug-4.3.5-0.11mdv2010.0 kdebase4-workspace-devel-4.3.5-0.11mdv2010.0 lib64nepomuk4-4.3.5-0.21mdv2010.0 lib64nepomukannotation0-0.6.0-2mdv2010.0 lib64nepomukcontext0-0.6.0-2mdv2010.0 lib64nepomukquery4-4.3.5-0.11mdv2010.0 lib64nepomukqueryclient4-4.3.5-0.11mdv2010.0 lib64nepomuktasks0-0.6.0-2mdv2010.0 lib64nepomukutils0-0.6.0-2mdv2010.0 lib64nepomukvisualization0-0.6.0-2mdv2010.0 nepomuk-scribo-0.6.0-2mdv2010.0 nepomuk-scribo-debug-0.6.0-2mdv2010.0 $ cat /etc/release Mandriva Linux release 2010.0 (Official) for x86_64 $ uname -a Linux marte.lan 2.6.31.12-desktop-3mnb #1 SMP Thu Mar 25 12:47:42 EDT 2010 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz GNU/Linux The backtrace is next. (gdb) bt #0 0x00007f92ade3e545 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007f92ade3fb60 in abort () at abort.c:88 #2 0x00007f92ade7dbd0 in malloc_printerr (action=2, str=0x7f92adf34363 "free(): invalid pointer", ptr=0x15d9) at malloc.c:6222 #3 0x00007f92afc3a3dc in QString::free (d=0x2030da0) at tools/qstring.cpp:955 #4 0x00007f92a7bb77b8 in Nepomuk::StrigiService::userStatusString (this=0x7fff351ed590) at /usr/lib/qt4/include/QtCore/qstring.h:866 #5 0x00007f92a7bc1743 in Nepomuk::SystemTray::slotUpdateStrigiStatus (this=0x1c73040) at /usr/src/debug/kdebase-runtime-4.3.5/nepomuk/services/strigi/systray.cpp:75 #6 0x00007f92a7bc1870 in Nepomuk::SystemTray::qt_metacall (this=0x1c73040, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.3.5/build/nepomuk/services/strigi/systray.moc:68 #7 0x00007f92afcf288c in QMetaObject::activate (sender=0x1b645e0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xffffffffffffffff) at kernel/qobject.cpp:3112 #8 0x00007f92a7bb78e8 in Nepomuk::StrigiService::qt_metacall (this=0x1b645e0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x1dc3ce0) at /usr/src/debug/kdebase-runtime-4.3.5/build/nepomuk/services/strigi/strigiservice.moc:77 #9 0x00007f92afcecba9 in QObject::event (this=0x1b645e0, e=0x202d890) at kernel/qobject.cpp:1110 #10 0x00007f92aef7112c in QApplicationPrivate::notify_helper (this=0x1abf010, receiver=0x1b645e0, e=0x202d890) at kernel/qapplication.cpp:4065 #11 0x00007f92aef783fe in QApplication::notify (this=0x7fff351ee1c0, receiver=0x1b645e0, e=0x202d890) at kernel/qapplication.cpp:4030 #12 0x00007f92afcdd6ac in QCoreApplication::notifyInternal (this=0x7fff351ee1c0, receiver=0x1b645e0, event=0x202d890) at kernel/qcoreapplication.cpp:610 #13 0x00007f92afcde2ba in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x1aa6cd0) at ../../src/corelib/kernel/qcoreapplication.h:213 #14 0x00007f92afd060d3 in postEventSourceDispatch (s=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:218 #15 0x00007f92ad55f4ce in IA__g_main_context_dispatch (context=0x1ac1290) at gmain.c:1960 #16 0x00007f92ad562e98 in g_main_context_iterate (context=0x1ac1290, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591 #17 0x00007f92ad562fc0 in IA__g_main_context_iteration (context=0x1ac1290, may_block=1) at gmain.c:2654 #18 0x00007f92afd05c73 in QEventDispatcherGlib::processEvents (this=0x1aa68c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:406 #19 0x00007f92af00464e in QGuiEventDispatcherGlib::processEvents (this=0x15d9, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #20 0x00007f92afcdbfe2 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #21 0x00007f92afcdc3b4 in QEventLoop::exec (this=0x7fff351edfa0, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:201 #22 0x00007f92afcde569 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #23 0x00000000004036fc in main (argc=2, argv=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.3.5/nepomuk/servicestub/main.cpp:151
*** Bug 235315 has been marked as a duplicate of this bug. ***
Can this be reproduced with KDE 4.4.X or 4.5?
I'm also using KDE 4.4 (Mandriva 2010.1 Spring) and I don't remember seing a crash similar to this one.
Looks like similar bug in Fedora, see: https://bugzilla.redhat.com/show_bug.cgi?id=583350 It was reproduced with KDE 4.4.5 too.
From bug 251133: - What I was doing when the application crashed: Nepomuk working in the background as normal and crashed. Does it from time to time, esp since I updated to kdelibs 4.5.1 - Updated backtrace (KDE 4.5.1): Thread 1 (Thread 0x7f2d32d44820 (LWP 8688)): [KCrash Handler] #6 0x00000030dda329a5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00000030dda34185 in abort () at abort.c:92 #8 0x00000030dda6fd5b in __libc_message (do_abort=2, fmt=0x30ddb438f8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:186 #9 0x00000030dda75676 in malloc_printerr (action=3, str=0x30ddb418e2 "corrupted double-linked list", ptr=<value optimized out>) at malloc.c:6283 #10 0x00000030dda781a4 in _int_free (av=0x7f2d20000020, p=0x7f2d208b38c0, have_lock=0) at malloc.c:4973 #11 0x00007f2d3572eeec in QString::free (d=0x7f2d208b38d0) at tools/qstring.cpp:1151 #12 0x00007f2d26a51c92 in ~QString (this=<value optimized out>, simple=true) at /usr/include/QtCore/qstring.h:869 #13 Nepomuk::StrigiService::userStatusString (this=<value optimized out>, simple=true) at /usr/src/debug/kdebase-runtime-4.5.1/nepomuk/services/strigi/strigiservice.cpp:184 #14 0x00007f2d26a51d1e in Nepomuk::StrigiService::simpleUserStatusString (this=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.5.1/nepomuk/services/strigi/strigiservice.cpp:163 #15 0x00007f2d26a5c6ac in Nepomuk::SystemTray::slotUpdateStrigiStatus (this=0x1e85db0) at /usr/src/debug/kdebase-runtime-4.5.1/nepomuk/services/strigi/systray.cpp:85 #16 0x00007f2d26a5c812 in Nepomuk::SystemTray::qt_metacall (this=0x1e85db0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7fb25550) at /usr/src/debug/kdebase-runtime-4.5.1/x86_64-redhat-linux-gnu/nepomuk/services/strigi/systray.moc:75
*** Bug 251133 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] From bug 257307: - What I was doing when the application crashed: When I work with KDE, Nepomuk indexes my disk. This takes hours per day with the CPU churning away at highest load with highest temperature (I have never seen my notebook run _this_ hot before). After some hours, nepomuk crashes with the attached backtrace. - Updated backtrace: [KCrash Handler] #7 0xffffe424 in __kernel_vsyscall () #8 0xb6223751 in raise () from /lib/i686/cmov/libc.so.6 #9 0xb6226b82 in abort () from /lib/i686/cmov/libc.so.6 #10 0xb625a18d in ?? () from /lib/i686/cmov/libc.so.6 #11 0xb6264281 in ?? () from /lib/i686/cmov/libc.so.6 #12 0xb6265ad8 in ?? () from /lib/i686/cmov/libc.so.6 #13 0xb6268bbd in free () from /lib/i686/cmov/libc.so.6 #14 0xb76a14dd in qFree (ptr=0xb1b1fd38) at global/qmalloc.cpp:60 #15 0xb76f0ab0 in QString::free (d=0x0) at tools/qstring.cpp:1108 #16 0xb2d9d3a9 in ~QString (this=0x83f8928, simple=true) at /usr/include/qt4/QtCore/qstring.h:869 #17 Nepomuk::StrigiService::userStatusString (this=0x83f8928, simple=true) at ../../../../nepomuk/services/strigi/strigiservice.cpp:184 #18 0xb2d9d3f1 in Nepomuk::StrigiService::simpleUserStatusString (this=0x83f8928) at ../../../../nepomuk/services/strigi/strigiservice.cpp:163 #19 0xb2da9c89 in Nepomuk::SystemTray::slotUpdateStrigiStatus (this=0x8574170) at ../../../../nepomuk/services/strigi/systray.cpp:85
*** Bug 257307 has been marked as a duplicate of this bug. ***
Created attachment 53912 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.1 - Crash happened a couple minutes after login, probably when indexing was complete? -- Backtrace (Reduced): #8 0x05b6300e in qFree (ptr=0xb45cfe08) at global/qmalloc.cpp:60 #9 0x05bb29c1 in QString::free (d=0xb45cfe08) at tools/qstring.cpp:1185 #10 0x0539cd03 in ~QString (this=0x87a0328, simple=true) at /usr/include/QtCore/qstring.h:882 #11 Nepomuk::StrigiService::userStatusString (this=0x87a0328, simple=true) at /usr/src/debug/kdebase-runtime-4.5.3/nepomuk/services/strigi/strigiservice.cpp:160 #12 0x0539cd42 in Nepomuk::StrigiService::simpleUserStatusString (this=0x87a0328) at /usr/src/debug/kdebase-runtime-4.5.3/nepomuk/services/strigi/strigiservice.cpp:152
*** Bug 259288 has been marked as a duplicate of this bug. ***
*** Bug 259408 has been marked as a duplicate of this bug. ***
*** Bug 259885 has been marked as a duplicate of this bug. ***
Created attachment 56221 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.0 - What I was doing when the application crashed: Every time I start KDE Nepomuk automatically begins indexing. It crashes before indexing is complete at intervals between one and five minute from KDE login even when no other desktop activity is taking place. -- Backtrace (Reduced): #14 0x004d5fed in qFree (ptr=0x9d592c0) at global/qmalloc.cpp:60 #15 0x00527180 in QString::free (d=0x0) at tools/qstring.cpp:1151 #16 0x02af4689 in ~QString (this=0x96e5560, simple=true) at /usr/include/qt4/QtCore/qstring.h:882 #17 Nepomuk::StrigiService::userStatusString (this=0x96e5560, simple=true) at ../../../../nepomuk/services/strigi/strigiservice.cpp:173 #18 0x02af46d1 in Nepomuk::StrigiService::simpleUserStatusString (this=0x96e5560) at ../../../../nepomuk/services/strigi/strigiservice.cpp:152
*** Bug 230592 has been marked as a duplicate of this bug. ***
*** Bug 263135 has been marked as a duplicate of this bug. ***
can anyone reproduce this with KDE 4.6?
Nope. Not here.
@thomas: and you had the crash in 4.5?
*** Bug 263914 has been marked as a duplicate of this bug. ***
*** Bug 264078 has been marked as a duplicate of this bug. ***
Created attachment 56806 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1 - What I was doing when the application crashed: The KDE session had just started and the nepomuk was probably indexing. Just before the crash, I had just started firefox and started browsing. Firefox 3.6.13 x86_64 on Fedora 14 -- Backtrace (Reduced): #11 0x0000003f246b797c in QString::free (d=0x7f7910939a30) at tools/qstring.cpp:1185 #12 0x00007f79184786d2 in ~QString (this=<value optimized out>, simple=true) at /usr/include/QtCore/qstring.h:883 #13 Nepomuk::StrigiService::userStatusString (this=<value optimized out>, simple=true) at /usr/src/debug/kdebase-runtime-4.5.5/nepomuk/services/strigi/strigiservice.cpp:160 #14 0x00007f791847875e in Nepomuk::StrigiService::simpleUserStatusString (this=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.5.5/nepomuk/services/strigi/strigiservice.cpp:152 #15 0x00007f7918483bec in Nepomuk::SystemTray::slotUpdateStrigiStatus (this=0x106b020) at /usr/src/debug/kdebase-runtime-4.5.5/nepomuk/services/strigi/systray.cpp:85
[Comment from a bug triager] From bug 267614 (KDE SC 4.5.5): - What I was doing when the application crashed: just booting up - this has happened reliably every day for the last week Dolphin autostarts with 5 tabs Manually start Google Chrome with 41 tabs after 20 -30 mins nepomuk crash notified From bug 267634 (KDE SC 4.5.5): - What I was doing when the application crashed: Just booted, connected to LAN then opened Firefox. I can't tell if it was related to opening Firefox, or just the end of the session opening sequence. Also, this directly follows applying yum updates from stable repositories (right before previous shutdown) Note from Dario: bug 267634 contains more information about the installed packages.
*** Bug 266792 has been marked as a duplicate of this bug. ***
*** Bug 267614 has been marked as a duplicate of this bug. ***
*** Bug 267634 has been marked as a duplicate of this bug. ***
Created attachment 58850 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2 - What I was doing when the application crashed: I've just opened Dolphin when Nepomuk crashed. It has happend most of the times but not always. -- Backtrace (Reduced): #8 0x00007f3519a12d7b in __libc_message (do_abort=2, fmt=0x7f3519afb400 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 #9 0x00007f3519a1ea8f in malloc_printerr (av=<value optimized out>, p=0x7f34fc000d80) at malloc.c:6283 #10 _int_free (av=<value optimized out>, p=0x7f34fc000d80) at malloc.c:4795 #11 0x00007f3519a228e3 in __libc_free (mem=<value optimized out>) at malloc.c:3738 #12 0x00007f351be5fbbf in ~QByteArray (this=0x26f8450, parseOptions=QUrlPrivate::ParseAndSet) at ../../include/QtCore/../../src/corelib/tools/qbytearray.h:383
This is fixed in 4.7 for two reasons: 1. the controller is no longer part of the file indexer service, and 2. the status is now thread-safe.
*** Bug 278932 has been marked as a duplicate of this bug. ***