Bug 730926 - system halts at reboot after install with vnc
Summary: system halts at reboot after install with vnc
Status: CLOSED DUPLICATE of bug 737118
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
: 738944 (view as bug list)
Depends On:
Blocks: F16Beta, F16BetaBlocker
TreeView+ depends on / blocked
Reported: 2011-08-16 09:23 UTC by Hongqing Yang
Modified: 2011-09-21 10:03 UTC (History)
7 users (show)

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

Attachments (Terms of Use)
screenshot (16.27 KB, image/png)
2011-08-16 09:23 UTC, Hongqing Yang
no flags Details
screenshot (1.36 KB, image/png)
2011-08-16 09:23 UTC, Hongqing Yang
no flags Details
anaconda logs (380.00 KB, application/x-tar)
2011-08-16 09:29 UTC, Hongqing Yang
no flags Details
boot messages (29.49 KB, text/plain)
2011-09-20 06:27 UTC, Kamil Páral
no flags Details
boot messages with systemd debug (125.88 KB, text/plain)
2011-09-20 06:56 UTC, Kamil Páral
no flags Details

Description Hongqing Yang 2011-08-16 09:23:04 UTC
Created attachment 518443 [details]

Description of problem:
refer test case:https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_VNC_Vncconnect

reboot system after installation with vnc, the system halts, whatever enforcing=0 or not. i386 and x86_64 are both tested.

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

How reproducible:


Steps to Reproduce:
1. install system with vnc
2. reboot after installation
Actual results:

system halts, whatever enforcing=0 or not

Expected results:

Additional info:

Comment 1 Hongqing Yang 2011-08-16 09:23:35 UTC
Created attachment 518444 [details]

Comment 2 Hongqing Yang 2011-08-16 09:29:53 UTC
Created attachment 518445 [details]
anaconda logs

Comment 3 Hongqing Yang 2011-08-17 05:43:25 UTC
reproduced on f16-alpha-rc5,  the it works well with minimal install

Comment 4 Hongqing Yang 2011-09-13 03:24:26 UTC
reproduced on f16-beta-tc2

Comment 5 Hongqing Yang 2011-09-16 04:58:34 UTC
reproduced on f16-beta-rc1

Comment 6 Adam Williamson 2011-09-20 01:43:38 UTC
why was this not proposed as a blocker bug? it seems to be one according to the alpha criteria.

Comment 7 Kamil Páral 2011-09-20 06:26:38 UTC
Reproduced with F16 Beta RC1 i686. Minimal install works, but default install doesn't boot. Proposing as 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 8 Kamil Páral 2011-09-20 06:27:11 UTC
Created attachment 523957 [details]
boot messages

Comment 9 Adam Williamson 2011-09-20 06:33:16 UTC
kamil: the other criterion to cite is "The installer must be able to complete an installation using the text, graphical and VNC installation interfaces " (Alpha) - the two together make this blocker, I think.

Comment 10 Kamil Páral 2011-09-20 06:56:52 UTC
Created attachment 523959 [details]
boot messages with systemd debug

adamw: Well, it _completed_ the installation, it just doesn't boot afterwards :-) I wasn't sure whether it covers that or not.

Attaching logs with systemd.log_level=debug. Heavy output warning!

Comment 11 Martin Gracik 2011-09-20 07:52:15 UTC
I think this is duplicate of bug #737118

Can you please retest with the latest release?

Comment 12 Kamil Páral 2011-09-20 09:07:39 UTC
(In reply to comment #11)
> I think this is duplicate of bug #737118

I just skimmed through the comments, but this bug seems to be happening also for runlevel 5, not just 3.

> Can you please retest with the latest release?

Latest release of anaconda? In that case we will probably have to wait for F16 Beta RC2.

Comment 13 Martin Gracik 2011-09-20 09:15:33 UTC
In the screenshot, one of the last messages is running /usr/bin/setup. That is run only in text-mode. So I suspect it's the same problem.

No need for latest anaconda, if what I'm saying is right, latest firstboot is enough, that is firstboot-16.4-1

Comment 14 Kamil Páral 2011-09-20 09:23:57 UTC
Do we have some compose ready that would include firstboot-16.4-1?

Comment 15 Martin Gracik 2011-09-20 10:16:12 UTC
I think you don't need a new compose, you just need a repo with the new firstboot package. But I'm not sure if it is anywhere yet.

The status on fedora updates is still pending...

Comment 16 Adam Williamson 2011-09-20 19:34:33 UTC
yeah, you only need a repo for the installer with firstboot in it. the new firstboot was just pushed to testing, so just installing with updates-testing selected might be enough if your mirror is up to date. otherwise, you can put a side repo up and point anaconda at it.

Comment 17 Hongqing Yang 2011-09-21 02:24:15 UTC
*** Bug 738944 has been marked as a duplicate of this bug. ***

Comment 18 Kamil Páral 2011-09-21 09:51:04 UTC
I have installed system over VNC using updates-testing including firstboot-16.4-1. The system boots. However, it boots only to runlevel 3 and I had to issue "init 5" to see firstboot and user session afterwards.

I think this bug can be closed as fixed and I'll file a separate bug report about the wrong default runlevel.

Comment 19 Martin Gracik 2011-09-21 10:03:12 UTC

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

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