Bug 1211038

Summary:	virt-viewer Windows x64 to X11 vino instance fails, TLS error
Product:	[Fedora] Fedora	Reporter:	Pedro Francisco <pedrogfrancisco>
Component:	vino	Assignee:	Søren Sandmann Pedersen <sandmann>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	amlau, debarshir, oholy, pedrogfrancisco, sandmann
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 13:41:57 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:

Description Pedro Francisco 2015-04-12 12:32:25 UTC

Description of problem:
virt-viewer Windows x64 to X11 vino instance fails, TLS error


Version-Release number of selected component (if applicable):
vino-3.16.0-1.fc22.x86_64


How reproducible:
Always


Steps to Reproduce:
1. Run Gnome via X11
2. setup remote access via control panel, with or without, same result
3. disable firewalld just in case
4. try to connect


Actual results:
[IPv4] Got connection from client XYZ.lan
  other clients:
Client Protocol Version 3.7
Advertising security type 18
Client returned security type 18
TLS Handshake failed: The TLS connection was non-properly terminated.
Client KIRA3.lan gone
Statistics:
framebuffer updates 0, rectangles 0, bytes 0



Expected results:
Connection should succeed

Comment 1 Fedora End Of Life 2016-07-19 13:41:57 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.