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 669597 - Sticky keys description rather misleading
Sticky keys description rather misleading
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Universal Access
3.3.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
3.10
Depends on:
Blocks:
 
 
Reported: 2012-02-07 19:05 UTC by Johannes Mockenhaupt
Modified: 2021-06-09 16:07 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Johannes Mockenhaupt 2012-02-07 19:05:05 UTC
The description of the sticky keys feature in the control center (Universial Access->Typing) reads "Treat a sequence of modifier keys as a key combination". This is IMHO wrong, as it describes the sticky feature with the locking mechanism DISABLED, while in actuality this very locking feature is enabled. So, if the user accidentially presses e.g. ctrl twice he/she will from then on out press ctrl with every key unless ctrl is unlocked. But the fact that a key can be locked is never told the user, nor is there any indication that a key is locked (there was the accessx status applet in GNOME 2.x, but that's gone, bug report here: https://bugzilla.gnome.org/show_bug.cgi?id=647711). If a user accidentially locks a key without knowing what key was locked (e.g. pressing shift together with ctrl), the user is left to figure out how to unlock an unknown key, likely ending up locking others in the process. This is tricky even if one knows about this.

Possible solutions in order of work they require:
1) change description to describe actual behaviour
2) add 'enable locking' as an additional setting
3) implement/port the accessx status-applet to GNOME3.
Comment 1 André Klapper 2012-02-07 20:16:55 UTC
Still in git master:
#: ../panels/universal-access/uap.ui.h:48
msgid "Treats a sequence of modifier keys as a key combination"
Comment 2 Johannes Mockenhaupt 2012-06-18 08:38:15 UTC
I won't be available for inqueries on this bug anymore. Feel free to close it.
Comment 3 Joanmarie Diggs (IRC: joanie) 2012-06-18 17:34:23 UTC
Possible alternative description: "Lock modifier keys until a non-modifier is pressed"
Comment 4 Matthias Clasen 2013-04-14 00:20:53 UTC
It looks like latch-to-lock is just broken.

Here is a debian bug report that seems to claim it fixed itself:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692396
but I am still seeing the problem in current f19
Comment 5 Bastien Nocera 2013-04-15 07:52:01 UTC
(In reply to comment #4)
> It looks like latch-to-lock is just broken.

Works fine here.

(In reply to comment #3)
> Possible alternative description: "Lock modifier keys until a non-modifier is
> pressed"

I don't like the "modifier" term though it's used elsewhere in the dialogue already.
Comment 6 Matthias Clasen 2013-04-16 00:28:45 UTC
How about "Allow to press keyboard combinations one key at a time" ?
Comment 7 Allan Day 2013-04-21 15:32:44 UTC
(In reply to comment #6)
> How about "Allow to press keyboard combinations one key at a time" ?

Sounds friendlier to me. "Allow to" is superfluous here though, so:

"Press keyboard combinations one key at a time"
Comment 8 André Klapper 2021-06-09 16:07:44 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new bug report at
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/

Thank you for your understanding and your help.