Bug 178451

Summary:	Can't use some keys in Midnight Commander
Product:	[Applications] konsole	Reporter:	András Manţia <amantia>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	finex, jan.kaspar, jpalecek, kejpi, mkyral, wrar
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Unspecified
Latest Commit:		Version Fixed In:

Description András Manţia 2008-12-22 11:56:45 UTC

Version:            (using Devel)
Installed from:    Compiled sources

In trunk (but not in 4.1.x), you can't use some keys in Mindight Commander, like +, * in the keypad. Actually they do unexpected thing:
* - enters the current dir, like enter
+ - insert an "l"

I can "fix" this in the profile's by removing the key combination binding, but I find this behavior to be wrong and a regression (these keys ALWAYS worked in konsole).

Comment 1 FiNeX 2008-12-22 12:03:34 UTC

I've just tested it, I confirm this problem.

Comment 2 Marian Kyral 2008-12-22 12:25:11 UTC

I can confirm with 4.1.85 too. Vi is also affected. I cannot enter keypad numbers.

Comment 3 Petr Kopecký 2008-12-31 12:11:13 UTC

I can confirm this bug on trunk (built from SVN 30/12/2008 on Gentoo). Additionally I have found out that it depends in Input setup in Konsole's profile. When default "XFree 4" is chosen Numerical keypad is not working in Midnight Commander (NumLock is on). On the other hane if you choose "Linux console" (sorry, I am not sure about correct English name as I am using localized KDE) then Numkeys are working but F1-F5 are not working. 
I can also confirm problems with Vim.

Comment 4 Jan Kaspar 2009-01-26 20:15:14 UTC

*** Bug 181401 has been marked as a duplicate of this bug. ***

Comment 5 Jan Kaspar 2009-01-26 20:18:37 UTC

I can confirm this issue too. On ArchLinux and KDE versions 4.1.96 and 4.2.0.

Kašpi

Comment 6 Marian Kyral 2009-01-26 20:48:37 UTC

There is an workaround:

1) Go to Settings / Update current profile / Input / Edit 
2) Remove any Keypad reference. 

Then should work again.

Comment 7 Andrey Rakhmatullin 2009-03-25 21:46:16 UTC

4.2.1: works OK.

Comment 8 FiNeX 2009-03-26 01:17:41 UTC

I confirm the bug is fixed on SVN-trunk too.

Thanks for checking Andrey!