-
-
Notifications
You must be signed in to change notification settings - Fork 617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Often, entry into the python console causes modifier keys to stick #12348
Comments
I have sometimes encountered modifier keys remaining in down state for a long time (also before 2020.4) but not so often and not necessarily in the console. In this case, I press all the modifiers one by one (both control, shift, alt and 3 NVDA) and things turn back normal. Of course, it is not a solution. |
Yes, I have encountered this situation, but it is not easy to reproduce. |
I'm a huge NVDA Python Console user, can't remember a working day in the last 5 years or so without using it. |
Steps to reproduce:
Actual behavior:
I can't give an exact STR without describing the actual behavior, and because this problem is intermittent.
For the last many alphas (probably all since 2020.4, maybe before), entry into the python console causes the NVDA and control keys to stick, perhaps over 60% of the time. I then have to restart NVDA to clear the jam (there may be other ways, I don't recall).
For example: pressing NVDA+ctrl+z, waiting for the prompt to appear, and then starting to type "import", will cause first the mouse settings dialog to open, then the configuration profiles dialog.
Possibly after that, more typing will start interacting with the dialog, or the keys will continue to stick, which eventually leads to a config reversion once the "r" is reached.
problem with python console log fragment.txt
Expected behavior:
Core doesn't freeze, the modifier keys release, the python console allows normal typing.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-22516,a0089a2f
Windows version:
Currently 20H2 (OS Build 19042.928),
but this has gone back at least through V2004.
Name and version of other software in use when reproducing the issue:
It might be relevant that this usually happens while Firefox is running, and possibly only while I'm focused on Firefox. However, I am not sure about that.
FF 84 through FF 88.
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Many, see above. I don't think this goes back before the post 2020.3 alpha sequence.
If add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
The text was updated successfully, but these errors were encountered: