Skip to content

Prevent Standby can leave Windows sleep prevention asserted after disable

Closure

Closed on 2026-05-24.

  • app commit 33c42bf (BUG-114: release standby prevention when idle) makes the release decision explicit: a previously-held system sleep assertion is released when the preference is disabled or the app is no longer connected or transferring.
  • test commit 9dcb7d7 covers activity gating, system-sleep-only flags, and release-only-when-previously-asserted behavior.
  • Workspace validation reran the release localization policy audit and passed for all 43 release language files.

Validation:

  • python -m emule_workspace validate
  • python -m emule_workspace build app --variant main --config Debug --platform x64 --build-output-mode ErrorsOnly
  • python -m emule_workspace build app --variant main --config Release --platform x64 --build-output-mode ErrorsOnly
  • Debug and Release native suites: standby_prevention and parity.

Summary

The Prevent Standby preference was activity-gated in code but described in the UI as a whole-application runtime behavior. More importantly, the only periodic caller was skipped when the preference was disabled, so a previously asserted Windows execution-state request could remain active instead of being released immediately.

Intended Outcome

  • Keep the low-drift activity-gated behavior: system sleep is blocked only while eMuleBB is connected or transferring.
  • Do not block display sleep.
  • Release the Windows execution-state assertion when the preference is disabled, when the app becomes idle, and during shutdown.
  • Make the label, tooltip, preference matrix, and canonical release translations describe the same behavior.