Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2019-01-02 at 15:59 +0100, Yves-Alexis Perez wrote:
> So I have a /somehow/ good news for you: the bug has started appearing on my
> box, out of the blue. It's not really good for me because it confirms the bug
> can manifest from nowhere, but at least that mean I might be able to
> investigate it.

Out of curiosity, do you mount /proc with hidepid=1 or hidepid=2? If so, can
you try removing the option (or set hidepid=0) for testing?

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlws9ZQACgkQ3rYcyPpX
RFvRUQgAwKtyfeGa27ergFGFqKz8AHoW43txrRfX07/t/f+OQ678ux1mog783RrC
3qHEL2LEcRM5PpZw0fON4wd9pMypgDiIl7uwjaDhoehZ9zE0trgNOeXTocryHq2d
ho4oXKm89zL55Dv/zsVkZB4SBIHYb9OSmIN3XrdHqWTjNdT3c8XXxokhOAN1YQU4
QT7Me0T3TKG1kSXGCePqzj8PJCgPeFLa+IppTvZg8N7Pyf9NuGd2Z9wWW98GDsbi
Ll5rLmeGG7qvC3j6g+X7uoENe+2lP8zCq95CqwVAJMqA+sFDEBAMFO7MTmCJCekL
fgDsERMTojGWWwxEaLBEweIYd6yacA==
=lNdr
-END PGP SIGNATURE-

Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, 2018-03-10 at 18:30 +0100, Stuart Pook wrote:
> On 10/03/18 15:26, Yves-Alexis Perez wrote:
> > On Sat, 2018-03-10 at 10:20 +0100, Stuart Pook wrote:
> > > 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?
> 
> This the first time that I tried.
> 
> > You can also edit the configuration (using dconf-editor for example) and I
> > think it should refresh it dynamically.
> 
> ok (perhaps it could print that just before it crashes ;-) )
> 
> I'll get a full stack trace next time.

So I have a /somehow/ good news for you: the bug has started appearing on my
box, out of the blue. It's not really good for me because it confirms the bug
can manifest from nowhere, but at least that mean I might be able to
investigate it.

Stay tuned.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlws0cIACgkQ3rYcyPpX
RFuylwgAhOqwOF7pO4QIj9V+KXTwIhyZidGasc1XqtaMv9RgWmCTiOLcb0h511n9
MGBDhphMVeKSGE2BqDXjzF638mUAqp/hC5/9tmepU8mALDIuP/x/TntJpqprcMCx
KO/EKtxwgbWhOVbyten+wZhUQM5vlTRnyDGjuNK5/bypOqCeddw8KtlwYCBW0atC
5YpMSQFeclUKBgGox5z7zS1QDKB/8lLUay20NKanClIPK0MaUE8s3IvwlDSGqDbh
inxu/lnkh8UfWJeG9e5nI67Wn3WsgJcysp6Im5+yqUBO1k80dagCQS5JVc4C/O3B
6oOMdu4a9HQVe5S+DPgti/mqCuS8Xw==
=ffs6
-END PGP SIGNATURE-

Bug#892290: [Pkg-xfce-devel] Bug#892290: Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

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.
> 
> What happens when you run light-locker from the command line?
> 
> 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.

Just a quick update on this. For you it always crash at unlock when running
from the command line. Does it also crash when running normally as part of the
session?

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAltpgyIACgkQ3rYcyPpX
RFvEYwgAsUOjdAW2bI+95oDW+tIXUcBYCokYwvzj3Ttrisqen5ldUfu6L8ISoHtU
JcktG8FmtWv4w+iieHbBVvMl+MLstb7/L2um09S/GntxvNW81byiy28mGP77v/jh
8sEM36RfQLyIEWUj9U4POIB5KD2odePi247pbUZhJGKdA0yNs0g94Yqh46v84U7V
ci54xfTpXO285b86VXxP5IdBLg/z6tsuRua5bpcnoepHqlXyPoT0R/icwgA9hgfL
IJCUsT1TrpN08G8eVgiT9BydMDWi6LsZOCgJ+LMkJdRK9VWiAvmDImSua3nSjHoK
gxBVFgL3keg1zyZastgul266GSol0Q==
=6rUx
-END PGP SIGNATURE-

Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Stuart Pook]

On 10/03/18 15:26, Yves-Alexis Perez wrote:

On Sat, 2018-03-10 at 10:20 +0100, Stuart Pook wrote:

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?


This the first time that I tried.


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


ok (perhaps it could print that just before it crashes ;-) )

I'll get a full stack trace next time.

:; gdb $(type -p light-locker)
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/light-locker...Reading symbols from 
/usr/lib/debug/.build-id/e0/45019311f6cb6efe20e0fcd299a4f1d8ed64b0.debug...done.
done.
(gdb) define f
Type commands for definition of "f".
End with a line saying just "end".

run  --debug
where
kill
end

(gdb) f
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffedcf0700 (LWP 11063)]
[New Thread 0x7fffed4ef700 (LWP 11064)]
[New Thread 0x7fffecab8700 (LWP 11065)]
[gs_debug_init] gs-debug.c:106 (10:18:51):   Debugging enabled
[main] light-locker.c:142 (10:18:51):initializing light-locker 1.8.0
[main] light-locker.c:164 (10:18:51):Platform:
gtk:3
systemd:yes
ConsoleKit: yes
UPower: yes
[main] light-locker.c:196 (10:18:51):Features:
lock-after-screensaver: yes
late-locking:   yes
lock-on-suspend:yes
lock-on-lid:yes
settings backend:   GSETTINGS
[main] light-locker.c:198 (10:18:51):lock after screensaver 3600
[main] light-locker.c:199 (10:18:51):late locking 0
[main] light-locker.c:200 (10:18:51):lock on suspend 1
[main] light-locker.c:201 (10:18:51):lock on lid 0
[main] light-locker.c:202 (10:18:51):idle hint 0
[query_session_id] gs-listener-dbus.c:2101 (10:18:51):   
org.freedesktop.login1.NoSessionForPID raised:
 PID 11059 does not belong to any known session


[init_session_id] gs-listener-dbus.c:2193 (10:18:51):Got session-id: (null)
[query_sd_session_id] gs-listener-dbus.c:2177 (10:18:51):Couldn't 
determine our own sd session id: No data available
[init_session_id] gs-listener-dbus.c:2198 (10:18:51):Got sd-session-id: 
(null)
[init_seat_path] gs-listener-dbus.c:2279 (10:18:51): Got seat: 
/org/freedesktop/DisplayManager/Seat0
[gs_listener_delay_suspend] gs-listener-dbus.c:449 (10:18:51):   Delay suspend
[gs_listener_x11_acquire] gs-listener-x11.c:172 (10:18:51):  ScreenSaver 
Registered
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (10:18:51):   
 obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus 
method=NameAcquired destination=:1.1875
[xroot_filter] gs-listener-x11.c:131 (12:16:55): ScreenSaver started
[listener_x11_blanking_changed_cb] gs-monitor.c:454 (12:16:55):  Blanking 
changed: 1
[gs_manager_timed_lock] gs-manager.c:488 (12:16:55): Start lock timer
[gs_listener_send_signal_active_changed] gs-listener-dbus.c:310 (12:16:55): 
 Sending the ActiveChanged(TRUE) signal on the session bus
[xroot_filter] gs-listener-x11.c:124 (12:50:07): ScreenSaver stopped
[listener_x11_blanking_changed_cb] gs-monitor.c:454 (12:50:07):  Blanking 
changed: 0
[gs_manager_stop_lock] gs-manager.c:499 (12:50:07):  Stop lock timer
[gs_listener_send_signal_active_changed] gs-listener-dbus.c:310 (12:50:07): 
 Sending the ActiveChanged(FALSE) signal on the session bus
[xroot_filter] gs-listener-x11.c:131 (13:04:56): ScreenSaver started
[listener_x11_blanking_changed_cb] gs-monitor.c:454 (13:04:56):  Blanking 
changed: 1
[gs_manager_timed_lock] gs-manager.c:488 (13:04:56): Start lock timer
[gs_listener_send_signal_active_changed] gs-listener-dbus.c:310 (13:04:56): 
 Sending the ActiveChanged(TRUE) signal on the session bus
[xroot_filter] gs-listener-x11.c:124 (13:05:07): ScreenSaver stopped
[listener_x11_blanking_changed_cb] gs-monitor.c:454 (13:05:07):  Blanking 
changed: 0
[gs_manager_stop_lock] gs-manager.c:499 (13:05:07):  Stop lock timer
[gs_listener_send_signal_active_changed] gs-listener-dbus.c:310 (13:05:07): 
 Sending the ActiveChanged(FALSE) signal on the session bus
[xroot_filter] gs-listener-x11.c:131 (13:47:20): 

Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Yves-Alexis Perez]

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

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

Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Stuart Pook]

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.

What happens when you run light-locker from the command line?

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.

I tried running light-locker in gdb but that hung my session and I had to login 
on another console and kill gdb to recover.

I think that light-locker should either run correctly from the command line or 
announce that it cannot be used that way.

thanks, Stuart

:; light-locker --debug
[gs_debug_init] gs-debug.c:106 (00:05:14):   Debugging enabled
[main] light-locker.c:142 (00:05:14):initializing light-locker 1.8.0
[main] light-locker.c:164 (00:05:14):Platform:
gtk:3
systemd:yes
ConsoleKit: yes
UPower: yes
[main] light-locker.c:196 (00:05:14):Features:
lock-after-screensaver: yes
late-locking:   yes
lock-on-suspend:yes
lock-on-lid:yes
settings backend:   GSETTINGS
[main] light-locker.c:198 (00:05:14):lock after screensaver 3600
[main] light-locker.c:199 (00:05:14):late locking 0
[main] light-locker.c:200 (00:05:14):lock on suspend 1
[main] light-locker.c:201 (00:05:14):lock on lid 0
[main] light-locker.c:202 (00:05:14):idle hint 0
[query_session_id] gs-listener-dbus.c:2101 (00:05:14):   
org.freedesktop.login1.NoSessionForPID raised:
 PID 32104 does not belong to any known session


[init_session_id] gs-listener-dbus.c:2193 (00:05:14):Got session-id: (null)
[query_sd_session_id] gs-listener-dbus.c:2177 (00:05:14):Couldn't 
determine our own sd session id: No data available
[init_session_id] gs-listener-dbus.c:2198 (00:05:14):Got sd-session-id: 
(null)
[init_seat_path] gs-listener-dbus.c:2279 (00:05:14): Got seat: 
/org/freedesktop/DisplayManager/Seat0
[gs_listener_delay_suspend] gs-listener-dbus.c:449 (00:05:14):   Delay suspend
[gs_listener_x11_acquire] gs-listener-x11.c:172 (00:05:14):  ScreenSaver 
Registered
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (00:05:14):   
 obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus 
method=NameAcquired destination=:1.1851
[listener_dbus_handle_session_message] gs-listener-dbus.c:1010 (00:14:00):  
 Received Lock request
[gs_grab_grab_root] gs-grab-x11.c:647 (00:14:00):Grabbing the root 
window
[gs_grab_get_keyboard] gs-grab-x11.c:153 (00:14:00): Grabbing keyboard 
widget=DF
[gs_grab_get_mouse] gs-grab-x11.c:213 (00:14:00):Grabbing mouse 
widget=DF
[gs_manager_create_windows_for_screen] gs-manager.c:548 (00:14:00):  
Creating 1 windows for screen 0
[gs_manager_create_window_for_monitor] gs-manager.c:324 (00:14:00):  
Creating window for monitor 0 [0,0] (1920x1200)
[update_geometry] gs-window-x11.c:197 (00:14:00):got geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:210 (00:14:00):using geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:197 (00:14:00):got geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:210 (00:14:00):using geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[gs_window_move_resize_window] gs-window-x11.c:243 (00:14:00):   Move and/or 
resize window on monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:197 (00:14:00):got geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:210 (00:14:00):using geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[gs_window_move_resize_window] gs-window-x11.c:243 (00:14:00):   Move and/or 
resize window on monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:197 (00:14:00):got geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:210 (00:14:00):using geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[gs_window_move_resize_window] gs-window-x11.c:243 (00:14:00):   Move and/or 
resize window on monitor 0: x=0 y=0 w=1920 h=1200
[gs_manager_timed_switch] gs-manager.c:445 (00:14:00):   Start switch to 
greeter timer
[gs_window_xevent] gs-window-x11.c:369 (00:14:00):   not raising our windows
[window_map_event_cb] gs-manager.c:233 (00:14:00):   Handling window 
map_event event
[gs_listener_resume_suspend] gs-listener-dbus.c:513 (00:14:00):  Resume 
suspend: fd=14
[manager_maybe_grab_window] gs-manager.c:204 (00:14:00): Moving grab to 
0x5587c72364d0
[gs_grab_move_keyboard] gs-grab-x11.c:450 (00:14:00):Moving keyboard grab 
from DF to 32C
[gs_grab_move_keyboard] gs-grab-x11.c:457 (00:14:00):*** doing X server grab
[gs_grab_release_keyboard] gs-grab-x11.c:279 (00:14:00): 

Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Yves-Alexis Perez]

On Fri, 2018-03-09 at 22:36 +0100, Stuart Pook wrote:
> > > Light-locker crashes when I unlock my session. This means that my
> > > session
> > > is not locked the next time it should be,
> 
> hi  Yves-Alexis
> 
> > there was no recent update to light-locker. What did change on your
> > system?
> > Unlock works fine here so I'll need more information in order to
> > reproduce.
> 
> I guess I don't normally run it from the command line.

I don't think it's supposed to be run that way anyway (see the message about
the session, for example). I think it'd be best to let it run from desktop
startup, then attach with gdb.

It might be worth looking at the backtrace.

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.

Regards,
-- 
Yves-Alexis

Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Stuart Pook]

On 09/03/18 14:50, Yves-Alexis Perez wrote:

control: tag -1 unreproducible moreinfo
On Wed, 2018-03-07 at 22:37 +0100, Stuart Pook wrote:

Dear Maintainer,

Light-locker crashes when I unlock my session. This means that my session
is not locked the next time it should be,


hi  Yves-Alexis


there was no recent update to light-locker. What did change on your system?
Unlock works fine here so I'll need more information in order to reproduce.


I guess I don't normally run it from the command line.

:; gdb $(type -p light-locker)
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/light-locker...Reading symbols from 
/usr/lib/debug/.build-id/e0/45019311f6cb6efe20e0fcd299a4f1d8ed64b0.debug...done.
done.
(gdb) run --debug
Starting program: /usr/bin/light-locker --debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffedcf0700 (LWP 27177)]
[New Thread 0x7fffed4ef700 (LWP 27178)]
[New Thread 0x7fffecab8700 (LWP 27179)]
[gs_debug_init] gs-debug.c:106 (22:27:46):   Debugging enabled
[main] light-locker.c:142 (22:27:46):initializing light-locker 1.8.0
[main] light-locker.c:164 (22:27:46):Platform:
gtk:3
systemd:yes
ConsoleKit: yes
UPower: yes
[main] light-locker.c:196 (22:27:46):Features:
lock-after-screensaver: yes
late-locking:   yes
lock-on-suspend:yes
lock-on-lid:yes
settings backend:   GSETTINGS
[main] light-locker.c:198 (22:27:46):lock after screensaver 3600
[main] light-locker.c:199 (22:27:46):late locking 0
[main] light-locker.c:200 (22:27:46):lock on suspend 1
[main] light-locker.c:201 (22:27:46):lock on lid 0
[main] light-locker.c:202 (22:27:46):idle hint 0
[query_session_id] gs-listener-dbus.c:2101 (22:27:46):   
org.freedesktop.login1.NoSessionForPID raised:
 PID 27173 does not belong to any known session


[init_session_id] gs-listener-dbus.c:2193 (22:27:46):Got session-id: (null)
[query_sd_session_id] gs-listener-dbus.c:2177 (22:27:46):Couldn't 
determine our own sd session id: No data available
[init_session_id] gs-listener-dbus.c:2198 (22:27:46):Got sd-session-id: 
(null)
[init_seat_path] gs-listener-dbus.c:2279 (22:27:46): Got seat: 
/org/freedesktop/DisplayManager/Seat0
[gs_listener_delay_suspend] gs-listener-dbus.c:449 (22:27:46):   Delay suspend
[gs_listener_x11_acquire] gs-listener-x11.c:172 (22:27:46):  ScreenSaver 
Registered
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (22:27:46):   
 obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus 
method=NameAcquired destination=:1.1767
[listener_dbus_handle_session_message] gs-listener-dbus.c:1010 (22:29:00):  
 Received Lock request
[gs_grab_grab_root] gs-grab-x11.c:647 (22:29:00):Grabbing the root 
window
[gs_grab_get_keyboard] gs-grab-x11.c:153 (22:29:00): Grabbing keyboard 
widget=DF
[gs_grab_get_mouse] gs-grab-x11.c:213 (22:29:00):Grabbing mouse 
widget=DF
[gs_manager_create_windows_for_screen] gs-manager.c:548 (22:29:00):  
Creating 1 windows for screen 0
[gs_manager_create_window_for_monitor] gs-manager.c:324 (22:29:00):  
Creating window for monitor 0 [0,0] (1920x1200)
[update_geometry] gs-window-x11.c:197 (22:29:00):got geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:210 (22:29:00):using geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:197 (22:29:00):got geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:210 (22:29:00):using geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[gs_window_move_resize_window] gs-window-x11.c:243 (22:29:00):   Move and/or 
resize window on monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:197 (22:29:00):got geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:210 (22:29:00):using geometry for 
monitor 0: x=0 y=0 w=1920 h=1200
[gs_window_move_resize_window] gs-window-x11.c:243 (22:29:00):   Move and/or 
resize window on monitor 0: x=0 y=0 w=1920 h=1200
[update_geometry] gs-window-x11.c:197 (22:29:00):got geometry for 
monitor 0: x=0 y=0 w=1920 h=1200

Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Yves-Alexis Perez]

control: tag -1 unreproducible moreinfo
On Wed, 2018-03-07 at 22:37 +0100, Stuart Pook wrote:
> Dear Maintainer,
> 
> Light-locker crashes when I unlock my session. This means that my session
> is not locked the next time it should be,

Hi,

there was no recent update to light-locker. What did change on your system?
Unlock works fine here so I'll need more information in order to reproduce.
> 
> When I run light-locker at the command line I see:
> 
> % light-locker --lock-after-screensaver=3600
> dbus[26450]: 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
> Aborted

Can you try running with --debug too?

Regards,
-- 
Yves-Alexis

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

Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Stuart Pook]

Package: light-locker
Version: 1.8.0-1
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

Light-locker crashes when I unlock my session. This means that my session
is not locked the next time it should be,

When I run light-locker at the command line I see:

% light-locker --lock-after-screensaver=3600
dbus[26450]: 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
Aborted

I've installed light-locker-dbgsym but the didn't improve the error
message.

I have various XDG environment variables set.

% env | grep XDG
XDG_CONFIG_HOME=/home/stuart/.config
XDG_MENU_PREFIX=lxde-
XDG_VTNR=7
XDG_SESSION_ID=2
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/stuart
XDG_SESSION_TYPE=x11
XDG_DATA_DIRS=/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/local/share/:/usr/share/:/usr/share/gdm/:/var/lib/menu-xdg/
XDG_SESSION_DESKTOP=LXDE
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_CURRENT_DESKTOP=LXDE
XDG_SEAT=seat0
XDG_RUNTIME_DIR=/run/user/1000
XDG_DATA_HOME=/home/stuart/.local/share
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_CONFIG_DIRS=/etc/xdg



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-3
ii  libc62.27-1
ii  libcairo21.15.10-2
ii  libdbus-1-3  1.12.6-2
ii  libdbus-glib-1-2 0.110-2
ii  libglib2.0-0 2.54.3-2
ii  libgtk-3-0   3.22.28-1
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libsystemd0  237-4
ii  libx11-6 2:1.6.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxss1  1:1.2.2-1+b2
ii  lightdm  1.18.3-4

light-locker recommends no packages.

light-locker suggests no packages.

-- Configuration Files:
/etc/xdg/autostart/light-locker.desktop changed:
[Desktop Entry]
Type=Application
Name=Screen Locker
Name[ca]=Bloquejador de pantalla
Name[cs]=Uzamykač obrazovky
Name[da]=Skærmlås
Name[de]=Bildschirmsperre
Name[en_GB]=Screen Locker
Name[es]=Bloqueador de pantalla
Name[fa]=قفل صفحه
Name[fi]=Näytön lukitusohjelma
Name[fr]=Verrouilleur d'écran
Name[gl]=Bloqueado da pantalla
Name[gu]=સ્ક્રીન લૉકર
Name[hi]=परदा अबरोधक
Name[hu]=Képernyőzár
Name[it]=Blocca schermo
Name[ja]=スクリーンのロック
Name[kk]=Экран блоктаушысы
Name[lt]=Ekrano užrakinimas
Name[nb]=Skjermlås
Name[nl]=Schermvergrendeling
Name[or]=ପରଦା ଅବରୋଧକ
Name[pl]=Blokada ekranu
Name[pt]=Bloqueio de Ecrã
Name[pt_BR]=Bloqueio de Tela
Name[ru]=Блокировщик экрана
Name[sk]=Uzamykač obrazovky
Name[tr]=Ekran Kilitleyici
Name[zh_CN]=屏幕锁
Name[zh_TW]=螢幕鎖定
Comment=Launch screen locker program
Comment[ca]=Obre el programa de bloqueig de la pantalla
Comment[cs]=Spustit Uzamykač obrazovky
Comment[da]=Start program for skærmlås
Comment[de]=Bildschirmsperre starten
Comment[en_GB]=Launch screen locker program
Comment[es]=Abrir el programa de bloqueo de pantalla
Comment[fi]=Käynnistä näytön lukitusohjelma
Comment[fr]=Lancer le verrouilleur d'écran
Comment[gl]=Iniciar o programa de bloqueo da pantalla
Comment[gu]=સ્ક્રીન લૉકર પ્રક્રિયાને શરુ કરો
Comment[hi]=परदा अबरोधक प्रोग्राम आरम्भ करें
Comment[hu]=Képernyőzár program indítása
Comment[it]=Lancia il programma blocca schermo
Comment[ja]=スクリーンロックのプログラムを実行する
Comment[kk]=Экранды блоктау бағдарламасын жөнелту
Comment[lt]=Paleisti ekrano užrakinimo programą
Comment[nb]=Kjør skjermlåsningsprogram
Comment[nl]=Schermvergrendelingsprogramma starten
Comment[or]=ପରଦା ଅବରୋଧକ ଆରମ୍ଭ କରନ୍ତୁ
Comment[pl]=Uruchamia program blokady ekranu
Comment[pt]=Lançar o programa de bloqueio do ecrã
Comment[pt_BR]=Iniciar o programa de bloqueio de tela
Comment[ru]=Запустить программу блокировки экрана
Comment[sk]=Spúšťa program na uzamknutie obrazovky
Comment[tr]=Ekran kilitleyici programını başlat
Comment[zh_CN]=启动屏幕锁程序
Comment[zh_TW]=啟動螢幕鎖定程式
Icon=preferences-desktop-screensaver
Exec=light-locker --lock-after-screensaver=3600
NoDisplay=true
NotShowIn=GNOME;Unity;


-- no debconf information