Description of problem: Under Fedora 8/x86-64, the number pad for my USB keyboard works as expected, when numlock is turned on. Under Fedora 9/x86-64, the number pad causes the mouse cursor to move around on the screen in a predictable manner: (7 == move upper left diagonal, 6 == move right, 2 == move down, etc.) Numlock and number pad work as expected when in console mode, thus only X11 is affected. lsusb output: Bus 002 Device 004: ID 045e:000b Microsoft Corp. Natural Keyboard Elite Bus 002 Device 002: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0 Version-Release number of selected component (if applicable): xorg-x11-drv-keyboard-1.3.0-3.fc9.x86_64 lspci and lsusb attached. How reproducible: always Steps to Reproduce: 1. Install Fedora 8 2. turn on numlock 3. press number keys on numpad Actual results: Mouse cursor moves. Expected results: Numbers appear on screen (when in terminal or editor etc). Additional info:
Created attachment 308885 [details] lsusb -v output
Created attachment 308886 [details] lspci -v output
Created attachment 308887 [details] xorg.conf
Could I ask for /var/log/Xorg.*.log as well, please?
Created attachment 309157 [details] Xorg logs
Just attached a tarball with all my Xorg logs. Some may be from Fedora 8, I did not check. NOTE/CORRECTION: In "Steps to Reproduce", #1 should read Install Fedora 9 not Install Fedora 8
Created attachment 309280 [details] Xorg.setup.log from the attachment 309157 [details] tarball
Created attachment 309282 [details] Xorg.0.log from the attachment 309157 [details] tarball
Created attachment 309283 [details] Xorg.0.log.old from the attachment 309157 [details] tarball
Created attachment 309284 [details] Xorg.1.log from the attachment 309157 [details] tarball
Created attachment 309285 [details] Xorg.2.log from the attachment 309157 [details] tarball
Created attachment 309286 [details] Xorg.2.log.old from the attachment 309157 [details] tarball
Created attachment 309287 [details] Xorg.3.log from the attachment 309157 [details] tarball
Created attachment 309288 [details] Xorg.4.log from the attachment 309157 [details] tarball
Created attachment 309289 [details] Xorg.5.log from the attachment 309157 [details] tarball
I'm seeing this as well. I have a "Saitek PLC" USB keyboard. (Jeff already provided quite a bit of information, so I'll refrain from attaching all of my information unless someone specifically says they want it...)
NOTE: Ctrl-Shift-Numlock restores proper numpad behavior (Dave Airlie's tip)
I'm seeing this as well.
I need a few additional logs to track this down - I can't reproduce it on server 1.5 branch tip, nor on F9, nor on git master. please post: - the output of xev when hitting the num key (that activates mouse keys) before and after it has been deactivated with Ctrl+Shift+NumLock. - the server-0.xkb file generated when running xkbcomp :0 - the output of xkbset q (google for your favourite mirror, I got mine from the debian repository)
(In reply to comment #19) > I need a few additional logs to track this down - I can't reproduce it on server > 1.5 branch tip, nor on F9, nor on git master. > > please post: > - the output of xev when hitting the num key (that activates mouse keys) before > and after it has been deactivated with Ctrl+Shift+NumLock. Jeff, after pressing Ctrl+Shift+NumLock as you suggested, the num pad starts working again. I didn't even know about this shortcut. Perhaps there was a bad default setting? Or I've just pressed this accidentally, but I'm not sure about that..
I can no longer reproduce this bug, either. I suspect it was already (accidentally, perhaps?) squashed...
Thanks for letting us know.