Bug 1030804

Summary: Failed to start via vnc
Product: [Fedora] Fedora Reporter: Tao Wu <twu>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, robatino, sdharane, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-15 22:47:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screen shot
none
syslog none

Description Tao Wu 2013-11-15 08:05:07 UTC 
Created attachment 824351 [details]
screen shot

Description of problem:
F20 final TC1 failed to start by vnc method, blocked at the first step as displayed in the attachment.

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


How reproducible:
100%

Steps to Reproduce:
https://fedoraproject.org/wiki/Test_Results:Fedora_20_Final_TC1_Install?rd=Test_Results:Current_Installation_Test

Actual results:


Expected results:


Additional info:
Comment 1 Tao Wu 2013-11-15 08:06:31 UTC 
Created attachment 824352 [details]
syslog
Comment 2 Tao Wu 2013-11-15 08:26:38 UTC 
It may be not caused by vnc, for it occurs even without vnc command.
Comment 3 Adam Williamson 2013-11-15 22:02:13 UTC 
Were you using a 32-bit image? If so I'd guess you reproduced this:

https://bugzilla.redhat.com/show_bug.cgi?id=1030719
Comment 4 Andre Robatino 2013-11-15 22:15:11 UTC 
The syslog attachment shows that it was in fact 32-bit, so probably a dupe of bug 1030719.
Comment 5 Adam Williamson 2013-11-15 22:47:06 UTC 
yeah, let's go with that.

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