Bug 1240416 - control-center isn't included in ISO install
Summary: control-center isn't included in ISO install
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: Installation - Satellite
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: TP2
: 1.0
Assignee: Jason Montleon
QA Contact: Tasos Papaioannou
Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks: rhci-sprint-11
TreeView+ depends on / blocked
 
Reported: 2015-07-06 20:36 UTC by Matt Reid
Modified: 2019-02-25 17:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-25 17:27:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matt Reid 2015-07-06 20:36:02 UTC
Description of problem:
After installing using RHCI-6.0-RHEL-7-20150630.t.0-RHCI-x86_64-dvd1.iso, when I went to try and change the resolution of the system, I discovered that control-center wasn't installed. When I tried to open the Settings dialog from the Gnome User applet, nothing happened after clicking on Settings...

I realize we're trying to keep the install minimal, but can we include something basic like control-center in the install? If we're installing and providing a desktop environment, it'd be nice to be able to easily configure it. Especially since the Gnome Classic environment still includes a menu entry for it in the user applet, regardless of if it is installed or not.

Version-Release number of selected component (if applicable):
RHCI-6.0-RHEL-7-20150630.t.0-RHCI-x86_64-dvd1.iso

How reproducible:
100%

Steps to Reproduce:
1. Install using ISO
2. Click username
3. Click Settings

Actual results:
Nothing happens

Expected results:
Gnome Control Center to open

Additional info:

Comment 1 Tasos Papaioannou 2016-01-08 21:23:12 UTC
VERIFIED on RHCI-6.0-RHEL-7-20160107.t.1

Comment 2 Sudhir Mallamprabhakara 2019-02-25 17:27:19 UTC
QCI has sunset. Closing the BZ's.


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