empathy assert failure: *** glibc detected *** empathy: double free or corruption (out): 0x0000000000e4b720 ***

[spaetz]

Just clicking on the edit button on a contact.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
AssertionMessage: *** glibc detected *** empathy: double free or corruption (out): 0x0000000000e4b720 ***
CrashCounter: 1
Date: Tue Jan 3 11:19:54 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: empathy
ProcEnviron:
 LC_CTYPE=en_US.UTF8
 PATH=(custom, user)
 LANG=en_US.UTF8
 SHELL=/bin/bash
Signal: 6
SourcePackage: empathy
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f7a0aa760b8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7f7a0aa76238 "double free or corruption (out)", ptr=<optimized out>) at malloc.c:6283
 __GI___libc_free (mem=<optimized out>) at malloc.c:3738
 empathy_groups_widget_set_group_details ()
 empathy_individual_widget_set_individual ()
Title: empathy assert failure: *** glibc detected *** empathy: double free or corruption (out): 0x0000000000e4b720 ***
UpgradeStatus: Upgraded to precise on 2011-12-20 (13 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare src voice

[spaetz (spaetz)]

P.S. when repeating the action, the "group selector" showed lots of bogus group names, such as unreadable chars (binary crap), and "fg_foreground_color", "fg_background_color", etc. (this are certainly NOT valid group names)

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #808600, 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.