Many of our debian users have reported (although I cannot reproduce it myself) that they started having problems with their keyboard arrows after upgrading to 4.5. As far as I can tell, they are all using the evdev driver, but selecting "evdev-managed keyboard" in kde's keyboard configuration doesn't fix it for them. However, they all have reported that running "setkxbmap -keycodes evdev" fixes the problem (until the next kde login). The information source is http://lists.debian.org/debian-kde/2010/09/msg00023.html and irc conversations.
Could you please attach output from this command twice xkbcomp :0 -xkb out.xkb Once when keys don't work right and once they do after -keycodes command.
Created attachment 51712 [details] output of "xkbcomp :0 -xkb out.xkb" after kde login
Created attachment 51713 [details] output of "xkbcomp :0 -xkb out2.xkb" after running "setkxbmap -keycodes evdev" Note: Those two attachments were given to me by the person who first reported the problem on the mailing list, see the ml link on the description for his exact description of the problem.
So I've shown attached files to the xkeyboard-config maintainer and he said that the groups are messed up, seems like the layout was only one but inside out.xkb there were two groups. So this looks like the bug in X.org: https://bugs.freedesktop.org/show_bug.cgi?id=18277 Also looking at http://lists.debian.org/debian-kde/2010/09/msg00061.html it looks like also the problem with keyboard model is that "keyboard kded module does not start for some reason" so this might also be related to how kde was built. At this point I can't help much until kded daemon startup is fixed. So I'll mark the bug as "need more info" to see if there's new information shows up that will point to problem in kde keyboard module.
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!