Bug 1340688

Summary: anaconda failed to perform an installation with inst.vnc boot option added
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-31 22:01:21 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:
Embargoed:
Attachments:
Description Flags
screenshot
none
anaconda.log
none
syslog
none
vncserver.log none

Description lnie 2016-05-30 05:30:23 UTC
Created attachment 1162669 [details]
screenshot

Description of problem:

Version-Release number of selected component (if applicable):
f24-20160528-workstaion-netinst-x86_64


How reproducible:
always

Steps to Reproduce:
1.add the boot option "inst.vnc"
2.vinagre the specific ip address and type "Enter"
3.

Actual results:
got the "connection closed" error

Expected results:


Additional info:

Comment 1 lnie 2016-05-30 06:20:01 UTC
Created attachment 1162673 [details]
anaconda.log

Comment 2 lnie 2016-05-30 06:20:30 UTC
Created attachment 1162675 [details]
syslog

Comment 3 lnie 2016-05-30 06:20:54 UTC
Created attachment 1162676 [details]
vncserver.log

Comment 4 Brian Lane 2016-05-31 22:01:21 UTC
Looks like this was broken by a change in tigervnc-1.6.0-4

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