kbuildsycoca4 assert failure: *** glibc detected *** /usr/bin/kbuildsycoca4: malloc(): memory corruption (fast): 0x0957c318 ***

[[e-mail]]

mala actualizacion de ubuntu 10.10 a ubuntu 11.04

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: kdelibs-bin 4:4.6.2-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-10.44-generic-pae 2.6.38.7
Uname: Linux 2.6.38-10-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/kbuildsycoca4: malloc(): memory corruption (fast): 0x0957c318 ***
Date: Thu Jun 16 12:56:34 2011
ExecutablePath: /usr/bin/kbuildsycoca4
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/bin/kbuildsycoca4 --incremental
ProcEnviron:
 LANG=es_ES.utf8
 SHELL=/bin/bash
 LANGUAGE=
Signal: 6
SourcePackage: kde4libs
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
Title: kbuildsycoca4 assert failure: *** glibc detected *** /usr/bin/kbuildsycoca4: malloc(): memory corruption (fast): 0x0957c318 ***
UpgradeStatus: Upgraded to natty on 2011-06-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (<unknown>:1604): Gdk-WARNING **: /build/buildd/gtk+2.0-2.24.4/gdk/x11/gdkdrawable-x11.c:942 drawable is not a native X11 window
 (<unknown>:1604): Gdk-WARNING **: /build/buildd/gtk+2.0-2.24.4/gdk/x11/gdkdrawable-x11.c:942 drawable is not a native X11 window
 (<unknown>:1604): Gdk-WARNING **: /build/buildd/gtk+2.0-2.24.4/gdk/x11/gdkdrawable-x11.c:942 drawable is not a native X11 window

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #791714, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.