indicator-weather crashed with SIGSEGV in g_atomic_int_get()

Bug #746361 reported by Lucian Adrian Grijincu
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
indicator-weather (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: indicator-weather

I have Paris - France, Bucharest - Romania and Suceava - Romania as locations.
After upgrading today to 11.03.27+repack-0ubuntu1 I set source to Yahoo, rather than Google.

I changed the location: initially it was Paris, then I set it to Bucharest, and tried to set it to Suceava, but that didn't work, so I tried again and still did not work.

I selected "Preferenes" (wanted to set it back to Google, maybe Google knows about Suceava), but after pressing "Preferences" the app crashed and apport collected info for this report.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-weather 11.03.27+repack-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Thu Mar 31 12:49:07 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110326)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LANGUAGE=ro_RO:en
 LANG=ro_RO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x77540c <g_atomic_int_get+12>: mov (%eax),%eax
 PC (0x0077540c) ok
 source "(%eax)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 g_atomic_int_get () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: indicator-weather crashed with SIGSEGV in g_atomic_int_get()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Lucian Adrian Grijincu (lucian.grijincu) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_atomic_int_get (atomic=0x28) at /build/buildd/glib2.0-2.28.4/./glib/gatomic-gcc.c:64
 g_bit_lock (address=0x28, lock_bit=0) at /build/buildd/glib2.0-2.28.4/./glib/gbitlock.c:211
 g_variant_lock (value=<value optimized out>) at /build/buildd/glib2.0-2.28.4/./glib/gvariant-core.c:221
 g_variant_ref_sink (value=0x18) at /build/buildd/glib2.0-2.28.4/./glib/gvariant-core.c:687
 g_variant_new_variant (value=0x18) at /build/buildd/glib2.0-2.28.4/./glib/gvariant.c:686

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-weather (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-weather (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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