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 564045 - gnome-settings-daemon keyboard a11y plugin doesn't reset XKB state on exit
gnome-settings-daemon keyboard a11y plugin doesn't reset XKB state on exit
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: plugins
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on: 564042
Blocks:
 
 
Reported: 2008-12-10 22:17 UTC by Ray Strode [halfline]
Modified: 2008-12-17 16:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Restore XKB state on plugin deactivation (2.58 KB, patch)
2008-12-10 22:19 UTC, Ray Strode [halfline]
committed Details | Review

Description Ray Strode [halfline] 2008-12-10 22:17:34 UTC
(from https://bugzilla.redhat.com/show_bug.cgi?id=445898)

g-s-d will set up AccessX hooks for enabling slowkeys and stickykeys at the GDM login screen.  This is very useful for those who need these features to login.  g-s-d, however, doesn't turn it back off when getting killed when the user's session is started.  

If a user logs into say IceWM or fvwm and holds shift for more than 8 seconds then slowkeys turns on and they get no notification of why the keyboard stopped working.

The a11y keyboard plugin should reset AccessX XKB state on plugin deactivation to what it was when the plugin was activated.

Note, this bug blocks on bug 654042 getting fixed, so that the plugin deactivation handler actually gets called.
Comment 1 Ray Strode [halfline] 2008-12-10 22:19:39 UTC
Created attachment 124387 [details] [review]
Restore XKB state on plugin deactivation