On Mon, Jan 28, 2019 at 09:01:24AM +0100, Olivier Berger wrote: > > Dear Maintainer, > > I tried to see what happens with light-locker when I experience screen > wakeup issues. > > I then launched light-locker with the --debug option, which seemed to > work, until I unlocked it which resulted in : > [listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (08:53:18): > obj_path=(null) interface=(null) method=(null) destination=:1.2599 > [switch_greeter_timeout] gs-manager.c:430 (08:53:27): Switch to greeter > timeout > [gs_listener_send_switch_greeter] gs-listener-dbus.c:139 (08:53:27): Send > switch greeter > [listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (08:53:28): > obj_path=/org/freedesktop/login1/session/_31013 > interface=org.freedesktop.DBus.Properties method=PropertiesChanged > destination=(null) > [listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (08:53:28): > obj_path=/org/freedesktop/login1/session/c17 > interface=org.freedesktop.DBus.Properties method=PropertiesChanged > destination=(null) > [listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (08:53:28): > obj_path=/org/freedesktop/login1/seat/seat0 > interface=org.freedesktop.DBus.Properties method=PropertiesChanged > destination=(null) > dbus[18962]: arguments to dbus_message_new_method_call() were incorrect, > assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line > 1362. > This is normally a bug in some application using the D-Bus library. > > D-Bus not built with -rdynamic so unable to print a backtrace > Abandon > > I guess this isn't the expected behaviour. >
Oh, and btw, this happened when I started light-locker --debug from the command-line, but actually, that seems to happen also when started from the command-line without --debug too... Hope this helps -- Olivier BERGER https://www-public.imtbs-tsp.eu/~berger_o/ - OpenPGP 2048R/0xF9EAE3A65819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France)
