sceenblank ignores $SCREEN_LOCK in /etc/default/acpi-support

Bug #3904 reported by Zach
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

The screenblank script in /usr/share/acpi-support/ doesn't check the value of the $LOCK_SCREEN variable as set in /usr/default/acpi-support. Even if LOCK_SCREEN is false or not set, the screen gets locked anyway.

Here is a patch to screeblank that checks the value of the $LOCK_SCREEn variable, and if 'true' then uses the -lock option to xscreensaver-command.

screenblank.patch:
--- screenblank 2005-11-04 17:09:36.000000000 -0500
+++ screenblank.new 2005-11-04 17:10:05.000000000 -0500
@@ -1,4 +1,7 @@
-su $user -c "(xscreensaver-command -throttle; xscreensaver-command -lock)"
+if [ x$LOCK_SCREEN = xtrue ]; then
+ LOCK='-lock'
+fi
+su $user -c "(xscreensaver-command -throttle; xscreensaver-command $LOCK)"
 xset dpms force off
 if [ x$RADEON_LIGHT = xtrue ]; then
     [ -x /usr/sbin/radeontool ] && radeontool light off

Revision history for this message
Paul Sladen (sladen) wrote :

Hello Zach, thanks for your report.

I just went to follow this up and found it's already been applied!

Changed in acpi-support:
status: Unconfirmed → Fix Released
a59ff5 (a59ff5a59ff5)
Changed in acpi-support (Ubuntu):
assignee: nobody → Slavik (slavikstar)
information type: Public → Public Security
Colin Watson (cjwatson)
Changed in acpi-support (Ubuntu):
assignee: a59ff5 (a59ff5a59ff5) → nobody
information type: Public Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.