konsole ignores keypad when numlock is off

[Sergei Ivanov]

Binary package hint: konsole

I have kubuntu karmik beta installed on a Toshiba L505 laptop. This laptop has a full 104-keys keyboard with a numeric keypad section and a numlock key. In konsole, the keypad keys do not work when numlock is off. They seem to be completely ignored.

When numlock is on, they produce digits as expected. Even with numlock off, keypad keys with ctrl or alt produce some escape sequences, but without modifiers they do not.

Other applications (I checked xterm, konqueror and firefox) do not have this problem. The keypad also works normally in a console VT.

ProblemType: Bug
Architecture: amd64
Date: Tue Oct 20 11:20:44 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
Package: kdelibs-bin 4:4.3.2-0ubuntu7
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kde4libs
Uname: Linux 2.6.31-14-generic x86_64

[Sergei Ivanov (svivanov)]

I fixed this by adding the following lines to konsole's keytab file
(patch taken from http://stochastic-randomness.blogspot.com/2009/08/konsole-numpad-fix-for-kde4.html):

# Keypad keys with NumLock Off
key Up -Shift+Ansi+AppCuKeys+KeyPad : "\EOA"
key Down -Shift+Ansi+AppCuKeys+KeyPad : "\EOB"
key Right -Shift+Ansi+AppCuKeys+KeyPad : "\EOC"
key Left -Shift+Ansi+AppCuKeys+KeyPad : "\EOD"

key Up -Shift+Ansi-AppCuKeys+KeyPad : "\E[A"
key Down -Shift+Ansi-AppCuKeys+KeyPad : "\E[B"
key Right -Shift+Ansi-AppCuKeys+KeyPad : "\E[C"
key Left -Shift+Ansi-AppCuKeys+KeyPad : "\E[D"

key Home +AppCuKeys+KeyPad : "\EOH"
key End +AppCuKeys+KeyPad : "\EOF"
key Home -AppCuKeys+KeyPad : "\E[H"
key End -AppCuKeys+KeyPad : "\E[F"

key Insert +KeyPad : "\E[2~"
key Delete +KeyPad : "\E[3~"
key Prior -Shift+KeyPad : "\E[5~"
key Next -Shift+KeyPad : "\E[6~"

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!