Bug 133338

Summary: khotkeys uses keycodes, not keysyms
Product: [Unmaintained] khotkeys Reporter: Pavel Bazika <pavel.bazika>
Component: generalAssignee: Lubos Lunak <l.lunak>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Pavel Bazika 2006-08-31 18:01:08 UTC 
Version:            (using KDE KDE 3.5.4)
Installed from:    Gentoo Packages
Compiler:          gcc 3.4.6 
OS:                Linux

Because khotkeys uses keycodes, there is a problem when xorg evdev driver is used. Some keycodes are not the same a those for standard kbd driver. xkb is capable to remap this another keycodes to right keysyms, but because khotkeys doesn't respect keysyms, it reacts to bad keys.

How to reproduce:

Define action in khotkeys: when print screen is pressed, then ksnapshot is executed. When defining, use standard kbd driver for your keyboard in xorg.conf. Printscreen key has keycode 111. Then exit X server, change your keyboard driver to evdev (you must have xorg 7.0 or greater, I have 7.1). Start KDE and try pressing up arrow button - ksnapshot will be executed, because up arrow has 111 keycode now.

When "setxkbmap -model evdev -keycodes evdev us" is called and xev utility is executed, then can be seen, that up arrow generates Up keysym. But khotkeys still executes ksnapshot.
Comment 1 Benjamin K. Stuhl 2006-11-14 21:01:57 UTC 
This is a dupe of bug 125559: khotkeys does actually use keysyms, it's just that there's a hack in there to fix Xorg's broken mapping of XK_Print and XK_Sys_Req in the default mapping... that hack is unnecessary for the evdev layout (see my patch in #125559).
Comment 2 Lubos Lunak 2007-01-02 14:25:04 UTC 

*** This bug has been marked as a duplicate of 125559 ***