Bug 172411

xev give following output when pressing up key:
"
KeymapNotify event, serial 34, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   4294967168 0   0
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

KeyRelease event, serial 34, synthetic NO, window 0x2c00001,
    root 0x1a6, subw 0x0, time 19946971, (85,168), root:(90,193),
    state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
"

so it does not give a KeyPressed event like other keys....

shift+up works ctrl+up does not work..

I have the same problem with KDE 4.1.3, compiled from portage with gcc 4.3.2 on Gentoo. When KDE starts, up key doesn't work at all. But if I kill X with Ctrl+Alt+Backspace, and start KDE again, up key will work. It is inconvenient way to run KDE, because you need to relogin every time you started computer.

Does the problem still exist? 

@Visiliy: Do you use evdev too?

No info since one week

I would like to confirm having the same issue on Debian (stable/testing/unstable/experimental).

Linux t500 2.6.32.8 #1 SMP Wed Feb 10 12:10:32 EST 2010 x86_64 GNU/Linux
ii  xserver-xorg-input-evdev      1:2.3.2-3
ii  libc6                         2.10.2-2
ii  udev                          149-2
ii  xserver-xorg-core             2:1.7.4-1
all KDE4 packages version         4:4.3.4-1

Created attachment 40827 [details]
xev output for non-working Up key

Created attachment 40828 [details]
xev output for working Down key

(In reply to comment #6)
> I would like to confirm having the same issue on Debian
> (stable/testing/unstable/experimental).
> 
> Linux t500 2.6.32.8 #1 SMP Wed Feb 10 12:10:32 EST 2010 x86_64 GNU/Linux
> ii  xserver-xorg-input-evdev      1:2.3.2-3
> ii  libc6                         2.10.2-2
> ii  udev                          149-2
> ii  xserver-xorg-core             2:1.7.4-1
> all KDE4 packages version         4:4.3.4-1

Forgot to mention, the same Up key (and everything else) works if I only run xinit which just spawns a X server + xterm, but under KDE4 it is not working.

System Settings -> Regional & Language -> Keyboard Layout -> Keyboard model is set to "Evdev-managed keyboard".

$ setxkbmap -print

xkb_keymap {
        xkb_keycodes  { include "evdev+aliases(qwerty)" };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include
"pc+us+hu:2+inet(evdev)+terminate(ctrl_alt_bksp)"       };
        xkb_geometry  { include "pc(pc104)"     };
};

Created attachment 40830 [details]
Output from "xkbcomp :0 - "

All the attachments were made under KDE4.

Also for some appications I can use Super+Up to replace the missing Up key.

Created attachment 40831 [details]
xorg.conf

Created attachment 40832 [details]
Xorg.0.log

This is a X11 issue. It has nothing to do with kde. Look at http://bugs.gentoo.org/153115 for some possible solutions.

(In reply to comment #15)
> This is a X11 issue. It has nothing to do with kde. Look at
> http://bugs.gentoo.org/153115 for some possible solutions.

I am not convinced this a X11 issue. Let me reiterate what I have written in #9.

If I execute xinit, which just runs the X server and a xterm without any window manager, etc. the Up key works.

If I execute startx, which runs X server and "whole" KDE4 the Up key is not working any more.

So for me the problem depends on the presence of KDE4!

I have made additional experiments. If I run KDE4 with startx Up key is not working, however if I start kdm the Up key works and keeps working after logging into KDE4 through kdm.

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!