Re: wsdisplay: disabling the screen burner while blanked leaves the display off

On Tue, Aug 04, 2026 at 02:45:50PM -0400, [email protected] wrote:
> 	Setting display.screen_off=0 while the console is currently blanked
> 	disables the burner timeout but never re-enables video, and never
> 	clears sc_burnman.  The display stays off, and subsequent keyboard
> 	activity then drives it the wrong way -- the screen darkens again on
> 	each keypress rather than waking.  Only a reboot recovers.

Are you sure that 'only a reboot recovers'?

What happens if you set display.screen_off to a non-zero value, (say 10000),
whilst the display is blanked?

(If you don't have network or serial access to the machine, this might mean
 typing the command at a blanked display.)

Unless it's a different issue to the one that I already know about, the
display will revert to normal behaviour _after the value is changed to
non-zero_.

For reference, I fixed the setting of display.screen_off to zero in 2022,
which was committed as revision 1.145 of wsdisplay.c.  Previously, it was not
possible to disable the screen burner once enabled.  The current behaviour is
the expected one, there is no implication that disabling the blanking timeout
would immediately un-blank the screen, (although it could easily be made to if
there was consensus on that).

By the way, running every potential bug report through an LLM to expand it is
not really helpful.  The paragraph I quoted from your original email is more
than enough to identify the issue.