indicator-weather assert failure: *** glibc detected *** /usr/bin/python: double free or corruption (fasttop): 0x00000000014ea8a0 ***

[Patrik Lundquist]

n/a

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/python: double free or corruption (fasttop): 0x00000000014ea8a0 ***
CheckboxSubmission: 22d2482f3d97d99d3e4e64bcfe8e3622
CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d
CrashCounter: 1
Date: Mon Sep 12 18:11:23 2011
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:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f7b7b6190d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7f7b7b619210 "double free or corruption (fasttop)", ptr=<optimized out>) at malloc.c:6283
 _int_realloc (av=0x7f7b7b8541c0, oldp=0x14ea890, oldsize=32, nb=<optimized out>) at malloc.c:5341
 __GI___libc_realloc (oldmem=0x14ea8a0, bytes=32) at malloc.c:3821
 g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: double free or corruption (fasttop): 0x00000000014ea8a0 ***
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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