Public bug reported:

This morning's updates broke both the screen lock (it never auto-locks
now) and dpms (if you manually lock the screen, it doesn't turn off any
more).

"xset dpms force off" still works to turn the screen off and "gnome-
screensaver-command -l" still locks the screen, so it probably isn't
gnome-screensaver's fault.

Is it a lightdm issue perhaps? Which app is in charge of this?

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-screensaver 3.6.1-7ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
Uname: Linux 4.4.0-9134-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Aug 20 12:22:54 2016
GnomeSessionIdleInhibited: Unknown
GnomeSessionInhibitors: Failed to acquire
GsettingsGnomeSession:
 org.gnome.desktop.session session-name 'ubuntu'
 org.gnome.desktop.session idle-delay uint32 60
InstallationDate: Installed on 2016-07-04 (46 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: gnome-screensaver
UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago)

** Affects: gnome-screensaver (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615184

Title:
  screen lock and dpms broken in yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1615184/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to