gconfd-2 crashed with SIGABRT in __kernel_vsyscall()

[Michel]

at the end of an upgrade process via aptitude, extract of /var/log/aptitude:
===
sam., oct. 29 2011 06:37:47 +0200

IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.

Will install 5 packages, and remove 0 packages.
12,3 kB of disk space will be used
=========================================
[UPGRADE] empathy 3.2.0.1-0ubuntu1 -> 3.2.0.1-0ubuntu1.1
[UPGRADE] empathy-common 3.2.0.1-0ubuntu1 -> 3.2.0.1-0ubuntu1.1
[UPGRADE] nautilus-sendto-empathy 3.2.0.1-0ubuntu1 -> 3.2.0.1-0ubuntu1.1
[UPGRADE] tzdata 2011l-0ubuntu0.11.10 -> 2011m-0ubuntu0.11.10
[UPGRADE] tzdata-java 2011l-0ubuntu0.11.10 -> 2011m-0ubuntu0.11.10
===========================================

popup about crash of gconf2

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libgconf2-4 3.2.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
Uname: Linux 3.0.0-13-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Sat Oct 29 06:38:24 2011
ExecutablePath: /usr/lib/libgconf2-4/gconfd-2
ProcCmdline: /usr/lib/libgconf2-4/gconfd-2
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=fr_FR:fr:en_GB:en
 LANG=fr_FR.UTF-8
Signal: 6
SourcePackage: gconf
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 gconf_database_set_sources ()
Title: gconfd-2 crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to oneiric on 2011-10-16 (12 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse gdm kqemu lightdm lpadmin netdev plugdev powerdev pulse pulse-access scanner tape users video www-data

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

[Michel (michel-mno)]

would be interesting to have access to https://bugs.launchpad.net/bugs/882525, that is private for the moment and so not accessible to me.