After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 599117 - A11y dialog does not enable SlowKeys or BounceKeys
A11y dialog does not enable SlowKeys or BounceKeys
Status: RESOLVED DUPLICATE of bug 96483
Product: gdm
Classification: Core
Component: general
unspecified
Other Solaris
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-20 21:05 UTC by Willie Walker
Modified: 2009-11-18 14:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Willie Walker 2009-10-20 21:05:30 UTC
The a11y dialog on the login screen doesn't appear to allow me to enable SlowKeys or BounceKeys.  Checking the check boxes appears to have no effect.  :-(
Comment 1 Willie Walker 2009-11-11 18:21:26 UTC
In digging into the sundry of a11y settings spread across a multitude of areas (see http://live.gnome.org/Accessibility/Mechanics), I think I figured out what is going on here.

It appears as though the features are being enabled, but their default timeout values are set to 0, effectively disabling their behavior.  See the bouncekeys_delay and slowkeys_delay values in http://git.gnome.org/cgit/libgnome/tree/schemas/desktop_gnome_accessibility_keyboard.schemas.in

I'm not sure if this is a bug in the schemas file (I believe the default value should be 300 for both) or something that needs to be carried over to gdm in some way.
Comment 2 Brian Cameron 2009-11-18 01:52:09 UTC
Why are the system default values set to 0?  This seems rather pointless since the configuration file seems to also provide bouncekeys_enable and slowkeys_enable configuration options to control whether they are enabled or not.

I am guessing most users don't see this problem in the user session since I'm guessing that the preferences dialog sets the value to a reasonable default when it is enabled via the GUI.

GDM just picks up the system defaults for configuration options.  So, if this is the problem, then wouldn't it make more sense to fix this in libgnome so that the default values are set to the right values?

The GDM greeter does have a configuration file that allows GDM to override certain settings.  We could also set it there, but it seems the wrong place to me.
Comment 3 Willie Walker 2009-11-18 14:08:52 UTC
(In reply to comment #2)
> Why are the system default values set to 0?  This seems rather pointless since
> the configuration file seems to also provide bouncekeys_enable and
> slowkeys_enable configuration options to control whether they are enabled or
> not.

It seems that way back in January 2003, someone named Jody Goldberg decided these were reasonable values:

7d65dd2b schemas/desktop_gnome_accessibility_keyboard.schemas.in (Jody Goldberg  2003-01-08 07:42:34 +0000  65)               <default>0</default>

7d65dd2b schemas/desktop_gnome_accessibility_keyboard.schemas.in (Jody Goldberg  2003-01-08 07:42:34 +0000 144)               <default>0</default>

The comment from that change seems to be: "set defaults to 0 to fix #96483"

I'll reopen bug #96483.

*** This bug has been marked as a duplicate of bug 96483 ***