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 363427 - slow key dialog not controllable by keyboard
slow key dialog not controllable by keyboard
Status: RESOLVED OBSOLETE
Product: gnome-settings-daemon
Classification: Core
Component: a11y-keyboard
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2006-10-19 14:48 UTC by Sebastien Bacher
Modified: 2019-03-20 10:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Sebastien Bacher 2006-10-19 14:48:39 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/control-center/+bug/65921

"When shift is held down for a few seconds and the irritating dialog pops up, it cannot be controlled by keyboard, i.e. I cannot hit "inactivate" by keyboard like I can in any other window. I must use the mouse. This is confusing."
Comment 1 Denis Washington 2008-01-16 16:16:58 UTC
The problem is that, when the dialog appears, slow keys are already activated - this means that the keyboard combination needs to be hold some time so that it is recognized (after all, that's what slow keys are about). Maybe it would be better if we activated it after the dialog shows up or, if we don't have any control over that, disable it and enable it again if the user chooses "Activate" in the dialog.
Comment 2 Denis Washington 2011-08-23 06:45:22 UTC
Does holding down Shift even still activate slow keys in GNOME 3? I am not able to reproduce this now.
Comment 3 GNOME Infrastructure Team 2019-03-20 10:49:44 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/157.