Forwarding this bug from a ubuntu reporter:
When the Keyboard Accessibility settings for Enabling Sounds and Modifier Keys have been set - but NOT set to disable if more than one key is pressed - the settings stop working fairly rapidly after most reboots.
When the Keyboard Accessibility settings for Enabling Sounds and Modifier Keys have been set - but NOT set to disable if more than one key is pressed - the settings stop working fairly rapidly in Hardy AMD64 and after most reboots.
1. This is extremely annoying for those of us who need to hear when a modifier key is pressed.
2. In Hardy AMD64 the Caps Lock key does not beep when modifier sounds are enabled - in Feisty it does.
It seems that if a modifier and another key are pressed at the same time it disables the Keyboard Accessibility settings for Enabling Sounds and Modifier Keys, even though "Disable if two keys pressed together" is NOT selected.
I have confirmed that the CapsLock key does not beep in Hardy Beta AMD64 but it does in Feisty.
Note that if "Disable sticky keys if two keys are pressed together", this is NOT changed in the Configuration Editor>desktop>gnome>accessibility>keyboard>"stickykeys_two_key_off" check box.
This is constantly reset (i.e. ticked) either by booting or something else. It is not possible to determine exactly when it gets reset as one does not know until after the event.
Please - this has been reported for years - please can more attention be paid to this minority group of users who need their Accessibility settings to be remembered by the system. It really is very important to some of us.
I do not really see how this is related to xkeyboard-config. xk-c has no settings related to accessibility. Could you please explain what exactly (in xk-c!) breaks the expected behavior?
Sorry, looks like this was misfiled originally.