upowerd assert failure: *** glibc detected *** /usr/lib/upower/upowerd: free(): invalid pointer: 0x08200d98 ***

[Stuart Minchington]

Binary package hint: upower

System = MacBook Pro 5,5 - 2.8GHz Core2Duo - 4GB's RAM

Description = Shortly after plugging in my power supply I saw the error icon in the upper task bar stating that "upowerd" had failed. I acknowledged the error by clicking the "Send a report" button. I didn't have to reboot or quit any other applications to resolve the issue but I have noticed that I no longer have an icon indicating that my battery is charging.

Full Error = upowerd assert failure: *** glibc detected *** /usr/lib/upower/upowerd: free(): invalid pointer: 0x08200d98 ***

Ubuntu version = 10.04 Beta 1 i386

Uname = 2.6.32-18-generic-pae

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: upower 0.9.1-1
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic-pae 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic-pae i686
NonfreeKernelModules: nvidia wl
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/lib/upower/upowerd: free(): invalid pointer: 0x08200d98 ***
CrashCounter: 1
Date: Wed Mar 31 22:02:45 2010
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

Signal: 6
SourcePackage: upower
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: upowerd assert failure: *** glibc detected *** /usr/lib/upower/upowerd: free(): invalid pointer: 0x08200d98 ***
UserGroups:

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