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

[Jan Groenewald]

Nope, nothing further.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-weather 11.11.28-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x0000000001604ea0 ***
CrashCounter: 1
Date: Wed Feb 29 14:11:54 2012
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111130.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f50fec41250 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=3, str=0x7f50fec3e343 "realloc(): invalid pointer", ptr=<optimized out>) at malloc.c:5007
 __GI___libc_realloc (oldmem=0x1604ea0, 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: 0x0000000001604ea0 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo

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