SUMMARY I have three launch keys on my keyboard, they are intended for the calculator apps but I remap and use them as I want. In 5.27 they worked perfectly fine, but in 6.01, kde does not recognise the first two and maps the third one to F9. STEPS TO REPRODUCE 1. Press the launch keys OBSERVED RESULT Nothing happens for the first two, the third one acts like F9 EXPECTED RESULT The keys should work how I mapped them to work SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1.71-1-lts (64-bit) (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2
I can confirm something is not OK with extra keyboard keys on Plasma 6. I have Logitech MX Keys keyboard with a dedicated calculator button. In `xev` it is correctly reported to produce XF86Calculator event: ``` KeyPress event, serial 41, synthetic NO, window 0x9800001, root 0x545, subw 0x0, time 98906706, (-215,321), root:(975,945), state 0x10, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 41, synthetic NO, window 0x9800001, root 0x545, subw 0x0, time 98906806, (-215,321), root:(975,945), state 0x10, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ``` but in System Settings it is not recognised, and KCalc is not opened any more when pressing the button. With Plasma it worked OK.
KDE no longer maps XF86Calculator to Launch1, as Qt has stopped doing that for a long time. Now KDE maps XF86Calculator to Qt::Key_Calculator, as is done upstream. But upstream patch (https://codereview.qt-project.org/c/qt/qtbase/+/535951) correctly mapping XF86Calculator to Qt::Key_Calculator is not included in 6.6.2, but will be included in 6.6.3 and 6.7 releases. If you go to system settings - shortcuts, the shortcut for kcalc should be Calculator (that has been changed from Launch1). That will start working once you install a Qt version containing the patch. So I am going to close this as UPSTREAM now. Feel free to reopen if this continues to happen in a Qt version containing https://codereview.qt-project.org/c/qt/qtbase/+/535951.