Bug 702762

Summary:	GDM 3.0 uses wrong shutdown icon if 'gnome-themes' 2.32 is installed
Product:	Red Hat Enterprise Linux 6	Reporter:	John T. Folden <john.t.folden>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 10:18:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description John T. Folden 2011-05-06 21:15:54 UTC

Description of problem:
The installation of fedora-icon-theme noarch 1.0.0-10.fc15 @updates-testing pulls in gnome-themes noarch 2.32.0-6.fc15 as a dependency. Once gnome-themes is installed the shutdown button in the top right of the GDM 3.0 screen no longer uses its normal symbolic icon, instead using a generic blue computer.

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

How reproducible:
100%

Steps to Reproduce:
1. Install fedora-icon-theme & gnome-themes
2. reboot
3. See incorrect shutdown icon on GDM screen.
  
Actual results:
The shutdown icon is a generic computer

Expected results:
The shutdown icon should be a symbolic image in line with other graphics used through out Gnome 3.

Additional info:
As a temporary workaround, downgrading to fedora-icon-theme noarch 1.0.0-9.fc15 and removing gnome-themes corrects this issue.

Comment 2 RHEL Program Management 2011-05-06 21:47:38 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 John T. Folden 2011-05-06 21:55:28 UTC

Opps, this was my first bug report and while I chose GDM correctly as the component, the product should have been Fedora rather than RHEL. Apologies...

Can the product be changed or must a new report be entered?

Comment 4 Suzanne Logcher 2011-10-06 18:49:59 UTC

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
               
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 5 Jan Kurik 2017-12-06 10:18:34 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/