[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Disabling Print Screen key



On 07/31/2007 10:09 AM, Luis Finotti wrote:
Hi,

My Print Screen key is too close to BackSpace, so I keep pressing it
by accident.  I use KDE, and this makes "KSnapshoyt" pop up.  (In
fluxbox, it sends the content of the terminal to the printer.)

I checked the key assignments of KDE, and I found no shortcut for the
PrtSc key, and even defining a different application for that key
would still make (only) KSnapshot pop up.  (KSnapshot was assigned to
Crtl+PrtSc, and I disabled it too, just in case.)

My Google searchs did not help (even on this list).

So, I decided to disable the key.

Using "xev", I saw that the keycode was 111:

....
KeyRelease event, serial 31, synthetic NO, window 0x3600001,
    root 0x91, subw 0x0, time 482199882, (485,527), root:(489,552),
    state 0x0, keycode 111 (keysym 0xff61, Print), same_screen YES,
    XLookupString gives 0 bytes:
....

Indeed, "xmodmap -pk" gave:

...
    111         0xff61 (Print)  0xff15 (Sys_Req)
...

So, I did "xmodmap -e "keysym Print = BackSpace"".  Now, "xev" gives:

....
KeyRelease event, serial 31, synthetic NO, window 0x3400001,
    root 0x91, subw 0x0, time 482660638, (-260,401), root:(838,426),
    state 0x0, keycode 111 (keysym 0xff08, BackSpace), same_screen YES,
    XKeysymToKeycode returns keycode: 22
    XLookupString gives 1 bytes: (08) "
....

and  "xmodmap -pk" gives:

...
    111         0xff08 (BackSpace)
...

But still, KSnapshot pops up, and the backspace has no effect.

Any suggestions or ideas (other than remove the key physically)??

Thanks,

Luis



My system (Debian 3.1, KDE 3.3.2) does not exhibit this behavior by default. I can enable (and disable) it by going into the KDE Control Center: K-> Control Center-> Regional & Accessibility-> Keyboard Shortcuts-> Command Shortcuts-> Graphics-> More Applications-> KSnapshot.

Perhaps you inadvertently made Print a shortcut for ksnapshot. If so, you should be able to disable it by going through the above sequence.




Reply to: