After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728055 - Apply keyboard repeat settings
Apply keyboard repeat settings
Status: RESOLVED FIXED
Product: mutter
Classification: Core
Component: wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
3.14.1
Depends on:
Blocks: wayland
 
 
Reported: 2014-04-11 21:06 UTC by Matthias Clasen
Modified: 2014-10-03 17:05 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
backend-native: Handle keyboard repeat settings (3.46 KB, patch)
2014-10-01 17:26 UTC, Rui Matos 		none Details | Review
backend-native: Handle keyboard repeat settings (3.79 KB, patch)
2014-10-02 13:19 UTC, Rui Matos 		committed Details | Review

Description Matthias Clasen 2014-04-11 21:06:48 UTC 
Mucha as for pointer configuration, mutter should read the settings that the control-center sets, and apply them.
Comment 1 Matthias Clasen 2014-09-30 12:37:13 UTC 
specifically, key repeat and numlock
Comment 2 Rui Matos 2014-10-01 17:26:07 UTC 
Created attachment 287531 [details] [review]
backend-native: Handle keyboard repeat settings

--

Let's leave NumLock state for another bug.

Key repeat settings are already working for the wayland frontend, the
only thing missing is the native backend for gnome-shell's own chrome
widgets (cue lament about needing to implement everything twice).
Comment 3 Jasper St. Pierre (not reading bugmail) 2014-10-01 18:05:56 UTC 
Review of attachment 287531 [details] [review]:

Are we sure this won't cause repeated events to be sent to Wayland clients?
Comment 4 Rui Matos 2014-10-02 13:19:33 UTC 
Created attachment 287585 [details] [review]
backend-native: Handle keyboard repeat settings

We need to tell clutter's evdev backend about the desktop's key repeat
settings so that our own key binding event processing and
gnome-shell's chrome widgets get their fake key events for continuous
key presses as they expect.

Note that the wayland frontend filters out these fake events and thus
wayland clients do not see them as specced.

--
Wrote a proper commit message that should answer your question.
Comment 5 Jasper St. Pierre (not reading bugmail) 2014-10-03 16:22:50 UTC 
Review of attachment 287585 [details] [review]:

Sure.
Comment 6 Rui Matos 2014-10-03 17:05:28 UTC 
Attachment 287585 [details] pushed as fa58752 - backend-native: Handle keyboard repeat settings