nepomukservicestub crashed with SIGSEGV in realloc()

[HardyTeam]

Binary package hint: kdebase-runtime

Nepomuk suddenly crashed in Karmic 9.10.
Last action was indexing by strigi.
Never got that team to run by now.

System: Kubuntu Karmic Koala 9.10
Nepomuk version 4.3.2 (KDE)
I expected that nepomuk/strigi would index my files and work.
Instead Dolphin got to work really slow and was better only when I stopped nepomuk (had that before).

The message came up without any action from my side.

ProblemType: Crash
Architecture: i386
Date: Sat Oct 31 18:43:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nepomukservicestub
LiveMediaBuild: Debian GNU/Linux 5.0 r0 "Lenny" - Official Snapshot i386 LIVE Binary 20081013-13:10
NonfreeKernelModules: fglrx
Package: kdebase-runtime 4:4.3.2-0ubuntu4
ProcCmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x58cd123: cmp 0xc(%eax),%esi
 PC (0x058cd123) ok
 source "0xc(%eax)" (0x7500720c) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: kdebase-runtime
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 realloc () from /lib/tls/i686/cmov/libc.so.6
 qRealloc (ptr=0x88ed6d0, size=512) at global/qmalloc.cpp:65
Title: nepomukservicestub crashed with SIGSEGV in realloc()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:malloc_consolidate (av=<value optimized out>)
_int_malloc (av=<value optimized out>,
_int_realloc (av=<value optimized out>, oldp=0x88ed6c8,
*__GI___libc_realloc (oldmem=0x88ed6d0, bytes=512)
qRealloc (ptr=0x88ed6d0, size=512) at global/qmalloc.cpp:65

[Jonathan Thomas (echidnaman)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: http://bugs.kde.org/show_bug.cgi?id=213540
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!