Description of problem: Listen option is not recognized in this new revision, but always in vncviewer man page and usage. Version-Release number of selected component (if applicable): tigervnc.x86_64 1.2.80-0.8.20130124svn5036.fc18 Command used by gitso, is "vncviewer -listen". With an old tigervnc rpm (tigervnc-1.1.0-6.1) it works fine : $ vncviewer -listen Visionneur TigerVNC pour la version 1.1.0 du serveur X - Paquetage construit le « Jul 23 2012 20:06:27 » Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt) Voir http://www.tigervnc.org pour plus d'informations sur TigerVNC. Sat Feb 2 15:39:14 2013 main: Listening on port 5500 But with a recent rpm (tigervnc-1.2.80-0.8.20130124svn5036) it doesn't work : vncviewer -listen TigerVNC Viewer 64-bit v1.2.80 (20130124) Built on Jan 24 2013 at 13:04:01 Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. usage: vncviewer [parameters] [host:displayNum] [parameters] vncviewer [parameters] -listen [port] [parameters]
This bug is ignored upstream since more than one year: http://sourceforge.net/tracker/index.php?func=detail&aid=3477054&group_id=254363&atid=1126848 Really sad since remmina-plugins-vnc does not work with "UltraVNC Single Click" :(
How is this possible? If not this is fixed, package must be downgraded to FC17 version.
Before it worked by removing the dash before listen as in: [code]vncviewer listen[/code] but now it gives the following error: [davide@dave ~]$ vncviewer listen TigerVNC Viewer 32-bit v1.2.80 (20130124) Built on Jan 24 2013 at 13:03:40 Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Tue Feb 5 09:38:56 2013 CConn: unable to resolve host by name: Nome o servizio sconosciuto
Same problem here. I vote for downgrade too, if this is not fixable.
Following the link posted here, I saw upstream has it marked as a duplicate of http://sourceforge.net/tracker/?func=detail&aid=3429667&group_id=254363&atid=1126848 and that issue has recent updates, including a not that it should be fixed in trunk.
(In reply to comment #5) > Following the link posted here, I saw upstream has it marked as a duplicate > of > http://sourceforge.net/tracker/ > ?func=detail&aid=3429667&group_id=254363&atid=1126848 and that issue has > recent updates, including a not that it should be fixed in trunk. It is already fixed in upstream. I'm preparing bigger update for tigervnc which will also fix this issue but update is currently blocked on bug #896648 which is not solved, yet. However I can build package with "-listen" support in koji if you cannot wait for some more time...
> However I can build package with "-listen" > support in koji if you cannot wait for some more time... Yes, please :-) That will help testing too.
tigervnc-1.2.80-0.9.20130307svn5060.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/tigervnc-1.2.80-0.9.20130307svn5060.fc18
*** Bug 906953 has been marked as a duplicate of this bug. ***
Package tigervnc-1.2.80-0.9.20130307svn5060.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing tigervnc-1.2.80-0.9.20130307svn5060.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3797/tigervnc-1.2.80-0.9.20130307svn5060.fc18 then log in and leave karma (feedback).
tigervnc-1.2.80-0.9.20130307svn5060.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.