To the Mate package maintainers

[Bastien Nocera]

On Tue, 2013-01-22 at 20:31 +0100, Nicolas Mailhot wrote:
> But do not try to wake it up by pressing num lock twice fast. It
> should be
> a noop but you can hit a gnome race and hose the system

That was fixed a couple of months ago. Please replace with up-to-date
complaints.

commit 15baf34186c6b5886b26e5a37698893be36f510b
Author: Bastien Nocera <hadess at hadess.net>
Date:   Tue Nov 6 19:13:12 2012 +0100

    keyboard: Prevent potential infinite loop
    
    XKB would notify us in the same way if the lockedMods
    changed because of a programmatic, or a physical/human change.
    
    This causes us changing the Num-Lock state generating another
    event on top of the one we just processed, and might cause
    infinite loops and 100% CPU usage.
    
    Instead, we now only apply the settings:
    - on startup
    - when remember-num-lock is changed to true
    
    https://bugzilla.gnome.org/show_bug.cgi?id=679151