indicator-weather crashed with SIGSEGV in g_type_check_instance_cast()

Bug #1032610 reported by Jared
218
This bug affects 51 people
Affects Status Importance Assigned to Milestone
Weather Indicator
New
Undecided
Unassigned

Bug Description

Weather Indicator was just running normally in the background and crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-weather 12.07.30~precise1 [origin: LP-PPA-weather-indicator-team]
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic i686
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
CrashCounter: 1
CrashDB: indicator_weather
Date: Thu Aug 2 18:46:25 2012
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
SegvAnalysis:
 Segfault happened at: 0x968c18 <g_type_check_instance_cast+56>: mov (%eax),%ebp
 PC (0x00968c18) ok
 source "(%eax)" (0x6562616c) not located in a known VMA region (needed readable region)!
 destination "%ebp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4
 ?? () from /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
ThirdParty: True
Title: indicator-weather crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to precise on 2012-04-19 (106 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jared (jared-vanvolkenburg) wrote :
security vulnerability: no → yes
visibility: private → public
security vulnerability: yes → no
Revision history for this message
Alberto Pérez Murado (partisan0) wrote :

Unassigned since (almost) 2 months ago? :O

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.