Hi Daniel, This has been already privately discussed but I'll put it here so that it's not forgotten. It looks to me that the problem with XkbSetDetectableAutoRepeat is still present in git master. I don't have a proper environment to test the latest code, but it doesn't seem to have been fixed. At an early stage (XkbProcessKeyboardEvent, AccessXKeyboardEvent), XkbLastRepeatEvent is initialized to point to an internal event. Then the actual detectable autorepeat functionality has been implemented in XkbFilterEvents by checking the value of XkbLastRepeatEvent. The problem is that between these two points the event has been copied to a core or extension event that has a different address (eg. in DeliverFocusedEvent). Before internal events this problem affected only core events. After looking at the code it seems that this problem may be present also with extension events as the internal events have a different address as the copied extension events. Is it just a matter of copying correct address to XkbLastRepeatEvent in EventToCore/EventToXI?
*** This bug has been marked as a duplicate of bug 22515 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.