Simon Ser

>moving the wl_event_loop_add_signal calls after the do_daemonize call fixes that issue Hmm, why does the daemonization remove the signal listener?

Can you try running with ASan? The stack trace doesn't make it immediately obvious what's going on.

``` meson build/ -Db_sanitize=address,undefined ```

> For the reference: #196 (comment) and two subsequent comments. This doesn't give any useful info on the crash, sadly.

>Is this behavior intentional? Right now the order is undefined. What would be the "right behaviour"? - Execute commands in the order specified on the CLI? - Sort by timeout...

Maybe it can be as simple as reversing a list insertion order (`wl_list_insert` inserts at head-of-list, need to add `.prev` to insert at end-of-list). Explicitly sorting by timeout value will...

Please reproduce with a manually compiled swaylock and post the new stack trace.

Can you try running with ASan? This smells like memory corruption.

Patches welcome.

>How would you feel about a similar option in sway itself, by the way? Sway users could just put `exec ready` in their config file.