Launchpad has imported 2 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=78012.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2014-04-27T20:08:20+00:00 Egmont Koblinger wrote: Turn on NumLock, verify the behavior by pressing the numpad digits. Change layout by executing a "setxkbmap us" or similar command. Verify that numpad digits still work as expected. Press and release any of the modifiers, e.g. left shift. Press the numpad keys and figure out that they're in a broken inconsistent state that should never occur. Numpad 5 inserts a literal 5 into applications, whereas the rest work as if NumLock had been turned off. numlockx reports it is switched on. Press the NumLock key and it's turned off, press again and it's turned on correctly. Expected behavior: changing layout should of course not effect numlock's state. Originally reported at https://bugs.launchpad.net/ubuntu/+source/gnome- settings-daemon/+bug/1247668. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1247668/comments/15 ------------------------------------------------------------------------ On 2014-04-28T00:16:06+00:00 Egmont Koblinger wrote: When NumLock is off, my numpad keys report keycodes 110-119 (with the exception of '5' which still has the keycode 84). E.g. in "xev", numpad '1' reports 115 End, instead of the expected 87 KP_End. (With NumLock on, it is 87 KP_1, as expected.) Speaking in terms of "xmodmap -pke" format, apparently the correct column is looked up (depending on NumLock's status), but in the wrong row for some reason (the row also depends on NumLock's status, though it shouldn't). Holding down the Fn key toggles the keycodes, i.e. with NumLock off it becomes 87 KP_End, and with NumLock on it becomes 115 End. The very same behavior is observable with "showkey" on the text console (with an offset of 8 in the key codes, and NumLock can't be toggled while showkey is running). Apparently, this laptop works differently than most laptops, and probably the hardware does some magic that it really shouldn't do. The commands "numlockx on" / "numlockx off" work as expected, they apparently somehow tell the hardware whether to alter the keycodes consistently with X's belief. Using "xmodmap -pke"'s terminology, the row and the column are switched together, and I haven't found a way to get to the other two row/column combos. This suggests that theoretically there should exist a workaround. Whenever X's belief of the NumLock state changes, it should do whatever "numlockx off" does to lie to the hardware so that it doesn't modify the keycodes. This is a Samsung NP300E5Z laptop. (By the way, it doesn't have a NumLock LED.) Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1247668/comments/16 ** Changed in: xorg-server Status: Unknown => Confirmed ** Changed in: xorg-server Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1247668 Title: NumLock turned off on layout switch To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1247668/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
