| Summary: | The launch keys on my keyboard does not work | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | yunusaydin590 |
| Component: | kcm_keys | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | minor | CC: | fanzhuyifan, kde, nicolas.fella, oleksandr |
| Priority: | NOR | Keywords: | qt6, regression, usability |
| Version First Reported In: | 6.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
yunusaydin590
2024-03-07 07:31:25 UTC
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. |