indicator-weather crashed with SIGSEGV in g_variant_builder_add_value()

Bug #762573 reported by Gerad Munsch
202
This bug affects 46 people
Affects Status Importance Assigned to Milestone
Application Indicators
Invalid
Undecided
Unassigned
Weather Indicator
Invalid
Undecided
Unassigned
indicator-weather (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: indicator-weather

Randomly crashed. Could be caused due to poor connectivity issues (my connection is loaded with packet loss).

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-weather 11.04.10+repack-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sat Apr 16 04:38:08 2011
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc31708db42: testb $0x4,0x20(%rdi)
 PC (0x7fc31708db42) ok
 source "$0x4" ok
 destination "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: indicator-weather crashed with SIGSEGV in g_variant_builder_add_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Gerad Munsch (unforgiven512) wrote :
Changed in weather-indicator:
status: New → Invalid
Changed in indicator-weather (Ubuntu):
status: New → Invalid
Revision history for this message
Ted Gould (ted) wrote :

Unfortunately it seems that our automated retracer was unable to retrace this bug. Which means we can't get the information we need from it. If you get this error again please resubmit so that we can track it down. Thanks!

Changed in indicator-application:
status: New → Invalid
Revision history for this message
Dave Vree (hdave) wrote :

Any chance you can delete this entire report so that new reports won't accidently select it when reporting?

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.