Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1340688 - anaconda failed to perform an installation with inst.vnc boot option added
Summary: anaconda failed to perform an installation with inst.vnc boot option added
Keywords:
Status: CLOSED DUPLICATE of bug 1280440
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-30 05:30 UTC by lnie
Modified: 2016-05-31 22:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-31 22:01:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (32.76 KB, image/png)
2016-05-30 05:30 UTC, lnie
no flags Details
anaconda.log (6.31 KB, text/plain)
2016-05-30 06:20 UTC, lnie
no flags Details
syslog (63.30 KB, text/plain)
2016-05-30 06:20 UTC, lnie
no flags Details
vncserver.log (789 bytes, text/plain)
2016-05-30 06:20 UTC, lnie
no flags Details

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


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