Bug 1083313

Summary:	Outdated help documentation (for v2.2, software is v3.8.2.1)
Product:	Red Hat Enterprise Linux 7	Reporter:	Steve Bonneville <sbonnevi>
Component:	gnome-system-monitor	Assignee:	David King <dking>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	vbenes, vhumpa
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gnome-system-monitor-3.14.1-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 07:24:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1174566

Description Steve Bonneville 2014-04-01 22:39:45 UTC

Description of problem:

The yelp help documentation for gnome-system-monitor references v2.2, and is out of date.  For example, discussion on how to open Preferences says to select "Edit -> Preferences" even though there's no Edit menu anymore...says that the tool can be started from the GNOME System -> Administration -> System Monitor menu that no longer exists, etc....  The screenshot provided at the "Getting Started" link is from GNOME 2, implies View is a menu item and not a button on the right, and so on.

Version-Release number of selected component (if applicable):

gnome-system-monitor-3.8.2.1-5.el7.x86_64

Steps to Reproduce:
1. Run gnome-system-monitor
2. From the top bar, select "System Monitor" -> Help

Comment 2 RHEL Program Management 2014-04-09 05:47:12 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 errata-xmlrpc 2015-11-19 07:24:03 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2215.html