[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#922269: x11-utils: X do not triggers the screensaver



Package: x11-utils
Version: 7.7+4
Severity: normal

Hello,

I noticed that my screensaver is not triggered anymore after the
default timeout yet I can activate it through "xset s activate".

It tried the following:

nicoe@mirabelle:~% while true; do
echo `xssstate -i` `xssstate -t` `xssstate -s`
sleep 10
done

Here's the result:

7 29983 off
9941 20054 off
19959 10036 off
29978 17 off
39997 0 off
50016 0 off

What's strange is that the timeout reach zero but the state of the
screensaver stays on "off".

I am not sure the bug resides in this package to be honest but since
xset sets user preferences for X it might be related.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages x11-utils depends on:
ii  libc6           2.28-7
ii  libfontconfig1  2.13.1-2
ii  libfontenc1     1:1.1.3-1+b2
ii  libfreetype6    2.9.1-3
ii  libgl1          1.1.0-1
ii  libx11-6        2:1.6.7-1
ii  libx11-xcb1     2:1.6.7-1
ii  libxaw7         2:1.0.13-1+b2
ii  libxcb-shape0   1.13.1-2
ii  libxcb1         1.13.1-2
ii  libxcomposite1  1:0.4.4-2
ii  libxext6        2:1.3.3-1+b2
ii  libxft2         2.3.2-2
ii  libxi6          2:1.7.9-1
ii  libxinerama1    2:1.1.4-2
ii  libxmu6         2:1.1.2-2
ii  libxmuu1        2:1.1.2-2
ii  libxrandr2      2:1.5.1-1
ii  libxrender1     1:0.9.10-1
ii  libxt6          1:1.1.5-1
ii  libxtst6        2:1.2.3-1
ii  libxv1          2:1.0.11-1
ii  libxxf86dga1    2:1.1.4-1+b3
ii  libxxf86vm1     1:1.1.4-1+b2

x11-utils recommends no packages.

Versions of packages x11-utils suggests:
pn  mesa-utils  <none>

-- no debconf information


Reply to: