indicator-weather assert failure: *** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x00007f0e083c7dd0 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-weather (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
indicator-weather assert failure: *** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x00007f0e083c7dd0 ***
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelMo
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x00007f0e083c7dd0 ***
CrashCounter: 1
Date: Fri Sep 9 15:09:11 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
__libc_message (do_abort=2, fmt=0x7f0e094560d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (action=3, str=0x7f0e094530ef "free(): invalid pointer", ptr=<optimized out>) at malloc.c:6283
__GI___libc_free (mem=<optimized out>) at malloc.c:3738
g_array_free () from /lib/x86_
?? () from /usr/lib/
Title: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x00007f0e083c7dd0 ***
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (7 days ago)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare
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 #747183, 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.