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

[Björn Tillenius]

Crashed in the background. I didn't interact with the indicator when it happened.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-weather 11.11.28-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x0000000001271530 ***
CrashCounter: 1
Date: Mon Mar 5 16:52:49 2012
ExecutablePath: /usr/bin/indicator-weather
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LC_TIME=en_US.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f3b467e3250 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=3, str=0x7f3b467e0343 "realloc(): invalid pointer", ptr=<optimized out>) at malloc.c:5007
 __GI___libc_realloc (oldmem=0x1271530, bytes=16) at malloc.c:3019
 g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x0000000001271530 ***
UpgradeStatus: Upgraded to precise on 2012-02-21 (12 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare

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