Bug 205888

Summary:	GRUB menu selection not visible with new color scheme
Product:	[Fedora] Fedora	Reporter:	Jurgen Kramer <gtmkramer>
Component:	fedora-logos	Assignee:	David Cantrell <dcantrell>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	alan, matthias, tmraz
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-09-27 03:41:21 UTC	Type:	---
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:	150224

Description Jurgen Kramer 2006-09-09 15:56:30 UTC

Description of problem:
With the new color scheme the highlight entry in the GRUB menu is not clearly
visible as being highlighted.

Version-Release number of selected component (if applicable):
redhat-artwork-5.0.4-2.fc6

How reproducible:
always

Steps to Reproduce:
1. Press a key when GRUB appears
2. Try to make boot selection with cursus keys
3.
  
Actual results:
Selected boot option not cleary marked due to color scheme

Expected results:
Selected boot option clearly marked and visible

Additional info:

Comment 1 Mike Chambers 2006-09-14 01:04:14 UTC

Yes agree, the highlighted bar from grub blended with the grub background
conflicts.  If the background stays, then the highlight/font colors should be
lot brighter and blend in better.

Comment 2 Thorsten Leemhuis 2006-09-17 08:26:07 UTC

maybe a dupe of 205820

Comment 3 Vallimar 2006-09-18 14:53:45 UTC

The correct component is: fedora-logos
Someone should correct that.

Comment 4 Peter Jones 2006-09-26 20:27:22 UTC

*** Bug 205820 has been marked as a duplicate of this bug. ***

Comment 5 Matthias Clasen 2006-09-27 03:41:21 UTC

This has been fixed in the latest artwork updates

Comment 6 Peter Jones 2006-09-27 22:08:36 UTC

*** Bug 206347 has been marked as a duplicate of this bug. ***