indicator-weather assert failure: *** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x00505968 ***
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| indicator-weather (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
indicator-weather seems to randomly crash...
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x00505968 ***
CrashCounter: 1
Date: Mon Sep 12 20:04:21 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=fr_BE.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
__libc_message (do_abort=2, fmt=0xd43080 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0x505968) at malloc.c:6283
_int_free (av=0xd7f400, p=0x505960) at malloc.c:4795
__GI___libc_free (mem=0x505968) at malloc.c:3738
?? () from /lib/i386-
Title: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x00505968 ***
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
| Olivier Berten (olivier-berten) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
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.