Package: gnome-screensaver Version: 3.6.1-7+b1 Severity: important Dear Maintainer,
After updating packages, I discovered that gnome-screensaver is now refusing to launch a second copy of itself on a different X display from an existing copy. Before, this would Just Work, but now gnome-screensaver explicitly complains "screensaver already running in this session." The particular way I have my system set up requires me to use two separate X displays (e.g. :0 and :1). Before, I was able to lock either display by running two copies of gnome-screensaver and running "gnome-screensaver-command -l" with the appropriate DISPLAY setting. Now, I am only able to ever lock one of the X displays because gnome-screensaver won't launch a second copy and gnome-screensaver-command communicates with the first copy regardless of DISPLAY. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/20 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-screensaver depends on: ii dbus-x11 1.10.12-1 ii gnome-icon-theme 3.12.0-2 ii gnome-session-bin 3.22.1-1 ii gsettings-desktop-schemas 3.22.0-1 ii libc6 2.24-5 ii libcairo2 1.14.6-1+b1 ii libdbus-1-3 1.10.12-1 ii libdbus-glib-1-2 0.108-1 ii libgdk-pixbuf2.0-0 2.36.0-1 ii libglib2.0-0 2.50.1-1 ii libgnome-desktop-3-12 3.22.1-1 ii libgnomekbd8 3.22.0.1-1 ii libgtk-3-0 3.22.2-1 ii libpam0g 1.1.8-3.3 ii libsystemd0 231-10 ii libx11-6 2:1.6.3-1 ii libxext6 2:1.3.3-1 ii libxklavier16 5.4-2 ii libxxf86vm1 1:1.1.4-1 Versions of packages gnome-screensaver recommends: ii gnome-power-manager 3.22.1-1 ii libpam-gnome-keyring 3.20.0-3 gnome-screensaver suggests no packages. -- no debconf information
