Here is an example of what is happening. I launched xev, pressed the 2 on the
number pad, then pressed the numlock to turn it on, then pressed 2 on the
number pad. This is what I am seeing:
KeyPress event, serial 33, synthetic NO, window 0x2e00001,
root 0x10d, subw 0x0, time 171385442, (40,170), root:(1405,354),
state 0x0, keycode 88 (keysym 0xff99, KP_Down), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 33, synthetic NO, window 0x2e00001,
root 0x10d, subw 0x0, time 171385545, (40,170), root:(1405,354),
state 0x0, keycode 88 (keysym 0xff99, KP_Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 33, synthetic NO, window 0x2e00001,
root 0x10d, subw 0x0, time 171388770, (40,170), root:(1405,354),
state 0x0, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 33, synthetic NO, window 0x2e00001,
root 0x10d, subw 0x0, time 171388883, (40,170), root:(1405,354),
state 0x0, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 33, synthetic NO, window 0x2e00001,
root 0x10d, subw 0x0, time 171390409, (40,170), root:(1405,354),
state 0x0, keycode 88 (keysym 0xff99, KP_Down), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 33, synthetic NO, window 0x2e00001,
root 0x10d, subw 0x0, time 171390599, (40,170), root:(1405,354),
state 0x0, keycode 88 (keysym 0xff99, KP_Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
-- James
________________________________
From: Hammer, James R [jrham...@lanl.gov]
Sent: Friday, July 19, 2013 11:21 AM
To: Brian Hinz
Cc: tigervnc-users@lists.sourceforge.net
Subject: Re: [Tigervnc-users] numlock issue in TigerVNC 1.3.0
On the same setup I described below (on a sunray), the java viewer does not
have a problem with numlock. Also, the numlock works when using the turboVNC
viewer.
With all of the neat features in the tigervnc client, it would be great to get
that one working in our environment. Any help would be greatly appreciated.
Thanks.
-- James
________________________________
From: Hammer, James R [jrham...@lanl.gov]
Sent: Friday, July 19, 2013 8:07 AM
To: Brian Hinz
Cc: tigervnc-users@lists.sourceforge.net
Subject: Re: [Tigervnc-users] numlock issue in TigerVNC 1.3.0
I am on a sunray. I use Gnome as my window manager. I ssh from my session on
the sunray to my VNC server. I launch the viewer in the ssh session,
connecting to localhost (the VNC server) and the display is reflected back to
my session on the sunray. I have tried this from both RHEL and Solaris Sunray
servers and get the same result.
I tried the same scenario from a standalone RHEL 6 box instead of the sunray.
I did not have the problem. The numlock worked fine there. So there must be
something happening in the sunray session that is messing up the numlock
(though numlock does work OK in the sunray session itself.
Any ideas for a work around on sunrays?
Thanks.
-- James
________________________________
From: bph...@gmail.com [bph...@gmail.com] on behalf of Brian Hinz
[bph...@users.sourceforge.net]
Sent: Thursday, July 18, 2013 8:21 PM
To: Hammer, James R
Cc: tigervnc-users@lists.sourceforge.net
Subject: Re: [Tigervnc-users] numlock issue in TigerVNC 1.3.0
On Thu, Jul 18, 2013 at 6:37 PM, Hammer, James R
<jrham...@lanl.gov<mailto:jrham...@lanl.gov>> wrote:
When connecting to tigerVNC-server 1.3.0 using tigerVNC vncviewer 1.3.0 numlock
is not working for me. My OS is RHEL 6 (client and server). Whether the
numlock on the keyboard is on or off, I can't get numbers when hitting number
keys on the keyboard.
With tigerVNC 1.2.0 I was able to work around this using a suggestion from
Peter to do the following:
xmodmap -e "remove mod2 = Num_Lock"
When I did that in the previous version, the numlock would work as expected.
This work around does not appear to work with version 1.3.0.
Are there any suggestions as to a work around in tigerVNC 1.3.0?
I can't reproduce this, both sets of number keys seem to work fine for me on
CentOS 6.4. Can you give some more details? Like how you are starting the
server, which window manager you are using, etc. Also, can you try the java
client to help rule out the server as the culprit.
-brian
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Tigervnc-users mailing list
Tigervnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-users
