Red Hat Bugzilla – Bug 110808
Anaconda erroneously attempts VNC Installation
Last modified: 2007-11-30 17:06:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
Description of problem:
In a Kickstarted installation, if 'vnc' is listed in the individual
packages section of the kickstart file Anaconda will start the VNC
server for installation instead of the X server.
This occurs even when networking has not been configured. The VNC
server is also started without a password.
If 'vnc' is no longer a valid package an error should be given that
the package does not exist.
The boot line used to start the installation is "linux
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a kickstart file with 'vnc' listed in the invidual packages
2. Boot the computer and start an installation using the kickstart file
Actual Results: Anaconda starts the VNC server for installation,
instead of the X server.
Expected Results: Anaconda should have started the X server for
installation, and then given an error that the package 'vnc' does not
exist if that package has been removed.
This was not a problem with RHL 9.0 (Shrike).
This is queued to be fixed in the first update.
*** This bug has been marked as a duplicate of 105789 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.