Description of problem: Logging in to Gnome on Wayland, my key repeat settings are ignored. Version-Release number of selected component (if applicable): Fedora 22 Gnome 3.16 libinput 20-21 How reproducible: Always Steps to Reproduce: 1. Log in to a Gnome wayland session 2. Change Repeat Key settings in Gnome settings 3. Test settings Actual results: The settings are ignored. Expected results: Settings take effect. Additional info:
This is Xwayland bug. Xwayland does not implement key-repating at all
sent a patch to devel list to fix it http://lists.x.org/archives/xorg-devel/2015-August/047169.html
Thanks, I think the fix made it into Fedora 22. Key repeat settings are working for gnome-terminal. Unfortunately, it isn't working for some apps, like xterm. I've started using xterm over gnome-terminal because of a separate wayland+gnome issue: https://bugzilla.redhat.com/show_bug.cgi?id=1242191
(In reply to somethingsome2000+redhat from comment #3) > Thanks, I think the fix made it into Fedora 22. Key repeat settings are > working for gnome-terminal. Unfortunately, it isn't working for some apps, > like xterm. I've started using xterm over gnome-terminal because of a > separate wayland+gnome issue: Nope, the patch is still hanging on list, that's why it's not working with xterm. Gnome-terminal just started using pure wayland instead of Xwayland I think.
(In reply to mchalupa from comment #2) > sent a patch to devel list to fix it > http://lists.x.org/archives/xorg-devel/2015-August/047169.html The patch got merged upstream
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.