Package: acpi-support Version: 0.141-2 Followup-For: Bug #593303 I agree that it is not OK to not wait for the screensaver before suspending or hibernating. Please revert this patch.
What happens both in my case and another user on Wheezy reporting via irc today is the screensaver fails to activate until seconds after resuming. Thus, if an unattended laptop is opened by another person and resumed, the attacker has seconds in which to type some command (e.g. killall xscreensaver!) thereby rendering the screen lock ineffective. Thanks, Ben -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages acpi-support depends on: ii acpi-fakekey 0.141-2 ii acpi-support-base 0.141-2 ii acpid 1:2.0.20-1 ii lsb-base 4.1+Debian12 ii pm-utils 1.4.1-13 ii x11-xserver-utils 7.7+1 Versions of packages acpi-support recommends: ii gnome-screensaver 3.6.1-1 ii rfkill 0.5-1 ii xscreensaver 5.22-1 Versions of packages acpi-support suggests: ii radeontool 1.6.2-1.1 ii vbetool 1.1-3 ii xinput 1.6.0-1 -- Configuration Files: /etc/default/acpi-support changed: ACPI_SLEEP=true ACPI_HIBERNATE=true LOCK_SCREEN=true DISPLAY_DPMS=xset XRANDR_OUTPUT=LVDS -- 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