indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_id()

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

Bug Description

fix it already

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2.1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Wed Nov 9 20:51:51 2011
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0f63ac572a <dbusmenu_menuitem_get_id+26>: cmp %rax,(%rdx)
 PC (0x7f0f63ac572a) ok
 source "%rax" ok
 destination "(%rdx)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 dbusmenu_menuitem_get_id () from /usr/lib/libdbusmenu-glib.so.4
 ?? () from /usr/lib/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
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_id()
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (26 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Brian Helfrich (brianhelfrich) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #742824, 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-amd64-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.