Bug#660201: gnome-screensaver: inconsistent behaviour between invocations

[Greg D'Arcy]

Package: gnome-screensaver
Version: 3.2.0-2+b1
Severity: important

Dear Maintainer,

On my dual-screen system, invoking gnome-screensaver sometimes (with no obvious
pattern) fails to blank the primary display, instead freezing the display that
was present immediately prior to invocation. The secondary display is correctly
blanked. This presents a clear security issue in my opinion.

Additionally, when unlocking, the unlock dialog is frequently left behind the
desktop background on the primary display, but given focus. This means that
although it's still possible to unlock the screen, it's not obvious to the user
that this is the case.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-screensaver depends on:
ii  dbus-x11                   1.4.16-1
ii  dpkg                       1.16.1.2
ii  gnome-icon-theme           3.2.1.2-1
ii  gnome-session-bin          3.2.1-1
ii  gsettings-desktop-schemas  3.2.0-2
ii  libc6                      2.13-26
ii  libcairo2                  1.10.2-6.2
ii  libdbus-1-3                1.4.16-1
ii  libdbus-glib-1-2           0.98-1
ii  libgdk-pixbuf2.0-0         2.24.1-1
ii  libglib2.0-0               2.30.2-6
ii  libgnome-desktop-3-2       3.2.1-3
ii  libgnomekbd7               3.2.0-1
ii  libgtk-3-0                 3.2.3-1
ii  libpam0g                   1.1.3-7
ii  libx11-6                   2:1.4.4-4
ii  libxext6                   2:1.3.0-3
ii  libxklavier16              5.1-3
ii  libxxf86vm1                1:1.1.1-2

Versions of packages gnome-screensaver recommends:
ii  gnome-power-manager   3.2.1-2
ii  libpam-gnome-keyring  3.2.2-2

gnome-screensaver suggests no packages.

-- no debconf information