Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages In "Configure Shortcuts..."-like dialogs when I try to assign Alt+Printscreen shortcut (aka Alt+Print) to an action it displays an error message with text "The key you just pressed isn't supported by Qt." At first, I really was being thinking that it's a limitation introduced in Qt4. But today I noticed that if I manually edit config files and write there "Alt+Print" -- it WORKS. Thus, it looks not like a Qt4 limitation, but like improperly working "Configure Shortcuts..."-like dialogs. P.S.: In KDE3.5 I was able to assign it (without manually editing files).
I confirm. In KDE, the default shortcut in KWin to copy a screenshot on the current window to the clipboard is Alt+Print. But it doesn't work at all. Trying to assign Alt+Print manually results in "The key you just pressed isn't supported by Qt." KDE 4.2.1, Qt 4.5.0. Was the same though with KDE 4.2.0, KDE 4.1.3 and Qt 4.4.2. The same happens for the "Web/Home" key on many "Internet keyboards". All buttons work (Back, Forward, Mail, Search, Calculator, etc, etc) except for the Web/Home one; it also results in "not supported by Qt."
I figured there are more default shortcuts that don't work because of this bug. For example, Alt+Shift+F12 is bound to "Suspend compositing" by default. However, it doesn't work. Trying to use this combination in the shortcut editor also results in a "the key you just pressed isn't supported by Qt."
Do you by chance use strg+shift to switch between to keyboard layouts? [ bash : 1007 ] $ setxkbmap -display $DISPLAY -print xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwertz)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+de(nodeadkeys)+inet(microsoftpro)+us:2+group(shifts_toggle)+group(lctrl_lshift_toggle)" }; xkb_geometry { include "microsoft(natural)" }; }; see the group group(lctrl_lshift_toggle) there. Mike
Hmm, I do use shift+ctrl. xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+us+inet(microsoftinet)+gr:2+de:3+group(alt_shift_toggle)" }; xkb_geometry { include "pc(pc104)" }; }; I can't seem to be able to disable this though. I uncheck "Alt+Shift" in the Keyboard Layout's "Advanced" tab and hit "Apply", but setxkbmap still reports alt_shift_toggle and I can keep switching using Alt+Shift. Disabling it seems to have no effect.
One switch method has to be active. So use "Both shift ..." for example. That is much less likely to interfere with something else.
And "alt+print" not working thing. Complain to you keyboard manufacturer. He should have given you and extra sysreq key. Now alt+print is sysreq. [ bash : 1005 ] $ xmodmap -pke | grep -i print 104:keycode 111 = Print Sys_Req Print Sys_Req Print Sys_Req I can't have alt+print too. It worked if you put it into the config file manually because someone patched kde to do bad things and interpret sysreq as print hardcoded. I removed that because it is not standard and only works on some keyboards. So in kde4.3 the workaround stops working too. I will close this bug as invalid because both parts are not kde's fault or responsibility.
Who's responsibility is it for the Web/Home key not working?
Qt's. But we know and hopefully get something done about it since nokia opened the repository to 3rd parties.