I couldn't run gconf-editor (gconf-gnome) on the host whilst this bug was occuring, so i used the following commands via a ssh:
gconftool -t bool -s /apps/gnome_settings_daemon/plugins/a11y-keyboard/active false sudo gconftool -t bool -s /apps/gnome_settings_daemon/plugins/a11y-keyboard/active false sudo restart gdm
^using karmic. try "sudo /etc/init.d/gdm restart" in place of the last line if it doesn't work on jaunty. (subscribing to this bug so i remember to change back if/when it's fixed. thanks)
I couldn't run gconf-editor (gconf-gnome) on the host whilst this bug was occuring, so i used the following commands via a ssh:
gconftool -t bool -s /apps/gnome_ settings_ daemon/ plugins/ a11y-keyboard/ active false settings_ daemon/ plugins/ a11y-keyboard/ active false
sudo gconftool -t bool -s /apps/gnome_
sudo restart gdm
^using karmic. try "sudo /etc/init.d/gdm restart" in place of the last line if it doesn't work on jaunty.
(subscribing to this bug so i remember to change back if/when it's fixed. thanks)