[Bug] Coredump after recent update

[d8f6]

When xss-lock activates after the allotted time it produces a coredump in the systemd journal. This is an up-to-date Arch Linux installation. The program still works as expected (calls my screenlocker and I can login), but I wanted to report it here. The error in the log is as follows:

Process 1090 (xss-lock) of user 1000 dumped core.
                                              
                                              Stack trace of thread 1090:
                                              #0  0x00007e3dc061ae44 n/a (libc.so.6 + 0x94e44)
                                              #1  0x00007e3dc05c2a30 raise (libc.so.6 + 0x3ca30)
                                              #2  0x00007e3dc05aa4c3 abort (libc.so.6 + 0x244c3)
                                              #3  0x00007e3dc05aa3df n/a (libc.so.6 + 0x243df)
                                              #4  0x00007e3dc05bac67 __assert_fail (libc.so.6 + 0x34c67)
                                              #5  0x00005ea1d7365d09 n/a (xss-lock + 0x3d09)
                                              #6  0x00005ea1d7365d94 n/a (xss-lock + 0x3d94)
                                              #7  0x00005ea1d73664bf n/a (xss-lock + 0x44bf)
                                              #8  0x00007e3dc0866a89 n/a (libglib-2.0.so.0 + 0x5ca89)
                                              #9  0x00007e3dc08c89b7 n/a (libglib-2.0.so.0 + 0xbe9b7)
                                              #10 0x00007e3dc0867787 g_main_loop_run (libglib-2.0.so.0 + 0x5d787)
                                              #11 0x00005ea1d7365239 main (xss-lock + 0x3239)
                                              #12 0x00007e3dc05abc88 n/a (libc.so.6 + 0x25c88)
                                              #13 0x00007e3dc05abd4c __libc_start_main (libc.so.6 + 0x25d4c)
                                              #14 0x00005ea1d7365555 _start (xss-lock + 0x3555)
                                              
                                              Stack trace of thread 1097:
                                              #0  0x00007e3dc0699e9d syscall (libc.so.6 + 0x113e9d)
                                              #1  0x00007e3dc08c19e0 g_cond_wait (libglib-2.0.so.0 + 0xb79e0)
                                              #2  0x00007e3dc082f8dc n/a (libglib-2.0.so.0 + 0x258dc)
                                              #3  0x00007e3dc089b687 n/a (libglib-2.0.so.0 + 0x91687)
                                              #4  0x00007e3dc0896236 n/a (libglib-2.0.so.0 + 0x8c236)
                                              #5  0x00007e3dc0618ded n/a (libc.so.6 + 0x92ded)
                                              #6  0x00007e3dc069c0dc n/a (libc.so.6 + 0x1160dc)
                                              
                                              Stack trace of thread 1100:
                                              #0  0x00007e3dc068e39d __poll (libc.so.6 + 0x10839d)
                                              #1  0x00007e3dc08c88fd n/a (libglib-2.0.so.0 + 0xbe8fd)
                                              #2  0x00007e3dc0867787 g_main_loop_run (libglib-2.0.so.0 + 0x5d787)
                                              #3  0x00007e3dc0a6a4b4 n/a (libgio-2.0.so.0 + 0x1124b4)
                                              #4  0x00007e3dc0896236 n/a (libglib-2.0.so.0 + 0x8c236)

Not sure if this is due to a library update or what, but I just wanted to let you know. Also, xss-lock still works locking again even after the initial core dump (not sure if that helps). Okay, thanks.