GNOME Bugzilla – Bug 766465
gnome-screensaver: Please re-enable the lock-screen feature for Jessie/testing
Last modified: 2017-12-19 18:30:11 UTC
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738631 This is quite an old Debian-bug, that hardly affects me anymore, but well, I reported it first, so I am the owner of it. Nonetheless, GNOME is the default desktop in Debian-Jessie, so I think this issue really should be dealt with. The original post was: > Package: gnome-screensaver > Version: 3.6.1-1 > Severity: minor > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > > - -- System Information: > Debian Release: jessie/sid > APT prefers testing-updates > APT policy: (500, 'testing-updates'), (500, 'testing'), (50, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.12.9caec (SMP w/2 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages gnome-screensaver depends on: > ii dbus-x11 1.8.0-1 > ii gnome-icon-theme 3.10.0-1 > ii gnome-session-bin 3.8.4-3 > ii gsettings-desktop-schemas 3.8.2-2 > ii libc6 2.17-97 > ii libcairo2 1.12.16-2 > ii libdbus-1-3 1.8.0-1 > ii libdbus-glib-1-2 0.100.2-1 > ii libgdk-pixbuf2.0-0 2.28.2-1+b1 > ii libglib2.0-0 2.36.4-1 > ii libgnome-desktop-3-7 3.8.4-2 > ii libgnomekbd8 3.6.0-1 > ii libgtk-3-0 3.8.6-1 > ii libpam0g 1.1.3-10 > ii libx11-6 2:1.6.2-1 > ii libxext6 2:1.3.2-1 > ii libxklavier16 5.2.1-1 > ii libxxf86vm1 1:1.1.3-1 > > Versions of packages gnome-screensaver recommends: > ii gnome-power-manager 3.8.2-1 > ii libpam-gnome-keyring 3.8.2-2+b1 > > gnome-screensaver suggests no packages. > > - -- no debconf information
What is the bug here? The only thing that sounds actionable is the subject - "enable the lock screen feature" - but it's unclear what you want, given that locking the screen has never been disabled. (Oh, and 3.6 has not been supported upstream since 3.8 was released three years ago ...)
(In reply to Florian Müllner from comment #1) > What is the bug here? Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!