Simon Ser

>still racy running an external command after swayidle -f How so?

I'm not sure we want to introduce more complexity in swayidle. Also, there's no good way for swayidle to detect if a lockscreen is running. I'd add another timeout that...

>I thought about creating a dedicated session daemon that handles systemd and sway events for suspend, lid switch, screen lock, DPMS, logind idle flag and inhibiting those. That would be...

@kittydoor This has been added in https://github.com/swaywm/sway/pull/4805

I don't think there's a PAM API to know what the remaining time is.

> so the following diff may be sufficient to fix the issue. Indeed! After discussing with pq in #wayland, it seems like it's a good practice to not use `wl_surface.set_buffer_scale`...

Thanks for the review!

This is unlikely, as the compositor won't allow multiple input inhibitors to be active at the same time.

>Is it possible that the next lock screen is queued up and immediately appears when I unlock the previous? No, it would get disconnected. >What does swaylock do if it...

Weird. SIGBUS typically means a write outside of an mmap'ed region bounds.