On Sat, 2018-03-10 at 10:20 +0100, Stuart Pook wrote:
> On 10/03/18 10:10, Yves-Alexis Perez wrote:
> > In any case, I really can't reproduce here, and you still didn't indicate
> > what
> > you changed to make it crash reliably, so I'm afraid I can't help.
> 
> light-locker crashes at unlock every time I run it from the command line.

And did it work before or is it the first time you tried?
> 
> What happens when you run light-locker from the command line?

It works just fine:

light-locker --lock-after-screensaver=3600 --debug
[gs_debug_init] gs-debug.c:106 (15:24:33):       Debugging enabled
[main] light-locker.c:142 (15:24:33):    initializing light-locker 1.8.0
[main] light-locker.c:164 (15:24:33):    Platform:
gtk:        3
systemd:    yes
ConsoleKit: yes
UPower:     yes
[main] light-locker.c:196 (15:24:33):    Features:
lock-after-screensaver: yes
late-locking:           yes
lock-on-suspend:        yes
lock-on-lid:            yes
settings backend:       GSETTINGS
[main] light-locker.c:198 (15:24:33):    lock after screensaver 3600
[main] light-locker.c:199 (15:24:33):    late locking 0
[main] light-locker.c:200 (15:24:33):    lock on suspend 1
[main] light-locker.c:201 (15:24:33):    lock on lid 0
[main] light-locker.c:202 (15:24:33):    idle hint 1
[init_session_id] gs-listener-dbus.c:2193 (15:24:33):    Got session-id: 
/org/freedesktop/login1/session/_32
[init_session_id] gs-listener-dbus.c:2198 (15:24:33):    Got sd-session-id: 2
[init_seat_path] gs-listener-dbus.c:2279 (15:24:33):     Got seat: 
/org/freedesktop/DisplayManager/Seat0
[gs_listener_delay_suspend] gs-listener-dbus.c:449 (15:24:33):   Delay suspend
[gs_listener_x11_acquire] gs-listener-x11.c:172 (15:24:33):      ScreenSaver 
Registered
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (15:24:33):       
 obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus 
method=NameAcquired destination=:1.75
> 
> I agree that it should not normally be run from the command line.  I wanted
> to run lightlocker with different options and the running it from the
> command line was faster than logging on and off.

You can also edit the configuration (using dconf-editor for example) and I
think it should refresh it dynamically.

Regards,
-- 
Yves-Alexis

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to