Comment 8 for bug 191181

Revision history for this message
truant (launchpad-ninj4) wrote :

Stickykeys in KDE works as one would expect, and retains it's settings - but the status notification panel applet hasn't been ported to KDE4 yet. So you can use stickykeys but you can't tell what state they're in. Which is actually worse.

Currently running Mint 6, which is basically a themed intrepid with a fancy menu - it uses the ubuntu repositories for all the important stuff, so the following should work on any (gnome+debian)ish system.

On my system, the following is is the only way I can find out what the actual gconf settings are - gconf-editor reports that stickykeys is enabled (it's not) and that two_key_off is off (it's on), whereas:

 gconftool-2 -R /desktop/gnome/ | grep stickykeys

gives me:

 stickykeys_modifier_beep = true
 stickykeys_enable = false
 stickykeys_two_key_off = true

Here's the clever bit. Set the appropriate keys:

 gconftool-2 --set /desktop/gnome/accessibility/keyboard/stickykeys_two_key_off --type bool 0
 gconftool-2 --set /desktop/gnome/accessibility/keyboard/stickykeys_enable --type bool 1
 gconftool-2 --set /desktop/gnome/accessibility/keyboard/stickykeys_modifier_beep --type bool 0

grepping the output of the -R command, now, gives:

   stickykeys_modifier_beep = false
   stickykeys_enable = true
   stickykeys_two_key_off = false

Which is right, and works like it says it should. (!) And it seems to stay working too. (!!) I haven't rebooted for a while, but I have logged out/in a bit.

hope this helps someone.