Package: xscreensaver
Version: 5.45+dfsg1-1
Severity: important
X-Debbugs-Cc: da...@cornell.edu

Dear Maintainer,

As of a few months ago (after a dist-upgrade + reboot), sometimes when I come
back to my desktop computer after leaving it alone for several hours, the
screen is unlocked with xscreensaver no longer running (i.e. locking the screen
no longer works until I run xscreensaver or xscreensaver-demo to restart it). I
haven't noticed any pattern of when it happens other than the screensaver
having been running for several hours, presumably undisturbed. Needless to say,
the screen being unlocked without a password is a security issue, although
admittedly a minor one for my setup.

If I leave xscreensaver running in a console inside screen, I can see output
like the following after a crash (no messages about it appear in dmesg):

$ xscreensaver
xscreensaver-systemd: 09:55:11: failed to connect as
org.freedesktop.ScreenSaver: File exists
xscreensaver:   signal: 0: child pid 3281394 (xscreensaver-systemd) exited
abnormally (code 1).
xscreensaver: 09:55:22: ClientMessage ignored while authentication dialog is
active
xscreensaver: 09:55:30: no keyboard or mouse data in /proc/interrupts?
xscreensaver: 12:05:53: ClientMessage ignored while authentication dialog is
active
xscreensaver: 15:36:23: ClientMessage ignored while authentication dialog is
active
xscreensaver: 19:11:55: ClientMessage ignored while authentication dialog is
active
XIO:  fatal IO error 0 (Success) on X server ":0.0"
      after 1702519 requests (1702495 known processed) with 0 events remaining.
$ X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  130 (MIT-SHM)
  Minor opcode of failed request:  3 (X_ShmPutImage)
  Resource id in failed request:  0xe41bff8
  Serial number of failed request:  23
  Current serial number in output stream:  24
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  130 (MIT-SHM)
  Minor opcode of failed request:  3 (X_ShmPutImage)
  Resource id in failed request:  0xe41bffc
  Serial number of failed request:  23
  Current serial number in output stream:  24
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  130 (MIT-SHM)
  Minor opcode of failed request:  3 (X_ShmPutImage)
  Resource id in failed request:  0xe41bffa
  Serial number of failed request:  23
  Current serial number in output stream:  24


Apologies: the issue is sporadic, so I did not notice it immediately and
therefore did not take note of exactly what the version numbers were
before/after the issue started.

Not sure it's related, but I'm using https://github.com/alexanderk23/gluqlo as
my screensaver program and am using xscreensaver-command -watch to run some
scripts on lock/unlock, based on the Perl script in the man page for
xscreensaver-command in the -watch section.

Let me know if there's any way I can collect more debugging information that
may be useful.


(Not sure what might be related; here's the versions of a few other packages
that aren't listed explicitly as dependencies. I think all of them have been
updated at least once since the problem started.)
ii  linux-image-amd64                                           5.10.28-1
amd64        Linux for 64-bit PCs (meta-package)
ii  nvidia-kernel-dkms                                          460.73.01-1
amd64        NVIDIA binary kernel module DKMS source
ii  xorg                                                        1:7.7+22
amd64        X.Org X Window System

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

Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xscreensaver depends on:
ii  init-system-helpers  1.60
ii  libatk1.0-0          2.36.0-2
ii  libc6                2.30-4
ii  libcrypt1            1:4.4.18-4
ii  libglib2.0-0         2.66.8-1
ii  libgtk2.0-0          2.24.33-1
ii  libpam0g             1.4.0-7
ii  libpango-1.0-0       1.46.2-3
ii  libsystemd0          247.3-5
ii  libx11-6             2:1.7.0-2
ii  libxext6             2:1.3.3-1.1
ii  libxi6               2:1.7.10-1
ii  libxinerama1         2:1.1.4-2
ii  libxml2              2.9.10+dfsg-6.3+b1
ii  libxmu6              2:1.1.2-2+b3
ii  libxrandr2           2:1.5.1-1
ii  libxt6               1:1.2.0-1
ii  libxxf86vm1          1:1.1.4-1+b2
ii  xscreensaver-data    5.45+dfsg1-1

Versions of packages xscreensaver recommends:
ii  libjpeg-turbo-progs   1:2.0.6-4
ii  perl                  5.32.1-3
ii  wamerican [wordlist]  2019.10.06-1
ii  xfonts-100dpi         1:1.0.4+nmu1.1

Versions of packages xscreensaver suggests:
ii  chromium [www-browser]              90.0.4430.85-1
ii  elinks [www-browser]                0.13.2-1+b1
ii  firefox [www-browser]               88.0-1
ii  firefox-esr [www-browser]           52.9.0esr-1
ii  fortune-mod [fortune]               1:1.99.1-7.1
ii  gdm3                                3.38.2.1-1
ii  google-chrome-stable [www-browser]  90.0.4430.93-1
ii  lynx [www-browser]                  2.9.0dev.6-2
ii  opera-stable [www-browser]          60.0.3255.170
pn  qcam | streamer                     <none>
ii  xdaliclock                          2.44+debian-2
pn  xfishtank                           <none>
pn  xscreensaver-data-extra             <none>
ii  xscreensaver-gl                     5.45+dfsg1-1
pn  xscreensaver-gl-extra               <none>

Reply via email to