Bug 1042794 - Red Hat branding in Anaconda is partially missing
Summary: Red Hat branding in Anaconda is partially missing
Keywords:
Status: CLOSED DUPLICATE of bug 1049655
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: redhat-logos
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.0
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 994043
TreeView+ depends on / blocked
 
Reported: 2013-12-13 12:14 UTC by Martin
Modified: 2014-09-15 00:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-14 15:23:33 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Martin 2013-12-13 12:14:27 UTC
Description of problem:
Red Hat branding in Anaconda is partially missing.

Version-Release number of selected component (if applicable):
RHEL-7.0-20131127.1-Workstation-x86_64

How reproducible:
always

Steps to Reproduce:
Boot to Anaconda and begin RHEL7 installation.

Actual results:
No Red Hat artwork during installation, except "Red Hat Enterprise Linux 7.0" string.

Expected results:
Red Hat artwork e.g. logo should be included.

Additional info:
From Branding Documentation:
The most significant of these are the images that cycle along the bottom of the screen while packages are installing.  These are provided by the system-logos package - fedora-logos for Fedora, and redhat-logos for RHEL.  Any images placed into /usr/share/anaconda/pixmaps/rnotes or /usr/share/anaconda/pixmaps/rnotes/<lang> will be cycled through, approximately one per minute, during installation.

Comment 2 David Shea 2013-12-17 15:43:14 UTC
Anaconda will display the images once they've been provided in /usr/share/anaconda/pixmaps/rnotes.

Comment 3 Bill Nottingham 2014-01-14 15:20:50 UTC
Dup of 1049655?

Comment 4 David Shea 2014-01-14 15:23:33 UTC
Yeah, the images are in redhat-logos now

*** This bug has been marked as a duplicate of bug 1049655 ***


Note You need to log in before you can comment on or make changes to this bug.