NVDA doesn't detect foreground change after win+d

cyrmax commented 9 months ago

Steps to reproduce:

Open any application, maybe it should be a QT app (in my case was TeamTalk 5.14);
Work normally, open other windows, desktops, browse the internet, etc;
Receive a bunch of notifications, for example from browser, Telegram, other programs;
Alt+tab to the QT app, for example teamtalk;
Move inside it, view something, navigate inside the window;
Press win+d to minimize all windows and jump to desktop;

Actual behavior:

At the first press of win+d visually desktop is shown but NVDA still thinks that it is inside Teamtalk window, you can navigate it and even change settings. To actually go to desktop you need to press win+d two more times, first to show teamtalk again and the second to actually go to desktop. I repeat, visually the desktop is shown and teamtalk window along with other windows is hidden properly as we expect from Windows after win+d hotkey. Important to know that this happens more often when you have lots of unread notifications in notification center. After I go to this center, clean everything I cannot reproduce the issue until i receive another bunch of notifications from several apps.

Expected behavior:

NVDA should always properly handle foreground changes and set focus to the window that is in foreground.

NVDA logs, crash dumps and other attachments:

nvda-no-focus-and-crash-on-log-open.log

System configuration

NVDA installed/portable/running from source:

Installed.

NVDA version:

Version: alpha-30035,709c3d9c (2024.1.0.30035)

Windows version:

Windows 10 22H2 (AMD64) build 19045.3636

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

TeamTalk v5.14 QT version with QT6. Or any other QT application with QT6 and sometimes with QT5.

Other information about your system:

N/A.

Other questions

Does the issue still occur after restarting your computer?

Yes, if I receive new notifications and do not view them.

Have you tried any other versions of NVDA? If so, please report their behaviors.

Didn't tried, but looks like in 2023.* this problem is reproduciable.

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?

For several hours this cures the problem but after a time the problem continues to happen.

seanbudd commented 9 months ago

This appears to be a Windows bug. Can you confirm this behaviour happens without a screen reader running or with Narrator?

Adriani90 commented 6 months ago

@cyrmax you say the COM registration fixing tool temporarily fixes this issue. Did you try to restart your computer right after performing the COM registration fixing tool? Are you still having this issue with NVDA 2024.1 Beta 10?

@seanbudd given the COM registration fixing tool has an effect on this, I guess something in the Windows on that machine is unregistering some dlls repeatedly. @cyrmax do you have software that gets updates automatically in a very short period of time? Or do you install or uninstall things while reproducing this issue? If yes, please provide a list of programs that get updates or that you install / uninstall while this issue occurs.

nvaccess / nvda