kbuildsycoca4 assert failure: *** glibc detected *** /usr/bin/kbuildsycoca4: corrupted double-linked list: 0x00000000025c9e70 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kde4libs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When I logged in for the second time after having upgraded Kubuntu to Natty, a notification window popped up, and clicking on the icon brought this bug report. When I had logged out the previous time (the first time after the upgrade), clicking on "Leave..." in the pop-up menu on the desktop did not show any shutdown menu at all (no reaction), nor was it possible to leave by clicking the main KDE menu button on the panel and then clicking Quit. Perhaps that provoked the error.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: kdelibs-bin 4:4.6.2-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/
Date: Wed Jun 29 13:35:21 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/bin/
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: kde4libs
StacktraceTop:
raise (sig=6) at ../nptl/
abort () at abort.c:92
__libc_message (do_abort=2, fmt=0x7f6b93baf400 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (action=3, str=0x7f6b93bac5d2 "corrupted double-linked list", ptr=<value optimized out>) at malloc.c:6283
_int_realloc (av=0x7f6b93de91c0, oldp=0x25c9e40, oldsize=<value optimized out>, nb=64) at malloc.c:5285
Title: kbuildsycoca4 assert failure: *** glibc detected *** /usr/bin/
UpgradeStatus: Upgraded to natty on 2011-06-29 (0 days ago)
UserGroups: adm admin cdrom dialout fuse lp lpadmin plugdev pulse pulse-access sambashare ssh sudo video
XsessionErrors: (knotify4:1771): GStreamer-CRITICAL **: gst_debug_
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 #800558, 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.