indicator-weather crashed with SIGSEGV in __GI___libc_free()

Bug #905802 reported by Marian
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-weather (Ubuntu)
New
Undecided
Unassigned

Bug Description

I did nothing special (executing maven in a console) then suddenly the message appeared.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2.1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Dec 17 21:51:39 2011
ExecutablePath: /usr/bin/indicator-weather
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
SegvAnalysis:
 Segfault happened at: 0x7f413139ed29 <__GI___libc_free+25>: mov -0x8(%rdi),%rax
 PC (0x7f413139ed29) ok
 source "-0x8(%rdi)" (0x5441554156415739) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 __GI___libc_free (mem=0x5441554156415741) at malloc.c:3709
 g_array_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libdbusmenu-glib.so.4
 ?? () from /usr/lib/libdbusmenu-glib.so.4
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: indicator-weather crashed with SIGSEGV in __GI___libc_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers video

Revision history for this message
Marian (mnion) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #828743, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.