light-locker doesn't work in 16.04 with GNOME

[Jacob Maher]

What happens:

When attempting to start the application from the terminal all I get is a warning then it immediately exits.
I have attempted a reboot but it seems the process does not start with the system nor my user session.

I have removed all screensaver packages and this has not helped the issue.

Output of light-locker --debug:

[gs_debug_init] gs-debug.c:106 (02:50:42): Debugging enabled
[main] light-locker.c:142 (02:50:42): initializing light-locker 1.7.0
[main] light-locker.c:144 (02:50:42): lock after screensaver 5
[main] light-locker.c:145 (02:50:42): late locking 0
[main] light-locker.c:146 (02:50:42): lock on suspend 1
[main] light-locker.c:147 (02:50:42): lock on lid 0
[main] light-locker.c:148 (02:50:42): idle hint 0
[init_session_id] gs-listener-dbus.c:2180 (02:50:42): Got session-id: /org/freedesktop/login1/session/c2
[init_session_id] gs-listener-dbus.c:2185 (02:50:42): Got sd-session-id: c2
[init_seat_path] gs-listener-dbus.c:2262 (02:50:42): Got seat: /org/freedesktop/DisplayManager/Seat0
[gs_listener_delay_suspend] gs-listener-dbus.c:449 (02:50:42): Delay suspend

** (light-locker:7588): WARNING **: screensaver already running in this session

package versions:

light-locker = 1.7.0-2ubuntu1
lightdm = 1.18.2-0ubuntu1

My system:

Ubuntu 16.04.1
DE: GNOME 3.18.5

What I expected:

The screen should lock, much the same way as running dm-tool lock from the terminal

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: light-locker 1.7.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jul 24 02:42:18 2016
InstallationDate: Installed on 2016-06-28 (25 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
SourcePackage: light-locker
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.