| View previous topic :: View next topic |
| Author |
Message |
superphreak4
n00b
Joined: 15 Jun 2005
Posts: 16
|
 Posted: Mon Apr 27, 2009 3:17 am Post subject: NumPad + others don't work through Windows RealVNC client |
 |
|
Recently I've noticed that my NumPad keys don't work when I connect to gentoo vnc server from windows xp realvnc client. I believe it started around the time I upgraded Xorg to 1.5. I use a Cables-2-Go 35555 KVM switch with USB KB/Mouse. KDE turns NumLock on at startup. So I switch KVM to my windows box and use VNC to control gentoo box since switching with KVM is slow, plus no hotkey switching with USB KB. From vnc client (windows numlock on) the numbers don't work, if I turn NumLock off all/most work except for '5'. The most annoying thing is that the 'delete' key (below 'insert', not 'backspace') does not work.
| Code: | | [ebuild R ] net-misc/vnc-4.1.3-r2 USE="opengl server xorgmodule" |
with the 'vnc' Xorg module
| Code: | black ~ # cat /etc/X11/xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
# InputDevice "Mouse0" "CorePointer"
# InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "on"
Option "AutoEnableDevices" "on"
# Option "AllowEmptyInput" "on"
EndSection
Section "Files"
ModulePath "/usr/lib64/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "dbe"
Load "record"
Load "vnc"
Load "GLcore"
Load "xtrap"
Load "glx"
Load "extmod"
Load "freetype"
Load "type1"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "G70 [GeForce 7600 GT]"
# BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
Option "PasswordFile" "/home/superphreak/.vnc/passwd"
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1920x1200_60" "1280x1024_60"
EndSubSection
EndSection
#Section "InputDevice"
# Identifier "Keyboard0"
# Driver "kbd"
#EndSection
#Section "InputDevice"
# Identifier "Mouse0"
# Driver "evdev"
# #Driver "mouse"
# Option "CorePointer"
# Option "Name" "Logitech USB Gaming Mouse"
# Option "HWHEELRelativeAxisButtons" "7 6"
# Option "Buttons" "9"
#EndSection
|
| Code: | black ~ # cat /etc/hal/fdi/policy/10-x11-input.fdi
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<!-- FIXME: Support tablets too. -->
<match key="info.capabilities" contains="input.mouse">
<merge key="input.x11_driver" type="string">mouse</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.x11_driver" type="string">evdev</merge>
</match>
</match>
<match key="info.capabilities" contains="input.keys">
<!-- If we're using Linux, we use evdev by default (falling back to
keyboard otherwise). -->
<merge key="input.x11_driver" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.x11_driver" type="string">evdev</merge>
</match>
</match>
<match key="info.capabilities" contains="input.touchpad">
<merge key="input.x11_driver" type="string">mouse</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.x11_driver" type="string">evdev</merge>
</match>
</match>
</device>
</deviceinfo>
|
That seems to me to be the most relevant info, let me know if more is needed.
Thank You |
|
| Back to top |
|
 |
superphreak4
n00b
Joined: 15 Jun 2005
Posts: 16
|
| Posted: Tue May 05, 2009 8:58 am Post subject: |
|
|
bump
Nobody has any suggestions/theories? |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Tue May 05, 2009 11:19 am Post subject: |
|
|
I may have one.
While I'm not using anything like vnc, I've read some posts about
virtualbox (I think), that suggest that this type of program may be doing
some internal remapping, that's no longer correct with evdev driver.
So, try to find a setting of the program that stops that. |
|
| Back to top |
|
|
|
Kernel & Hardware
