I figured out a workaround for this, but I don't know what the problem with the underlying code is. These are the steps I followed and now Sticky Keys is working. I was just going through gconf-editor options when I came across this thing.
1. Start gconf-editor (Configuration Editor).
2. Go to /desktop/gnome/accessibility
3. I had enabled Sticky Keys from Keyboard preferences before starting gconf-editor. I found that stickykeys_enable was checked. stickykeys_modifier_beep was checked. stickykeys_two_key_off was also checked. This is important, because I had specifically not enabled this option from Keyboard preferences. Nevertheless, it was checked. I unchecked this, and set value for timeout to an extremely large value (24000).
Since then, Sticky Keys has been working fine. So I guess it's some issue with 'Disable sticky keys if two keys are pressed together' being active when it shouldn't be, right?
Another thing. Set timeout to a value other than 120, and then check / uncheck any other Sticky Keys related gconf option. The timeout will get reset to 120. Is this expected behavior or a bug? (If it's the latter, should I file a new bug for this?)
I figured out a workaround for this, but I don't know what the problem with the underlying code is. These are the steps I followed and now Sticky Keys is working. I was just going through gconf-editor options when I came across this thing.
1. Start gconf-editor (Configuration Editor). gnome/accessibi lity modifier_ beep was checked. stickykeys_ two_key_ off was also checked. This is important, because I had specifically not enabled this option from Keyboard preferences. Nevertheless, it was checked. I unchecked this, and set value for timeout to an extremely large value (24000).
2. Go to /desktop/
3. I had enabled Sticky Keys from Keyboard preferences before starting gconf-editor. I found that stickykeys_enable was checked. stickykeys_
Since then, Sticky Keys has been working fine. So I guess it's some issue with 'Disable sticky keys if two keys are pressed together' being active when it shouldn't be, right?
Another thing. Set timeout to a value other than 120, and then check / uncheck any other Sticky Keys related gconf option. The timeout will get reset to 120. Is this expected behavior or a bug? (If it's the latter, should I file a new bug for this?)