Summary: | KWin-on-libinput ignores keyboard KCM settings; uses default repeat delay/rate | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Sam Edwards <CFSworks> |
Component: | libinput | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | broaden_acid002, bugseforuns, butirsky, kde, matthias.fauconneau, nate, putr4.s |
Priority: | NOR | Keywords: | wayland |
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-desktop/commit/3c880f6c941b946d15a4245c8feef2c4f3e0de8d | Version Fixed In: | 5.26 |
Description
Sam Edwards
2019-06-20 07:40:24 UTC
Can you submit that patch to Phabricator? https://community.kde.org/Get_Involved/development *** Bug 409536 has been marked as a duplicate of this bug. *** @Sam Do you need help with submitting the patch? Git commit 3b0f704e3b90b723a8516ce3fbff9bd18e2b11cf by Nate Graham, on behalf of Sam Edwards. Committed on 10/07/2019 at 23:13. Pushed by ngraham into branch 'Plasma/5.16'. Fix case-sensitivity typo in libinput configuration function Summary: This fixes the bug where KWin-on-Wayland doesn't respect keyboard repeat settings FIXED-IN: 5.16.4 Test Plan: 1. Start Wayland session 2. Open Wayland KCM and note the keyboard repeat/rate/delay 3. Go to keyboard preferences KCM and adjust the keyboard repeat/rate/delay 4. Open the Wayland KCM again and verify the keyboard repeat/rate/delay adjustments (it may be necessary to restart the Wayland session before this step) Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D22388 M +1 -1 input.cpp https://commits.kde.org/kwin/3b0f704e3b90b723a8516ce3fbff9bd18e2b11cf Rate setting is still not working after update to plasma 5.16.4 on Arch Linux even after relogin. Operating System: Arch Linux KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 Patrick, either reopen, or create a new ticket. Comments on closed bugs rarely get seen. *** Bug 410628 has been marked as a duplicate of this bug. *** Kubuntu 20.04, rate settings still not working. >Rate setting is still not working after update to plasma 5.16.4 on Arch Linux
even after relogin.
Please set to something non standard and include output of
WAYLAND_DEBUG=1 qtdiag |& grep keyboard
output on neon unstable [3068071,334] wl_registry@2.global(3, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3068072,417] -> wl_seat@6.get_keyboard(new id wl_keyboard@3) [3068073,268] wl_keyboard@3.repeat_info(25, 600) [3068073,292] wl_keyboard@3.keymap(1, fd 4, 53810) [3068107,012] wl_registry@12.global(3, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3068116,561] wl_registry@21.global(3, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) keyboardInputInterval: 400 keyboardAutoRepeatRate: 30 [3068207,640] -> wl_keyboard@3.release() urgh, indeed. This should be fixed > This should be fixed
As in on git master I assume? It still happens to me on Plasma 5.25.5 (more system info below).
Operating System: Arch Linux
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.6
Kernel Version: 5.19.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Hmm, maybe not then. At least I remember adding code that makes kwin process key repeat settings. A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1140 Git commit 3c880f6c941b946d15a4245c8feef2c4f3e0de8d by Vlad Zahorodnii. Committed on 12/09/2022 at 12:38. Pushed by vladz into branch 'master'. kcms/keyboard: Fix Notifiers field for KeyRepeat,RepeatDelay,RepeateRate options KeyRepeat, RepeatDelay, and RepeateRate have custom names. We need to specify those names in the Notifiers field otherwise kconfig source generator won't generate relevant notification code. M +1 -1 kcms/keyboard/keyboardmiscsettings.kcfgc https://invent.kde.org/plasma/plasma-desktop/commit/3c880f6c941b946d15a4245c8feef2c4f3e0de8d *** Bug 450319 has been marked as a duplicate of this bug. *** |