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

[Nicolas DERIVE]

Crash during a refresh.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic-pae 3.0.1
Uname: Linux 3.0.0-8-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/python: double free or corruption (out): 0xade14000 ***
CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912
CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e
Date: Sat Aug 13 18:38:30 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/indicator-weather
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 LANGUAGE=fr_FR:fr:en_GB:en
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
 __libc_message (do_abort=2, fmt=0xb75d2ea0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0xade14000) at malloc.c:6283
 _int_free (av=0xb760f400, p=0xade13ff8) at malloc.c:4795
 __GI___libc_free (mem=0xade14000) at malloc.c:3738
 standard_free (mem=0xade14000) at /build/buildd/glib2.0-2.29.14/./glib/gmem.c:101
Title: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: double free or corruption (out): 0xade14000 ***
UpgradeStatus: Upgraded to oneiric on 2008-10-18 (1029 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users 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 #741759, 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.