xflock4 needs a 'sleep 1' before 'xset dpms force off' to prevent backlight from immediately reactivating
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Xfce4 Session |
In Progress
|
Medium
|
|||
xfce4-session (Ubuntu) |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Without a 'sleep 1' before +dpms command, slock or xtrlock, etc. will cause a laptop backlight to immediately reactivate.
description: Notebook
product: 4180AP3
vendor: LENOVO
version: ThinkPad T420
*-firmware
vendor: LENOVO
physical id: d
version: 83ET82WW (1.52 )
date: 06/04/2018
size: 128KiB
capacity: 8128KiB
*-display
bus info: pci@0000:00:02.0
width: 64 bits
clock: 33MHz
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xfce4-session 4.12.1-3ubuntu4 [modified: usr/bin/xflock4]
ProcVersionSign
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 7 10:11:37 2018
InstallationDate: Installed on 2018-11-04 (2 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
SourcePackage: xfce4-session
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in xfce4-session: | |
importance: | Unknown → Medium |
status: | Unknown → In Progress |
As noted at http:// www.shallowsky. com/linux/ x-screen- blanking. html calls to "xset dpms" need to be prefixed with "sleep 1":
will blank the screen (or activate the screensaver program, if you're using
one) after a delay of one second. You need the delay because X gets a little
confused about the order of events; it will blank the screen but immediate
un-blank it, thinking the activity of your typing the command happened
recently enough to come out of screensaver mode.
sleep 1; xset dpms force off
will turn the screen OFF after a delay of one second. You can also use
standby, suspend, or on instead of off.
Downstream bug report: https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 776674