Bug 123554 - In kickstart installation GNOME and KDE group names are different from COMPS.XML
In kickstart installation GNOME and KDE group names are different from COMPS.XML
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
2
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jeremy Katz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-19 07:28 EDT by Greg
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-07 14:15:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Greg 2004-05-19 07:28:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040207 Firefox/0.8

Description of problem:
Hi,

I've tried to install FC2 release using KICKSTART. After first install
i had anaconda-ks.cfg file with both KDE and GNOME as follows:

#@ GNOME Desktop Environment
@ GNOME Desktop
#@ KDE Desktop Environment
@ KDE (K Desktop Environment)

(commented lines are what i received and not commented were found
after cheating in COMPS.XML).

Thanks,
Greg



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


How reproducible:
Always

Steps to Reproduce:
1. Install FC2 with KDE and GNOME
2. Copy anaconda-ks.cfg to another computer 
3. Perform NFS install with ks=... pointing to anaconda-ks.cfg
4. During install anaconda will tell you that GNOME and KDE are
something like not available (continue / abort ?)
    

Additional info:
Comment 1 Luc Lalonde 2004-07-05 12:52:32 EDT
I can confirm and reproduce this problem.
Comment 2 Jeremy Katz 2004-10-07 14:15:31 EDT
There are a couple of aliases for this as the displayed name has
changed over time.  In anaconda-ks.cfg, I canonicalize things somewhat.

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