Thanks. Could you please tell us the exact brand/model of your keyboard?
Do you have another keyboard somewhere that you could try?
It sounds strange I know, but apparently on a few computers the numpad keys start producing different keycodes when numlock is off (namely the keycodes of the standalone cursor keys). I have no clue yet if it's a problem with the keyboard itself, or the motherboard, bios, what else tries to be more clever than it should...
Make sure NumLock is off. From a terminal start "xev", and press numpad 1. A few friends confirmed to me that they see "keycode 87, keysym KP_End" which is I think the expected result. On the other hand, I see "keycode 115, keysym End" which apparently somehow leads to the broken behavior, I guess you also see this latter.
Thanks. Could you please tell us the exact brand/model of your keyboard?
Do you have another keyboard somewhere that you could try?
It sounds strange I know, but apparently on a few computers the numpad keys start producing different keycodes when numlock is off (namely the keycodes of the standalone cursor keys). I have no clue yet if it's a problem with the keyboard itself, or the motherboard, bios, what else tries to be more clever than it should...
Make sure NumLock is off. From a terminal start "xev", and press numpad 1. A few friends confirmed to me that they see "keycode 87, keysym KP_End" which is I think the expected result. On the other hand, I see "keycode 115, keysym End" which apparently somehow leads to the broken behavior, I guess you also see this latter.
(Just for reference: https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 600659# c63 is a totally different bug apparently caused by the same underlying weird keycode change.)