nvaccess
System no longer goes into hybernate/standby
Steps to reproduce:
Run installed or portable NVDA version 2023 or latest alpha and observe if computer will go to sleep mode after some time.
Actual behavior:
Computer stays awake even anyone does not work on it.
Expected behavior:
Computer should go to sleep mode after some time of inactivity.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source and its version:
2023.3.4 and latest alpha as on27.03.24 (both installed and portable)
Windows version:
W10 22h2 with march updates
Name and version of other software in use when reproducing the issue:
n/a
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.
It worked normally, computer went to sleep mode when NVDA 2022.4 has been used.
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
Possible duplicate of #14913
@jcsteh wasn't #15097 supposed to fix this? It says merged, but there's nothing about that change in the changes file, and this user seems to still face it.
Yes, #15097 should have fixed this, and some users confirmed that it did. I think it's not listed in the changes file because it was merged before WASAPI was included in a release.
I can't think of any reason WASAPI should be causing this now. I'd be suspicious of the recently added code to play silence, except that this isn't in a release yet, only in alpha.
Have you tried disabling WASAPI in advanced settings, and checking if your machine can go to sleepp after NVDA's restart?
I cannot reproduce in nvda 2023.2 on a Lenovo machine, and also not reproducing on an Asus machine with last alpha
@gregjozk can you please profide more information on how you reproduced this issue?
- was any audio or video media playing in foreground or background?
- Which energy plan are you using in the batery settings in your Windows?
- Were there any Windows updates or other updates of any software loading / instaling in the background while you were waiting for the laptop to go in hibernate mode?
- Was any other software loading anything in background (e.g. downloading something etc.)?
Please test this again and report the result:
- Turn on the machine
- Start NVDA
- Make sure WASAPI is enabled in advanced settings
- Make sure the "keep the device awake" value in NVDA audio settings category is set to <= 30 seconds
- Don't start any program, just make sure you can navigate e.g. with speech on the desktop
- Let the machine alone for a longer time and check after a while if it is still active.
considering all this, are you still reproducing the issue?
We would like more information on steps to reproduce before we give this a priority rating. If this is reproducible by people then this becomes a higher priority fix.
Adding to the testing steps above:
- If it does not go to sleep with NVDA running: quit NVDA, and leave the machine alone again until the sleep duration has passed, and determine if it has gone to sleep then.
You can adjust the time to sleep timer down to five minutes or so for these tests.
Hello,
excuse me for very delayed responce. It seems, that this problem has been solved. Accidantly I did not disabled all addons manually. When I restarted NVDA without addons in "exit dialog - NVDA+q" all was fine. Issue was already opened at problematic addon, so this ticket can be closed. Again, I'm very sorry for raisin this issue.
See: #https://github.com/paulber19/NVDAExtensionGlobalPlugin/issues/15
Hi. I actually noticed this add-on malfunctioning when Wasapi is activated. But I reproduced this malfunction with a portable version of NVDA version alpha-31645, bf96860d and without add-ons., Wasapi activated:
- configure Windows (for my part Windows 10 22H2) to put the computer to sleep after one minute.
- start NVDA,
- type "NVDA+Alt+s" once. NVDA says that NVDA and apps are on both channels.
- no longer touch the keyboard. The computer does not go to sleep after one minute. Stop NVDA and no longer touch the keyboard. The computer then goes to sleep after a minute.
Le 05/05/2024 13:41, gregjozk a écrit :
Hello,
excuse me for very delayed responce. It seems, that this problem has been solved. Accidantly I did not disabled all addons manually. When I restarted NVDA without addons in "exit dialog - NVDA+q" all was fine. Issue was already opened at problematic addon, so this ticket can be closed. Again, I'm very sorry for raisin this issue.
See: #paulber19/NVDAExtensionGlobalPlugin#15 https://github.com/paulber19/NVDAExtensionGlobalPlugin/issues/15
— Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/16337#issuecomment-2094771998, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADZLFFG4JIB3ASBMGDK4523ZAYLGNAVCNFSM6AAAAABFKF5M72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUG43TCOJZHA. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Does this happen when you explicitely choose sound split disabled in NVDA audio settings?Von meinem iPhone gesendetAm 05.05.2024 um 19:19 schrieb paulber19 @.***>: Hi.
I actually noticed this add-on malfunctioning when Wasapi is activated.
But I reproduced this malfunction with a portable version of NVDA
version alpha-31645, bf96860d and without add-ons., Wasapi activated:
- configure Windows (for my part Windows 10 22H2) to put the computer to
sleep after one minute.
-
start NVDA,
-
type "NVDA+Alt+s" once. NVDA says that NVDA and apps are on both channels.
-
no longer touch the keyboard.
The computer does not go to sleep after one minute.
Stop NVDA and no longer touch the keyboard.
The computer then goes to sleep after a minute.
Le 05/05/2024 13:41, gregjozk a écrit :
Hello,
excuse me for very delayed responce. It seems, that this problem has
been solved. Accidantly I did not disabled all addons manually. When I
restarted NVDA without addons in "exit dialog - NVDA+q" all was fine.
Issue was already opened at problematic addon, so this ticket can be
closed.
Again, I'm very sorry for raisin this issue.
See: #paulber19/NVDAExtensionGlobalPlugin#15
https://github.com/paulber19/NVDAExtensionGlobalPlugin/issues/15
—
Reply to this email directly, view it on GitHub
https://github.com/nvaccess/nvda/issues/16337#issuecomment-2094771998,
or unsubscribe
You are receiving this because you are subscribed to this
thread.Message ID: @.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Re-opening for investigation.
Given the comments and the last changes on sound split, it seems that when sound split is disabled, the issue does not occur anymore. But when sound split mode (with 100% in botch channels for all sources) is enabled, the issue is reproducible.
@seanbudd I think this needs some higher priority. If the community does not have a solution for this, the sound split feature might cost batery life in many situations because in this case NVDA will not honor the energy saving profiles set in Windows. If there is no solution found for this, I think sound split will need to be reverted unfortunately.
The user might think the laptop will go to sleep, and if this does not happen the Windows will shut down when the batery is completely unccharged. This will lead to loss of data in case people have still open documents in different applications, and will probably cause very annoying situations. It is unfortunate but I think we will have to live with the sound split as an add-on until a solution is found.
How can you guys tell when your computer goes to sleep? I set my to go to sleep in 1 minute and I was listening to the fan, but I'm getting inconclusive results. Sometimes it stops spinning after 2 or three minutes, sometimes it doesn't stop spinning at all even with pre-soundSplit revisions. Is there a tool that can like maybe beep right before computer falls asleep?
@mltony In my case, my computer does not wake upon keyboard action. Thus, not only can I usually tell from the click output quietly from the sound card when it goes to sleep if I have my external speakers turned up, but I can also tell because key presses will do nothing.
Back when I was testing these non-sleep problems, I would simply wait a bit longer than the appropriate time, and if I couldn't otherwise tell that it was sleeping, I would press an NVDA review key. If I heard nothing, it was sleeping.
By the way, I have found that, at least for me, one minute is often not reliable as a time to sleep--frequently it doesn't happen on time.
Three minutes is the minimum I am comfortable with expecting sleep results.
I am still having a hard time reproducing this. My computer doesn't seem to be entering standby mode even when NVDA is not running.
I am really not sure how to proceed here. Out of two laptops that I have neither apperas to enter standby mode in 1 minute even after specifying 1 minute in windows settings. Listening to their fan is useless - in one laptop the fan never stops spinning, on the other one it does stop after 2-4 minutes, but I haven't been able to conclusively ascertain that it entered standby.
I also tried writing a script that would beep, but it seems that playing any sound prevents Windows from entring standby .
I also repeated all these experiments on a pre-sound-split build, with add-ons disabled and even with NVDA turned off. No luck creating a reliably reproducing test case.
I also tried to disable waking my compiuter on keyboard events via powercfg command and that doesn't appear to work either.
I would guess that one of wasapi calls, probably setting a callback listener somehow interferes with standby timer in Windows. But without a reliable test case I can't really investigate this further.
How can you guys tell when your computer goes to sleep? I set my to go to sleep in 1 minute and I was listening to the fan, but I'm getting inconclusive results. Sometimes it stops spinning after 2 or three minutes, sometimes it doesn't stop spinning at all even with pre-soundSplit revisions. Is there a tool that can like maybe beep right before computer falls asleep?
@mltony It might be possible to set up a web server on the laptop and determine if it's gone to sleep by whether it can be accessed on other devices.
Inspired by @hwf1324's comment I found a reliable way - I ping my computer from the other laptop and when replies stop coming - that indicates that it went standby. However, having said this, I tested current beta branch thoroughly with different versions of sound split and different setting, and my computer enters standby mode reliably regardless of whether sound split is enabled or disabled. In my understanding OP complained about v2023.3 - so thishas nothing to do with sound split. Then OP mentioned some problematic addon. Then @CyrilleB79 mentioned this issue happens when sound split is enabled. Did you disable your add-ons when you tried this? I guess it would be great if someone else could try to reproduce this - as it won't repro on my computer.
It seems only @paulber19 is able to reproduce this with portable version of NVDA and add-ons disabled. @paulber19 do you have any other third party application on your PC that could be touched by sound split? E.g. any audio software running in the background?
@paulber19 do you have any other third party application on your PC that could be touched by sound split? E.g. any audio software running in the background No, there are no applications running in the background and simply stop NVDA and the system will automatically go to sleep one minute after stopping. I reproduced the problem quite easily:
- I configure the sound split mode other than "disabled".
- I save the configuration.
- I restart NVDA.
- I'm waiting for it to go to sleep which doesn't happen.
I start the test again, this time choosing the sound split mode "disabled". It goes into standby mode. All these tests are done with NVDA 2024.2 and all add-ons disabled.
I found another case where the standby does not happen either, this with NVDA 2023.3.4, NVDA 2024.1 and NVDA 2024.2
- install a synthesizer (like ibmtts for example)
- choose this synthesizer as your current synthesizer.
- check that WASAPI is activated.
- save the configuration.
- restart NVDA with add-ons disabled.
- as NVDA cannot load the current synthesizer, it switches to OneCore. An error is entered in the log.
- wait for standby. It doesn't happen.
Now start the test again by configuring OneCore as the current synthesizer. No error is reported and standby occurs normally.
With WASAPI disabled, even with the error, it goes to sleep.
What to think of all this? It seems that WASAPI is affected and probably using the Pycaw library with Wasapi enabled too.