Weather indicator crashed: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: malloc(): smallbin double linked list corrupted: 0x09f18cc8 ***

[Marcin Sulikowski]

When I unlocked the screen I noticed the crash information. Indicator was set to show weather in Warsaw.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/python: malloc(): smallbin double linked list corrupted: 0x09f18cc8 ***
Date: Wed Oct 19 19:49:31 2011
ExecutablePath: /usr/bin/indicator-weather
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LANGUAGE=pl_PL:pl:en_GB:en
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
 __libc_message (do_abort=2, fmt=0xa79080 "*** 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=0x9f18cc8) at malloc.c:6283
 _int_malloc (av=0xab5400, bytes=64) at malloc.c:4308
 __libc_calloc (n=1, elem_size=64) at malloc.c:4065
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: malloc(): smallbin double linked list corrupted: 0x09f18cc8 ***
UpgradeStatus: Upgraded to oneiric on 2011-10-15 (4 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy fuse lp lpadmin netdev plugdev sambashare 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 #746386, 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.