Skip to content
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

NVDA2022.3.3 throws error for a split second when computer goes to sleep #14475

Closed
cary-rowen opened this issue Dec 25, 2022 · 4 comments · Fixed by #14457
Closed

NVDA2022.3.3 throws error for a split second when computer goes to sleep #14475

cary-rowen opened this issue Dec 25, 2022 · 4 comments · Fixed by #14457
Labels
p5 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Milestone

Comments

@cary-rowen
Copy link
Contributor

cary-rowen commented Dec 25, 2022

Steps to reproduce:

alt+f4 Click on the sleep option in the dialog.

Actual behavior:

At this point you will hear NVDA beeping as the error is logged.

Expected behavior:

There are no errors.

NVDA logs, crash dumps and other attachments:

log.txt

System configuration

NVDA installed/portable/running from source:

installed

NVDA version:

2022.3.3, 2022.4Beta4 and Alpha-27364,

Windows version:

Windows 10 22H2 (x64) build 19045.2364

Name and version of other software in use when reproducing the issue:

None

Other information about your system:

None

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.

Yes

If NVDA 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

@cary-rowen cary-rowen changed the title NVDA throws error for a split second when computer goes to sleep NVDA2022.3.3 throws error for a split second when computer goes to sleep Dec 25, 2022
@Brian1Gaff

This comment was marked as off-topic.

@seanbudd
Copy link
Member

Thanks for reporting @cary-rowen, this is a known case. The error level log will be suppressed in #14457.

@cary-rowen
Copy link
Contributor Author

@seanbudd
OK, feel free to close this issue.

@seanbudd
Copy link
Member

We will keep it open to track the problem. Thank you for documenting this issue clearly, it will help reduce duplicates and improves the documentation of the PR to fix it.

@seanbudd seanbudd added p5 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. labels Jan 3, 2023
seanbudd added a commit that referenced this issue Jan 4, 2023
Closes #14475
Follow up for #14416

Summary of the issue:
#14416 added a log message at exception level.
This log message is for when the relative z-order for an NVDAObject and the lock screen cannot be determined.
While a noisy exception here is useful for alpha/beta testing of this code, this log message is almost always triggered once when locking windows. This is because the lock screen may not exist while windows is in the process of locking.

Description of user facing changes
Lower log level
@nvaccessAuto nvaccessAuto modified the milestone: 2023.1 Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p5 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants