indicator-weather crashed with SIGSEGV in g_variant_ref_sink()

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

Bug Description

i don't know what's happening...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-weather 11.11.28-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Tue Apr 17 17:34:18 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
ProcEnviron:
 LANGUAGE=pt_BR:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6fa61ce <g_variant_ref_sink+30>: mov 0x14(%esi),%ecx
 PC (0xb6fa61ce) ok
 source "0x14(%esi)" (0x0000001b) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 g_variant_ref_sink () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_new_variant () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () 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
Title: indicator-weather crashed with SIGSEGV in g_variant_ref_sink()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin sambashare sudo

Revision history for this message
Silvon Tavares (silvon-tavares) 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 #916715, 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-i386-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.