indicator-weather crashed with SIGSEGV in g_array_free()

Bug #1179232 reported by Sergey
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Weather Indicator
New
Undecided
Unassigned

Bug Description

Randomly crashes with no apparent reason.
Seems to be alike #1017444 and #1063643, but on Ubuntu 13.04.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-weather 12.07.30-0ubuntu1.1 [origin: unknown]
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CrashCounter: 1
CrashDB: indicator_weather
Date: Sun May 12 18:53:36 2013
ExecutablePath: /usr/bin/indicator-weather
InstallationDate: Installed on 2013-02-24 (77 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1ce252d885 <g_array_free+21>: lock cmpxchg %ecx,0x18(%rdi)
 PC (0x7f1ce252d885) ok
 source "%ecx" ok
 destination "0x18(%rdi)" (0x7f1cd5338b48) in non-writable VMA region: 0x7f1cd532c000-0x7f1cd5346000 r-xp /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4.0.12
SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4.0.12
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 g_array_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
ThirdParty: True
Title: indicator-weather crashed with SIGSEGV in g_array_free()
UpgradeStatus: Upgraded to raring on 2013-05-02 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Sergey (kazenyuk) wrote :
Sergey (kazenyuk)
information type: Private → Public
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.