You can clone with
The screen isn't locked when resuming from suspend (by selecting suspend from the session menu or closing the laptop lid). I'm guessing Light Locker lacks the scripts to lock the session on suspend and hibernate?
The screen is only locked when suspending the laptop by using "dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend" but then I can't unlock it: after entering the password in the lock screen, the lock message is displayed and then nothing happens.
Tested under both Unity and Xfce.
Ubuntu: 13.10 Saucy Salamander
Light-Locker: 0.1.0+1+1~saucy1 (installed via release PPA)
Let me know if you need any other info.
so far I haven't tested light-locker in Saucy, so I'm not (yet) sure what's happening there.
Thanks for testing this – we'll investigate (might take a bit though as I'm travelling atm).
Anyway, if you still have a Raring box around to test it would be nice to know whether it works for you there.
One last question: was this a Virtualbox test or a real-install?
The test was on real hardware. Suspend doesn't work in VirtualBox, that's why I didn't test it in Raring too...
Oh, and I only have Saucy and Quantal (I should upgrade sometime but it's a pretty messed up installation) installed on real hardware.
We really wanna fix this issue before 1.0, so a bit more information might be needed in order to reproduce your problem.
What greeter are you using? (Our tests have mostly been performed with lightdm-gtk-greeter)
Could you start the greeter from a terminal – ideally with debug output enabled – and see whether there are any hints as to why unlocking doesn't work? (You can also check the logs in /var/log/lightdm/*)
And last but not least what power-manager are you using?
We've mostly tested xfce4-power-manager so far, so not sure how gnome-power-manager works (maybe it relies on systemd?) or whatever Unity uses by default.
My test was performed under both Unity and Xfce (I'm not sure if there are some interferences if both are installed in the same time), in Ubuntu 13.10.
So for the greeter, I'm using unity-greeter and the power manager is the one used under each session: for Unity it's gnome-power-manager and xfce4-power-manager for Xfce of course.
How do I run the greeter from a terminal? Running "unity-greeter" in a terminal displays this:
[+0.00s] DEBUG: unity-greeter.vala:442: Starting unity-greeter 13.10.1 UID=1000 LANG=en_US.UTF-8
[+0.00s] DEBUG: unity-greeter.vala:445: Setting cursor
[+0.00s] DEBUG: unity-greeter.vala:459: Loading command line options
[+0.00s] DEBUG: unity-greeter.vala:487: Setting GTK+ settings
[+0.02s] DEBUG: unity-greeter.vala:510: Creating Unity Greeter
[+0.02s] DEBUG: unity-greeter.vala:55: Creating background surface
[+0.02s] WARNING: No LIGHTDM_TO_SERVER_FD environment variable
And that's it...
It is not possible to run the greeter for a terminal. But the output is logged to /var/log/lightdm/*.log
Also you can run light-locker with --debug. That will give verbose output on the signals it receives for suspend/resume and locking.
light-locker support UPower and systemd signals. Do you know what is used when closing the lid?
I ran "light-locker --debug", then closed the laptop lid and here are the debug logs (lightdm.log, x-0-greeter.log, x-1-greeter.log and the "light-locker --debug" output): https://dl.dropboxusercontent.com/u/1113424/debug.tar.gz
Ubuntu uses Saucy Salamander systemd logind instead of ConsoleKit. By default systemd support is auto-detected by light-locker. Since the libsystemd-login-dev package isn't installed, this will fail:
sudo apt-get install libsystemd-login-dev
./configure --with-systemd will complain about this.