indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_id()

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

Bug Description

Random crash after no particular action.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-weather 11.11.28-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 9 19:20:24 2012
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
SegvAnalysis:
 Segfault happened at: 0x7fe9d007b95a <dbusmenu_menuitem_get_id+26>: cmp %rax,(%rdx)
 PC (0x7fe9d007b95a) ok
 source "%rax" ok
 destination "(%rdx)" (0x6f6d2e7265) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 dbusmenu_menuitem_get_id () 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
 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :
visibility: private → public
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 this software 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.

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.