Bug 752503

Summary: unable to connect to tigervnc 1.1 server
Product: [Fedora] Fedora Reporter: Heiko Adams <bugzilla>
Component: vinagreAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17CC: berrange, bnocera, cfergeau, garrett.mitchener, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 20:23:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Heiko Adams 2011-11-09 17:46:45 UTC
Description of problem:
vinagre seems to be unable to connect to tigervnc 1.1 servers. Everytime I try to connect to a tigervnc 1.1 server running on my wifes windows machine, vinagre just says that the connection was closed.

Version-Release number of selected component (if applicable):
vinagre-3.2.1-2.fc16.i686
gvnc-0.4.3-1.fc15.i686
gtk-vnc2-0.4.3-1.fc15.i686

How reproducible:
allways

Steps to Reproduce:
1. start vinagre
2. open a new connection to tigervnc 1.1 server
3.
  
Actual results:
no connection to remote server

Expected results:
vinagre should connect to remote server

Additional info:
remmina and tigervnc-viewer don't have this problem

Comment 1 Matthias Clasen 2011-11-14 21:47:12 UTC
Filed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=664074

Comment 2 Garrett Mitchener 2013-04-08 18:47:10 UTC
I think I'm seeing this as well, just trying to get from one Fedora 18 machine (VNC viewer) to another (VNC server).  Possible complication: Our firewall is configured so that the VNC connection from the outside has to go through ssh, which is running through a VPN.

Comment 3 Fedora End Of Life 2013-07-03 20:26:22 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2013-07-31 20:23:10 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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