Bug 175583 - Wrong keymap for numpad 1 7, home, end when using wmaker with vnc
Summary: Wrong keymap for numpad 1 7, home, end when using wmaker with vnc
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: vnc
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-13 00:33 UTC by Tsang Yong
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-05-05 14:54:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tsang Yong 2005-12-13 00:33:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

Description of problem:
i installed wmaker and realvnc recently. When I try to type in the xterm in that vnc session with wmaker, the numpad key 1 and 7 is not working. 

I get effectively <home> and <end> no matter what the numlock is active or not. The key works fine in the console but not in my vnc sessions. 

Please help!

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.rpm -ihv Windowmaker-<new version>
2.install realvnc
3.run wmaker with vnc 
4.Press 1 and 7 numpad key in xterm will produce <home> and <end> effect, no matter the numpad LED is active or not. 

Additional info:

Comment 1 Tim Waugh 2005-12-13 10:01:07 UTC
You haven't filled in the 'version-release number of selected component' field.
 What does 'rpm -q vnc vnc-server' say?

Comment 2 Tsang Yong 2005-12-14 04:16:23 UTC
[yongtin@strawberry ~]$ rpm -qa | grep vnc
vnc-server-4.1.1-10
[yongtin@strawberry ~]$ 

Comment 3 Jitka Kozana 2006-03-01 15:16:54 UTC
I cannot reproduce your bug.   
Please try the newest version of vnc and let me know, if this problem still 
occurs. 

Comment 4 John Thacker 2006-05-05 14:54:48 UTC
Closing due to lack of response.


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