From nobody@FreeBSD.org  Fri Aug 16 18:46:18 2013
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by hub.freebsd.org (Postfix) with ESMTP id 702C9861
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Aug 2013 18:46:18 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from oldred.freebsd.org (oldred.freebsd.org [8.8.178.121])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.freebsd.org (Postfix) with ESMTPS id 5EB282A44
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Aug 2013 18:46:18 +0000 (UTC)
Received: from oldred.freebsd.org ([127.0.1.6])
	by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id r7GIkIUa077504
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Aug 2013 18:46:18 GMT
	(envelope-from nobody@oldred.freebsd.org)
Received: (from nobody@localhost)
	by oldred.freebsd.org (8.14.5/8.14.5/Submit) id r7GIkHDH077502;
	Fri, 16 Aug 2013 18:46:17 GMT
	(envelope-from nobody)
Message-Id: <201308161846.r7GIkHDH077502@oldred.freebsd.org>
Date: Fri, 16 Aug 2013 18:46:17 GMT
From: kaltheat <kaltheat@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: net/tigervnc
X-Send-Pr-Version: www-3.1
X-GNATS-Notify: meta+ports@vmeta.jp

>Number:         181345
>Category:       ports
>Synopsis:       net/tigervnc: shortcuts like Ctrl-C does not work on vncviewer because of fltk
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          feedback
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 16 18:50:00 UTC 2013
>Closed-Date:    
>Last-Modified:  Wed Sep 11 05:59:46 UTC 2013
>Originator:     kaltheat
>Release:        FreeBSD 9.1 amd64
>Organization:
>Environment:
>Description:
When using tigervnc Ctrl-c, Ctrl-d is not working at supposed in VNC-session (tried in xterm on VNC-server). I'm connecting to a VNC-server provided by virtualbox-ose (VBoxHeadless). I'm running xorg-server-1.12.4_1,1 .


This[1] report arouses the suspicion that it might be a problem with fltk. As I've seen tigervnc-port is using fltk from ports whereas in building instructions for tigervnc the developers recommend to use a patched version of fltk.


[1] http://sourceforge.net/p/tigervnc/bug-tracker/79/

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: edwin 
State-Changed-When: Fri Aug 16 18:50:08 UTC 2013 
State-Changed-Why:  
Awaiting maintainers feedback (via the GNATS Auto Assign Tool) 

http://www.freebsd.org/cgi/query-pr.cgi?pr=181345 

From: Edwin Groothuis <edwin@FreeBSD.org>
To: meta+ports@vmeta.jp
Cc: bug-followup@FreeBSD.org
Subject: Re: ports/181345: net/tigervnc
Date: Fri, 16 Aug 2013 18:50:07 UT

 Maintainer of net/tigervnc,
 
 Please note that PR ports/181345 has just been submitted.
 
 If it contains a patch for an upgrade, an enhancement or a bug fix
 you agree on, reply to this email stating that you approve the patch
 and a committer will take care of it.
 
 The full text of the PR can be found at:
     http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/181345
 
 -- 
 Edwin Groothuis via the GNATS Auto Assign Tool
 edwin@FreeBSD.org

From: kaltheat <kaltheat@googlemail.com>
To: <bug-followup@FreeBSD.org>,  <edwin@FreeBSD.org>,  <meta+ports@vmeta.jp>
Cc:  
Subject: Re: ports/181345: net/tigervnc
Date: Fri, 16 Aug 2013 21:37:34 +0200

 Hi,
 
 there is also PR ports/180911 which is a patch to update net/tigervnc to newest version 1.3.0.
 I've tested the patch and patched port compiles fine, but it doesn't solve PR ports/181345.
 
 Regards,
 kaltheat
 

From: Koichiro IWAO <meta+ports@vmeta.jp>
To: kaltheat <kaltheat@googlemail.com>
Cc: bug-followup@FreeBSD.org, meta+ports@vmeta.jp
Subject: Re: ports/181345: net/tigervnc
Date: Sat, 17 Aug 2013 11:19:44 +0900

 Thanks for your report.
 
 The reason why tigervnc-port uses fltk from ports is, in-tree fltk was
 removed[1] shortly after 1.2.0 release. Actually, 1.3.0 does not includes
 fltk in its source tree. Probably, building tigervnc with included version
 of fltk does not solve the issue becasue 1.3.0 no longer includes fltk
 and control keys still do not work as you confirmed.
 
 I will look for the issue but I'm busy now. If you find anything about
 the issue, please let me know.
 
 [1] http://sourceforge.net/p/tigervnc/code/4951/tree/trunk/CMakeLists.txt?diff=4935
 > Remove the in-tree versin of FLTK. Maintaining such a copy is way too
 > much work, and it's constantly out of sync. Let's document what the
 > main developers (ie Cendio) are using instead. 
 
 On Fri, Aug 16, 2013 at 09:37:34PM +0200, kaltheat wrote:
 > Hi,
 > 
 > there is also PR ports/180911 which is a patch to update net/tigervnc to newest version 1.3.0.
 > I've tested the patch and patched port compiles fine, but it doesn't solve PR ports/181345.
 > 
 > Regards,
 > kaltheat
 > 
 
 -- 
 `whois vmeta.jp | nkf -w`
 meta <meta@vmeta.jp>

From: Koichiro IWAO <meta@vmeta.jp>
To: kaltheat <kaltheat@googlemail.com>
Cc: meta+ports@vmeta.jp, bug-followup@freebsd.org
Subject: Re: ports/181345: net/tigervnc
Date: Sat, 17 Aug 2013 14:10:27 +0900

 I define "ctrl keys don't work":
   ctrl keys are always detected, tested by xev(1)
   when pressing another key with a ctrl key (ex ctrl-c),
   the other key ("c") is not detected
 
 The issue may possibly upstream issue. I tested several combinations of
 VNC client/server. The result is below. It seems the sever part of
 tigervnc-port works fine. Even if TigerVNC viewer runs on Mac,
 ctrl keys don't work. I don't have Windows environment. Would you please
 test whether ctrl-? shortcuts works with TigerVNC viewer on Windows?
 
 Server                     Client                           Ctrl keys
 S: net/tigervnc 1.2.0  <-> C: TigerVNC viewer on Mac     => don't
 S: net/tigervnc 1.2.0  <-> C: net/tigervnc viewer 1.2.0  => don't
 S: Mac Screen Sharing  <-> C: net/tigervnc viewer 1.2.0  => don't
 S: net/tigervnc 1.2.0  <-> C: built-in Mac VNC client    => works!
 S: net/tigervnc 1.2.0  <-> C: net/remmina (libvncclient) => works!
 
 
 Regards,
 -- 
 `whois vmeta.jp | nkf -w`
 meta <meta@vmeta.jp>

From: Koichiro IWAO <meta@vmeta.jp>
To: bug-followup@freebsd.org, kaltheat@gmail.com
Cc:  
Subject: Re: ports/181345: net/tigervnc
Date: Sat, 17 Aug 2013 14:42:32 +0900

 I had an mistaken idea.
 I found almost the same bug  reported on archlinux bug tracker.
 
    https://bbs.archlinux.org/viewtopic.php?id=166735
    https://bugs.archlinux.org/task/36186
 
 The solution is to update fltk to newer snapshot or apply paches shown
 in the tracker to fltk 1.3.2.
 
 Regards,
 -- 
 `whois vmeta.jp | nkf -w`
 meta <meta@vmeta.jp>
 

From: Koichiro IWAO <meta@vmeta.jp>
To: bug-followup@freebsd.org, kaltheat@gmail.com
Cc:  
Subject: Re: ports/181345: net/tigervnc
Date: Wed, 11 Sep 2013 14:41:49 +0900

 I made a patch and  raise a PR ports/182006.
 Waiting for feedback from the maintainer of x11-toolkits/fltk.
 
 -- 
 `whois vmeta.jp | nkf -w`
 meta <meta@vmeta.jp>
>Unformatted:
