Comment 1 by jteh on 2010-11-03 22:39
I'm guessing that control also doesn't work to silence speech, nor any other command? Does this always happen or only sometimes? What if you press NVDA+f12 again shortly after?
Changes:
Milestone changed from None to None

Comment 2 by Bernd on 2011-06-19 22:20
On my Windows XPSP3 machine this error occurs also. On the logon screen NVDA+12 and other NVDA commands work but after login all NVDA keys aktivated with NVDA+key don't work. Strangely Pressing Control to stop speech works. After few time NVDA+f12 works as expected.

Comment 3 by mdcurran on 2011-06-19 23:12
To be clear, do you mean that after logging in (you're now in Windows and are running the non-service copy of NVDA) NVDA+f12 does not work for a delaied amount of time? or am I miss-understanding.

Comment 4 by Bernd on 2011-06-19 23:29
yes, that's right. I was in windows and used the non-service-copy of nvda.

Comment 5 by briang1 on 2011-06-20 10:30
Just to clarify, did you allow the screensaver to come on, then hit a key to terminate it, or was this just because the log on screen was cancelled and nothing else.
I gave up on screensavers due to most screenreaders giving strange effects in one way or another upon return, or when they were running. Indeed, one strange thing is that the better the graphic card, the faster things started to work after it had been on, which makes me wonder if its not really nvda as such which is the problem but some kind of processor loading effect

PS why is O/S set to Vista if its XP pro?

Comment 6 by zahari_bgr on 2015-03-04 03:28
Hi,
I don't have access to an XP machine any more and I can't remember experiencing that, but I remember that on slow machines there is actually a slight delay between cancelling the screen saver and the operating system becoming usable.
So @briang1 might be right and this issue might have nothing to do with NVDA.

Comment 7 by jteh on 2015-03-16 05:06
It's possible that NVDA's idea of pressed modifier keys is wrong, as we don't get notified when the system switches to a secure desktop in XP. There are some ugly ways to detect this, but given that XP is now end-of-life anyway, I don't think it makes sense for us to invest resources into this. Assuming I'm right, if you're locking by pressing Windows+l, pressing the Windows key once will probably fix this. If you're locking via the control+alt+delete dialog, pressing control+alt once will probably fix this.
Changes:
Added labels: wontfix
State: closed