There is a race condition which can leave the screen contents visible if a key is pressed on the keyboard very quickly after the screen saver kicks in.
XScreenSaver was configured to blank the display immediately (and power it off) instead of displaying a screen saver.
Steps to reproduce
Using XScreenSaver, configure it to blank and power off the display immediately upon invocation. Very quickly after it kicks in, press any key on the keyboard. (This may not be reproducible easily.)
Expected behavior
The contents of the display prior to the screensaver's invocation must not be visible under any circumstances unless the correct password is entered.
Actual behavior
Whatever was displayed prior to the invocation of XScreenSaver is clearly shown with the XScreenSaver password dialog superimposed over it.
Qubes OS release
4.1 (the current patch release as of 2022-10-08)
Brief summary
There is a race condition which can leave the screen contents visible if a key is pressed on the keyboard very quickly after the screen saver kicks in.
XScreenSaver was configured to blank the display immediately (and power it off) instead of displaying a screen saver.
Steps to reproduce
Using XScreenSaver, configure it to blank and power off the display immediately upon invocation. Very quickly after it kicks in, press any key on the keyboard. (This may not be reproducible easily.)
Expected behavior
The contents of the display prior to the screensaver's invocation must not be visible under any circumstances unless the correct password is entered.
Actual behavior
Whatever was displayed prior to the invocation of XScreenSaver is clearly shown with the XScreenSaver password dialog superimposed over it.