indicator-application-service assert failure: *** glibc detected *** /usr/lib/indicator-application/indicator-application-service: double free or corruption (fasttop): 0x08d4a238 ***

[Andy Duffell]

Binary package hint: indicator-application

This crash is occurring consistently shortly after login on my Eee PC 1000HG running Unity on Maverick. I'm also consistently getting telepathy-butterfly crashing (bug 665517), don't know whether this related, but they both crash about the same time.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-application 0.2.9-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/lib/indicator-application/indicator-application-service: double free or corruption (fasttop): 0x08d4a238 ***
CrashCounter: 1
Date: Thu Oct 28 10:22:40 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/indicator-application/indicator-application-service
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/indicator-application/indicator-application-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.utf8
Signal: 6
SourcePackage: indicator-application
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: indicator-application-service assert failure: *** glibc detected *** /usr/lib/indicator-application/indicator-application-service: double free or corruption (fasttop): 0x08d4a238 ***
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

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