After locking and unlocking Windows, NVDA modifier key doesn't work #1856

Closed
nvaccessAuto opened this Issue Oct 21, 2011 · 11 comments

1 participant

@nvaccessAuto

Reported by surveyor on 2011-10-21 10:47
To reproduce:
Logg-off pressing windows+L
Logg-in again.
You should see NVDA keys doesn't work.
To make it work, iether go to the desktop pressing windows+M or restart NVDA.

@nvaccessAuto

Comment 1 by jteh on 2011-10-21 10:50
What operating system? I've seen this sometimes in Windows XP, but never in later versions.
Changes:
Changed title from "After logging-off and logging-in windows, NVDA modifier keys doesn't work" to "After locking and unlocking Windows, NVDA modifier key doesn't work"

@nvaccessAuto

Comment 2 by surveyor (in reply to comment 1) on 2011-10-21 11:25
Replying to jteh:

What operating system? I've seen this sometimes in Windows XP, but never in later versions.

At least, It occurs on windows 7 32 bit machine which I'm currently using.

@nvaccessAuto

Comment 3 by jteh on 2011-10-21 11:28
I assume you're just pressing Win+l, typing your password and pressing enter? What does NVDA say after you unlock?

@nvaccessAuto

Comment 4 by surveyor (in reply to comment 3) on 2011-10-21 12:14
Replying to jteh:

I assume you're just pressing Win+l, typing your password and pressing enter? What does NVDA say after you unlock?

NVDA just reads the title of the window which is active before locking. But, I've previewed NVDA log and, I've noticed Windows key remained pressed. Because, even if I don't press windows key, log adds windows key to each key presses. I think that is the reason why the problem disappears after pressing windows+m.

@nvaccessAuto

Comment 5 by jteh on 2011-10-21 12:33
Ah. I can reproduce it in Windows 7 now too. It occurs if the Windows key is down at the point where Windows locks. Normally, I let go of the Windows key really quickly after pressing Win+l, but if I keep holding it for a bit longer, it sticks for me too. This will also depend on how fast Windows locks on your system.

@nvaccessAuto

Comment 6 by heikofolkerts on 2012-05-17 11:18
It is also enough when just pressing the Windows key itself after unlocking. This solution makes it easy to work arround.
I suppose that this is a bug of Windows itself.

@nvaccessAuto

Comment 7 by jteh on 2012-05-17 21:33
I think we can solve this for Windows Vista and later, but not Windows XP. We should clear keyboardHandler.currentModifiers if a switch to a secure desktop is detected.
Changes:
Milestone changed from None to 2012.3

@nvaccessAuto

Comment 8 by jteh on 2012-06-06 09:07
Fixed in f90d181 for Windows Vista and later.
Changes:
State: closed

@nvaccessAuto

Comment 9 by surveyor (in reply to comment 8) on 2012-06-07 20:32
Replying to jteh:

Fixed in f90d181 for Windows Vista and later.

Two different result:
I've tried on a computer 32bit windows 7 and no problem. I've tried with windows 7 64bit and I've got NVDA error sounds when I pressed windows+l to lock and after unlocking. Furthermore, I couldn't use NVDA key until I press Windows key. Ataching a log
Changes:
State: reopened

@nvaccessAuto

Attachment nvda.log added by surveyor on 2012-06-07 20:34
Description:

@nvaccessAuto

Comment 10 by jteh on 2012-06-07 23:15
Oops. I broke that with an unrelated change. Fixed again in 66214dd.
Changes:
State: closed

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2012.3 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment