Bug 784746 - gnome-screensaver shows incorrect status for numlock
Summary: gnome-screensaver shows incorrect status for numlock
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-26 01:32 UTC by Andrew Cathrow
Modified: 2014-09-07 22:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-26 15:15:51 UTC
Type: ---


Attachments (Terms of Use)

Description Andrew Cathrow 2012-01-26 01:32:28 UTC
See https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/841541 which seems to be a direct match

Filing under x server after discussion with halfline and jrb


gnome-screensaver-3.2.0-1.fc16.x86_64
xorg-x11-server-Xorg-1.11.3-1.fc16.x86_64

the gnome-screensaver unlock dialog shows two indicators that the numlock key is on (both with an icon the text field and with text in the dialog).
The key is not on.

There seems to be no way to clear that indicator (reboot, etc).

The numlock key is not on, if I press the numlock key there is no change to the indicators but the numlock feature works, if I press it again, it disables the numlock feature, however the indicators continue to show numlock is on

Comment 1 Satish Balay 2012-08-25 15:24:32 UTC
I just noticed the exact same behavior on 2 different machines with F16/gnome3

It appears if I key in numlock during normal gnome session [which I normally never use] - the status stays as on [on the gnome-screensaver passwd prompt] - even if you toggle numlock off [either during gnome regular session or during the screen saver login prompt]. And this is persisting after reboot aswell.

So I'm not sure how to clear up this state info in gnome..

gnome-screensaver-3.2.0-1.fc16.x86_64
xorg-x11-server-Xorg-1.11.4-3.fc16.x86_64
kernel-3.4.9-2.fc16.x86_64

Comment 2 Fedora End Of Life 2013-01-16 21:02:59 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-26 15:15:54 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.