dconf-service assert failure: *** glibc detected *** /usr/lib/d-conf/dconf-service: free(): invalid next size (fast): 0x09a6eeb8 ***

[Jon "The Nice Guy" Spriggs]

I'm very sorry, I don't know why I've received this error message, but it happened after running an update against Maverick today.

As requested, here is the results of my lsb_release and apt-cache policy commands:

spriggsj@spriggsj-laptop:~$ lsb_release -rd && apt-cache policy dconf
Description: Ubuntu maverick (development branch)
Release: 10.10
dconf:
  Installed: (none)
  Candidate: 0.5.1-2
  Version table:
     0.5.1-2 0
        500 http://gb.archive.ubuntu.com/ubuntu/ maverick/universe Packages

Please let me know if you need more data.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: libdconf0 0.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Uname: Linux 2.6.35-7-generic i686
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/lib/d-conf/dconf-service: free(): invalid next size (fast): 0x09a6eeb8 ***
Date: Mon Jul 12 20:23:45 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/d-conf/dconf-service
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Alpha i386 (20100630.1)
ProcCmdline: /usr/lib/d-conf/dconf-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
Signal: 6
SourcePackage: d-conf
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
Title: dconf-service assert failure: *** glibc detected *** /usr/lib/d-conf/dconf-service: free(): invalid next size (fast): 0x09a6eeb8 ***
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #603226, 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.