Version: KDE 3.2.1 and 3.3.1 (using KDE KDE 3.3.1) Installed from: SuSE RPMs OS: Linux I have a "Logitech Internet Navigator Keyboard" which features several extra "multimedia" keys. In addition the 12 F-keys can be operated in two modes, switchable via an "F-Lock" key analogous to the NumCapsLock keys. After fixing the SuSE 9.1 install (with 9.0 it worked out of the box), I get all the keys to report keycodes and symbols in xev. Under KDE 3.2.1 and after the update to 3.3.1 via SuSE rpms: _All_ of these keys _can_ be configured in kmenuedit to start up programs. But _some_ of these keys _cannot_ be configured as shortcuts within the program. I.e. the key "F10" when switched to alternate mode can be set in kmenuedit to start konqueror, but it cannot be set as a shortcut to close the program in either konqueror or kmail (instead of ctrl+q). The error-window reads: >>Die Tastenkombination "" ist bereits der globalen Aktion "Defaults timestamp" zugeordnet. Möchten Sie die neue Zuordnung vornehmen?<< A list of what works and what doesn't: code symbol kmenuedit shortcut 236 XF86Mail y y 168 XF86Messenger Y n! 169 XF86WebCam y n! 144 XF86AudioPrev y y 153 XF86AudioNext y y 237 XF86AudioMedia y y 176 XF86AudioRaiseVolume y y 174 XF86AudioLowerVolume y y 160 XF86AudioMute y y 162 XF86AudioPlay y y 164 XF86AudioStop y y 171 XF86VendorHome y n! 229 XF86Search y y 172 XF86Shop y n! 230 XF86Favorites y y 178 XF86HomePage y y 223 XF86Standby y y 167 XF86ScrollClick y n! 234 XF86Back y y 233 XF86Forward y y 173 XF86New y n! 165 XF86Reply y n! 175 XF86MailForward y n! 179 XF86Send y n! 180 XF86Finance y n! 194 XF86Community y n! 185 XF86Start y n! 186 XF86Save y n! 187 XF86MyComputer y y 195 XF86Documents y n! 196 XF86Pictures y n! 197 XF86Music y n! It would be great if you guys could get that working! Otherwise: Fantastic work! I'm using KDE sice 1.1 and I love it since 2.0. Last week I installed Linux, of course with KDE, on a friend's computer who said that he was sick of viruses. Cheers Peter Rabitsch PS: Because several applications (konqueror and kmail and maybe others) show the same behavior the bug might be in a library, in a part which is not used by kmenuedit.
i have the same problem. (or looks like) With some XF86 the shortcuts doesn't work. Even if i can set the shortcut. For example, with kmenuedit, i can press XF86WWW to set the shortcut for firefox (the key XF86WWW is writen) but when i press the key, nothing happens. I have a Logitech Cordeless Keyboard. When i try with xev, the key works too. There is one think strange, sometimes, the shortcut works, sometimes not, For now, i didn't find when it works and when not. Another thing : I tried to set Ctrl+XF86WWW and it works. sorry for my bad english :) thanks for your work, i love kde :)
I forgot to say that i am on debian unstable and kde 3.5 but i had the same problem with kde 3.4.
I can reproduce this bug. In kcontrol, keys as XF86Close work as a general shortcut but not as a application shortcut. Thus, these keys are not usable in any application for its (local) shortcuts, but you can set them in applications' global shortcuts if exist (e.g. Kopete). The problem is not the keycode but the xmodmap identifier.
Same problem for me with kde 3.5.x and now 4.1.0 (debian testing & experimental). But a related problem with 4.1.0 is that the names of keys shown when setting a shortcut often don't correlate with the names xev reports. E.g.: xev kde shortcut XF86LaunchA Launch (C) XF86LaunchB Launch (D) XF86LaunchC Launch (E) XF86LaunchD Launch (F) XF86LaunchE <doesn't work> XF86LaunchF <doesn't work>
Is this still an issue in 4.2? Thanks!
(In reply to comment #5) > Is this still an issue in 4.2? Thanks! Yes, it is. When you try to assign one of those shortcuts, there is a popup saying that "The key pressed isn't supported by Qt" (or some such, in German it says, "Die gerade gedrückte Taste wird von Qt nicht unterstützt."). So it seems that this would not be an issue with KDE as such but rather with Qt.
I can confirm the XF86WWW problem on KDE 4.2. Steps to reproduce ------------------- - In systemsettings -> Input Actions -> Trigger click Shortcut - Press key "Internet" on the keyboard. Result ------ Error message box "Unsupported key" with text "The key you just pressed isn't supported by QT". All other keys are working. The key "Internet" (keycode 178) was assigned to XF86HomePage in xkeyboard-config 1.4 (which worked), but this seems to be changed now in xkeyboard-config 1.5. List of multimedia keys as reported by xev -------------------------------------------- keycode 178 (keysym 0x1008ff2e, XF86WWW) keycode 236 (keysym 0x1008ff19, XF86Mail) keycode 229 (keysym 0x1008ff1b, XF86Search) keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume) keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume) keycode 160 (keysym 0x1008ff12, XF86AudioMute) Versions / Configuration --------------------------- ArchLinux KDE 4.2.0 QT 4.4.3 xorg-server 1.5.3-4 xkeyboard-config 1.5-1 Keyboard: no name "Model No KB-9908" with multimedia keys Internet, Email, Search, Volume-, Volume+, Mute /etc/xorg.conf Option "XkbModel" "logiaccess"
I noticed regressions with some hotkeys. On KDE 3.5.10 every single key worked, but on KDE 4.2.1 several keys get the "The key pressed isn't supported by Qt" message while trying to assign a global shortcut. Here's a full list: keycode 180 (keysym 0x1008ff18, XF86HomePage) keycode 151 (keysym 0x1008ff2b, XF86WakeUp) not supported keycode 150 (keysym 0x1008ff2f, XF86Sleep) not supported keycode 163 (keysym 0x1008ff19, XF86Mail) keycode 148 (keysym 0x1008ff1d, XF86Calculator) keycode 172 (keysym 0x1008ff14, XF86AudioPlay) keycode 174 (keysym 0x1008ff15, XF86AudioStop) keycode 173 (keysym 0x1008ff16, XF86AudioPrev) keycode 171 (keysym 0x1008ff17, XF86AudioNext) keycode 169 (keysym 0x1008ff2c, XF86Eject) not supported keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume) keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume) keycode 121 (keysym 0x1008ff12, XF86AudioMute) keycode 179 (keysym 0x1008ff32, XF86AudioMedia) keycode 166 (keysym 0x1008ff26, XF86Back) keycode 167 (keysym 0x1008ff27, XF86Forward) keycode 136 (keysym 0xff69, Cancel) not supported keycode 181 (keysym 0x1008ff29, XF86Refresh) keycode 225 (keysym 0x1008ff1b, XF86Search) keycode 185 (keysym 0x1008ff78, XF86ScrollUp) not supported keycode 186 (keysym 0x1008ff79, XF86ScrollDown) not supported keycode 145 (keysym 0x1008ff58, XF86Cut) not supported keycode 143 (keysym 0x1008ff6d, XF86Paste) not supported keycode 141 (keysym 0x1008ff57, XF86Copy) not supported keycode 190 (keysym 0xff66, Redo) not supported keycode 139 (keysym 0xff65, Undo) not supported keycode 156 (keysym 0x1008ff41, XF86Launch1) keycode 157 (keysym 0x1008ff42, XF86Launch2) keycode 210 (keysym 0x1008ff43, XF86Launch3) Versions / Configuration --------------------------- Gentoo GNU/Linux KDE 4.2.1 QT 4.5.0 xorg-server 1.5.3 xkeyboard-config 1.4 xf86-input-evdev 2.1.3 Keyboard: Cherry CyMotion Linux "CYA Model 210XX" /etc/xorg.conf: Section "InputDevice" Identifier "Keyboard0:1" Driver "evdev" Option "Device" "/dev/input/by-id/usb-046a_0023-event-kbd" Option "XkbLayout" "de" Option "XkbVariant" "deadgraveacute" Option "XkbOptions" "compose:rwin,lv3:ralt_switch,altwin:left_meta_win,eurosign:e" EndSection Section "InputDevice" Identifier "Keyboard0:2" Driver "evdev" Option "Device" "/dev/input/by-path/pci-0000:00:02.0-usb-0:2:1.1-event-" Option "XkbLayout" "de" Option "XkbVariant" "deadgraveacute" Option "XkbOptions" "compose:rwin,lv3:ralt_switch,altwin:left_meta_win,eurosign:e" EndSection Section "ServerLayout" Identifier "seat0" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "AlwaysCore" # This is one keyboard coressponding to 2 event devices InputDevice "Keyboard0:1" "CoreKeyboard" InputDevice "Keyboard0:2" "AlwaysCore" EndSection
*** This bug has been confirmed by popular vote. ***
*** Bug 254231 has been marked as a duplicate of this bug. ***
I still have this problem(s). Keyboard is a Cherry CyMotion... via USB. Some keys work but have different names than xev gives them. Many keys are not supported by Qt (at least this is what it says). Some keys I can set using khotkeys but do not trigger anything. System Qt: 4.7.1 KDE: 4.6.00 (4.6.0) "release 6"
Most keys I've tried recently work, but not reliably when using multiple keyboards. E.g. the "lock screen" button on my thinkpad doesn't usually work now, starting from when I bound a key on an external keyboard to XF86ScreenSaver (usually only the one on the external keyboard works, though wierdly after doing this test with xev they both started working, even after closing xev). XEV for thinkpad key: KeyRelease event, serial 41, synthetic NO, window 0x1800001, root 0x266, subw 0x0, time 75582093, (74,85), root:(76,108), state 0x0, keycode 160 (keysym 0x1008ff2d, XF86ScreenSaver), same_screen YES, XKeysymToKeycode returns keycode: 124 XLookupString gives 0 bytes: XFilterEvent returns: False And for external keyboard: KeyRelease event, serial 43, synthetic NO, window 0x1800001, root 0x266, subw 0x0, time 75598454, (74,85), root:(76,108), state 0x0, keycode 124 (keysym 0x1008ff2d, XF86ScreenSaver), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
Is this still happening in Plasma 5.19 or a similarly recent version?
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 mark the bug 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!
Hello again :) The situation has improved, but the following keys still get ignored: keycode 185 (keysym 0x1008ff78, XF86ScrollUp) keycode 186 (keysym 0x1008ff79, XF86ScrollDown) There is no message about unsupported keys anymore, they just get ignored by Qt/KDE. The xev tool still reports them. I use the wayland session (No Xorg binary on the system. Xwayland only). System --------------------------- Gentoo GNU/Linux Kernel 5.8.8 KDE 5.19.5 Qt 5.15.1 libinput 1.16.1 Keyboard: Cherry CyMotion Master Linux
Thanks for the update; changing status.
I guess the question is, what would you expect those keys to do? Are they dedicated pgup/pgdn keys?
The bug here requests that all extra keys can be used to assign shortcuts, either global or within an application.
Ah OK. Moving to kglobalaccel then