empathy assert failure: *** glibc detected *** empathy: double free or corruption (!prev): 0x08eaf000 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
empathy (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: empathy
I received a message, and instead of clicking on it in the indicator applet, I clicked on Empathy in the launcher, and then on the contact that sent me the message. From this moment, the messages I typed appeared in the notification area like if I received them. Then Empathy crashed.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.34.0-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.38-
NonfreeKernelMo
Architecture: i386
AssertionMessage: *** glibc detected *** empathy: double free or corruption (!prev): 0x08eaf000 ***
CrashCounter: 1
Date: Fri Apr 15 12:04:06 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
ProcCmdline: empathy
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_US:en
LANG=en_US.UTF-8
Signal: 6
SourcePackage: empathy
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
Title: empathy assert failure: *** glibc detected *** empathy: double free or corruption (!prev): 0x08eaf000 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nautilus:1493): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(<unknown>:1472): dee-WARNING **: Transaction from com.canonical.
(<unknown>:1472): dee-WARNING **: Transaction from com.canonical.
(<unknown>:1472): dee-WARNING **: Transaction from com.canonical.
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 #721503, 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.