Bug 740264 - VNC install boots into runlevel 3
Summary: VNC install boots into runlevel 3
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F16Beta, F16BetaBlocker
TreeView+ depends on / blocked
Reported: 2011-09-21 13:37 UTC by Kamil Páral
Modified: 2011-09-21 15:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-09-21 14:09:10 UTC

Attachments (Terms of Use)

Description Kamil Páral 2011-09-21 13:37:26 UTC
Description of problem:
I tried to install Fedora 16 RC1 DVD i686 with updates and updates-testing repositories enabled, all defaults. When doing standard installation, computer correctly starts in runlevel 5. But when doing the same installation over VNC, computer starts in runlevel 3 (/etc/systemd/system/default.target is symlinked to runlevel3.target).

Expected behavior is getting the same configuration as in non-VNC install.

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

How reproducible:

Steps to Reproduce:
1. https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_VNC
2. boots into runlevel 3, should into 5

Comment 1 Kamil Páral 2011-09-21 13:39:30 UTC
Proposing for Beta blocker:

In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account

Comment 2 Chris Lumens 2011-09-21 14:09:10 UTC
A VNC install gets you runlevel 3 by default, so this is not a bug.

Comment 3 Kamil Páral 2011-09-21 15:36:01 UTC
Ouch. Sorry for the noise. I'll amend our test cases to point that out.

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