The forcedpms change was very unwise, there are more xlock usecases broken/made
annoying.
a) some window managers (like fluxbox) map a key combo to starting xlock in
the DEFAULT configuration.
The user presses the Lock_the_screen combo
If the computer is fast enough, the xlock starts and the screen is blanked
before the key in released
And the release of the key unblanks the screen.
The feature is useless here and caused an ugly backlight off-on flash
b) One use for the -mode blank is the transparent "screensaver"
Such thing can be used for example when someone want's to show something on the
screen (perhaps a video or presentation) and disable keyboard/mouse to make
sure noone messes with them
(because IR receivers aren't affected by xlock, I use it while the "TV centrum
software" mythtv is on)
Here the feature troubles/breaks a legitimate usecase
c) Failure to lock when dpms is missing/disabled is certainly not acceptable
Being unable to lock the computer after upgrade makes it useless in many
places
¯¯
sidenote: even thought it's not your fault, ubuntu seems to take the dpms
force way.... without presenting the "turn the bad feature off" option
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
