Package: xlockmore Version: 1:5.31-1 Followup-For: Bug #591279 First, I fully ACK the original report.
Second, I want to note that although (at least in 5.31) DPMS support seems to be compiled in (config.h: #define USE_DPMS 1), the parameters -dpmsstandby, -dpmssuspend, and -dpmsoff seem to have NO effect, neither in version 5.31 nor in 5.27 (which doesn't suffer from this immediate DPMS off bug). The command xlock -dpmsoff 5 -dpmssuspend 5 -dpmsstandby 5 seems to be in no way different from the command xlock For me, the desired behavior of xlock is: DEFAULT: don't fiddle with DPMS parameters, leave it to X11. Otherwise, use -dpms... options to override X11 values. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (501, 'testing'), (50, 'unstable'), (25, 'experimental'), (12, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages xlockmore depends on: ii libc6 2.13-27 ii libgcc1 1:4.7.0-1 ii libice6 2:1.0.7-2 ii libpam0g 1.1.3-7 ii libsm6 2:1.2.0-2 ii libstdc++6 4.7.0-1 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxmu6 2:1.1.0-3 Versions of packages xlockmore recommends: ii libpam-modules 1.1.3-7 Versions of packages xlockmore suggests: ii fortune-mod [fortune] 1:1.99.1-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
