Bug 1211038 - virt-viewer Windows x64 to X11 vino instance fails, TLS error
Summary: virt-viewer Windows x64 to X11 vino instance fails, TLS error
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: vino
Version: 22
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-12 12:32 UTC by Pedro Francisco
Modified: 2016-07-19 13:41 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 13:41:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


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