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

On Tue, Aug 04, 2026 at 07:56:48PM -0000, Crystal wrote in 
<[email protected]>:
>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'?

No, I was wrong about that, sorry.

>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_.

You are absolutely right about that. With the display blanked, setting
display.screen_off=0 leaves it off and keypresses don't wake it; setting it back
to non-zero brings it straight back.

Please disregard the report and my apologies for taking up your time on this.

>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.

Point taken. I was aiming to be thorough and should have stuck to what I
actually observed.

Regards,

Remco