Bug 1030804 - Failed to start via vnc
Summary: Failed to start via vnc
Keywords:
Status: CLOSED DUPLICATE of bug 1030719
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: i386
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-15 08:05 UTC by Tao Wu
Modified: 2014-10-28 23:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-15 22:47:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screen shot (14.23 KB, image/png)
2013-11-15 08:05 UTC, Tao Wu
no flags Details
syslog (58.61 KB, text/plain)
2013-11-15 08:06 UTC, Tao Wu
no flags Details

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 ***


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