indicator-weather assert failure: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x0000000002203d80 ***

[Ted Gould]

Crashed in the background. I'm guessing it was doing an update.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x0000000002203d80 ***
Date: Wed Jul 13 15:28:54 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x7f9668eed718 "*** glibc detecusername *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7f9668eeaa47 "realloc(): invalid pointer", ptr=<value optimized out>) at malloc.c:6283
 __libc_realloc (oldmem=0x2203d80, bytes=16) at malloc.c:3778
Title: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x0000000002203d80 ***
UpgradeStatus: Upgraded to oneiric on 2011-06-17 (26 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd 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 #765397, 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.