desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #67154
[Bug 841541] Re: "num lock is on" warning remains even after num lock is turned off (thinkpad, numlock status for laptop and external keyboard different)
This is a weird message, as I am on a desktop computer and I have this
message in all password fields. My Numlock key must be on.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/841541
Title:
"num lock is on" warning remains even after num lock is turned off
(thinkpad, numlock status for laptop and external keyboard different)
Status in “gnome-screensaver” package in Ubuntu:
Triaged
Status in “gnome-screensaver” source package in Oneiric:
Triaged
Status in “gnome-screensaver” source package in Precise:
Triaged
Bug description:
Version: 3.1.5-0ubuntu6
Release: 11.10
After fiddling with Num Lock, I noticed that the lock window claimed
it was still enabled, and yet it is not.
Comments info:
"it might be connected with the fact that on (new) Thinkpads there are something like TWO num locks, one is for an external keyboard and the other - for the internal one."
Sequence of events:
* Turn on Num Lock.
* Lock the screen. (On a ThinkPad, I do this by pressing Fn+F2. Whatever option it is that means "lock the screen immediately", I have it turned on.)
* Tap a key to bring up the screen-locked/enter-password dialog.
* Observe the warning.
* Turn off Num Lock.
* Observe the warning is still there.
* Successfully unlock the screen.
* Lock the screen again.
* Observe the warning is still there.
* [Optional] Unlock the screen. File a bug against gnome-screensaver.
Not related to bug #835649, which concerns showing the warning when
Num Lock is enabled but not otherwise problematic, e.g. when using a
"full-size" (i.e. "has lots of extra keys") keyboard.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/841541/+subscriptions
References