indicator-weather crashed with SIGABRT in raise()

Bug #857505 reported by herr.larsson
84
This bug affects 12 people
Affects Status Importance Assigned to Milestone
indicator-weather (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

it crashes

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 23 17:29:36 2011
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110920.5)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-weather
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: indicator-weather crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
herr.larsson (herr.larsson) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f8aec402bc0 "append_value_to_blob", message=0x32b7db0 "assertion failed: (g_utf8_validate (v, -1, &end) && (end == v + len))") at /build/buildd/glib2.0-2.29.92/./glib/gtestutils.c:1425
 g_assertion_message_expr (domain=0x7f8aec3e0701 "GLib-GIO", file=0x7f8aec401ad8 "/build/buildd/glib2.0-2.29.92/./gio/gdbusmessage.c", line=1986, func=0x7f8aec402bc0 "append_value_to_blob", expr=<optimized out>) at /build/buildd/glib2.0-2.29.92/./glib/gtestutils.c:1436
 append_value_to_blob (value=<optimized out>, type=0x7f8aec91ee62, mos=0x326d000, dos=0x31d5060, out_padding_added=0x0, error=0x7fff57f96248) at /build/buildd/glib2.0-2.29.92/./gio/gdbusmessage.c:1986
 append_body_to_blob (error=0x7fff57f96248, dos=0x31d5060, mos=0x326d000, value=<optimized out>) at /build/buildd/glib2.0-2.29.92/./gio/gdbusmessage.c:2200
 g_dbus_message_to_blob (message=<optimized out>, out_size=0x7fff57f96168, capabilities=<optimized out>, error=0x7fff57f96248) at /build/buildd/glib2.0-2.29.92/./gio/gdbusmessage.c:2371

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-amd64-retrace
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
Daniel Hahler (blueyed)
visibility: private → public
Changed in indicator-weather (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
MB (blitzko) wrote :

indicator-weather continues to crash, somewhat randomly (meaning I don't see a pattern), on my recently upgraded to Ubuntu 12.04 system, just as it did when it was 11.10.

tags: added: precise
tags: added: quantal
tags: added: qa-manual-testing
Para Siva (psivaa)
tags: added: rls-q-incoming
tags: added: rls-q-notfixing
removed: rls-q-incoming
Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

Considering the rarity of this error I suspect it is caused by a web service timing out or returning unexpected data.

Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

After closer inspection it looks like this, and many of the other crashes in this indicator, are caused by a race condition in the threading code. The crash always seems to happen while updating self.refresh_show, which apparently gets deleted and recreated from a different callback on a separate gobject timeout.

Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

I fully disabled one of the threads and it still crashes all over the place so I have no idea what is wrong...

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.