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 673084 - warning about Num Lock is silly on a desktop machine
warning about Num Lock is silly on a desktop machine
Status: RESOLVED DUPLICATE of bug 662093
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-29 14:28 UTC by Dan Winship
Modified: 2012-03-30 22:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dan Winship 2012-03-29 14:28:42 UTC
The "You have the Num Lock key on" warning is silly on a desktop machine, since the difference between number keys and arrow keys is visible even in password-entry mode, so the user will figure it out right away.

I assume the warning is there for people on laptops, where having Num Lock on would cause letter keys to turn into numbers, which would be a problem. But if so, then it should only be shown on laptops. And if we can't reliably tell that the user is on a laptop, then it would be better to just drop the warning entirely, because it will more or less always be shown on desktop machines, and so eventually the user will completely stop noticing it, and then one day it says "You have the Caps & Num Lock keys on" instead they won't even realize it.

(Alternate possibility: only show the warning after the user types a KP_whatever key.)
Comment 1 Ray Strode [halfline] 2012-03-30 22:24:24 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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