[Pkg-xfce-devel] Bug#828204: light-locker: Without chrome running, obeys xfce4-power-manager. With chrome, usually doesn't.
korz at optonline.net
Sun Jun 26 02:05:21 UTC 2016
I've run Debian testing on my systems for about 13 years now and usually dist-
upgrade daily but at least weekly.
Run up to the problem:
On 2016.06.19 I picked up light-locker as part of the changes since 2016.06.17.
/root/LOG.20160619.0:Selecting previously unselected package light-locker.
/root/LOG.20160619.0:Preparing to unpack .../light-locker_1.7.0-3_amd64.deb
/root/LOG.20160619.0:Unpacking light-locker (1.7.0-3) ...
/root/LOG.20160619.0:Setting up light-locker (1.7.0-3) ...
After I tracked down the new tab in xfce4-power-manager-settings that the
light-locker installation had added, it no longer used "light-locker-command
--lock" and locked the screen, but rather just blanked and then turned off the
backlight, which was what I wanted.
However, part of that transition to using light-locker also recommended
removing xscreensaver packages:
The following packages were automatically installed and are no longer
xfce4-volumed xscreensaver xscreensaver-data
After doing some research, this seemed sane so on 2016.06.21:
/root/LOG.autoremove.20160621.0: xfce4-volumed xscreensaver xscreensaver-
/root/LOG.autoremove.20160621.0:Removing xscreensaver (5.34-2) ...
/root/LOG.autoremove.20160621.0:Removing xscreensaver-data (5.34-2) ...
Since then, if google chrome (stable) is not running, power management on the
display works just as set.
However, if google chrome is running, for a while display blanking and turndown
works as configured, but eventually blanking doesn't work.
"light-locker-command --lock" locks as expected, but I'm not looking for
locking, just blanking in a few minutes followed by shutting down the display
"light-locker-command --activate" blanks as expected, then comes right back on
in about 2.5-3 seconds with:
$ light-locker-command --activate
** Message: The screensaver failed to activate.
If I wait for the configured blank and power-off timeouts (temporarily set at 1
and 2 minutes for testing), I expect the screen to blank at 1 minute and power
off the light at 2 minutes, like it does when chrome is not running.
I expected the system to follow what it says in the light-locker documentation
for it and lightdm, that it would shift to tty8, blank, etc and stay that way
until there was activity to wake it up.
I've poked around my session logs and the system logs, but not yet come upon
related logs, nor a way of discovering what it is about chrome that often keeps
the power management on the display from obeying my settings.
For now I can either reinstall xscreen, or remember to turn off power to the
display, neither of which seems the right solution.
Is there a log to check (and what is that), or a debug setting to enable (and
how do I do that), to let me discover what is waking up the display and keeping
it awake all night long?
$ dpkg -l light-locker lightdm google-chrome-stable
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
ii google-chrome- 51.0.2704.10 amd64 The web browser from Google
ii light-locker 1.7.0-3 amd64 simple screen locker for lightDM
ii lightdm 1.18.1-1 amd64 simple display manager
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (550, 'testing'), (99, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages light-locker depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1
ii libc6 2.22-11
ii libcairo2 1.14.6-1+b1
ii libdbus-1-3 1.10.8-1
ii libdbus-glib-1-2 0.106-1
ii libglib2.0-0 2.48.1-1
ii libgtk-3-0 3.20.6-1
ii libpango-1.0-0 1.40.1-1
ii libpangocairo-1.0-0 1.40.1-1
ii libsystemd0 230-2
ii libx11-6 2:1.6.3-1
ii libxext6 2:1.3.3-1
ii libxss1 1:1.2.2-1
ii lightdm 1.18.1-1
light-locker recommends no packages.
light-locker suggests no packages.
-- no debconf information
More information about the Pkg-xfce-devel