mstoeckl / swaylock-plugin Goto Github PK

Sometimes the indicator vanishes after e.g. typing in a password and failing to log in.

I used to use a full-screen sticky mpv with my GIFs until wlroots adopted the stricter no-background policy, which broke my workflow. Then you saved my life, please provide us a link to pay you a beer (or a coffee).

meson complains:

swaylock-plugin/meson.build:159:0: ERROR: File pam/swaylock-plugin does not exist.

This produces a similar bug to swaywm/sway#3631 when swaylock is not installed alongside.
I think this is because swaylock-plugin wants to use /etc/pam.d/swaylock to check the user password, which usually does not exist if the original swaylock is not installed.
Instead this fork has /etc/pam.d/swaylock-plugin. And indeed, if I do sudo ln -s /etc/pam.d/swaylock-plugin /etc/pam.d/swaylock it works again.

Note: this would require some method of avoiding infinite retries when the plugin program is broken. Perhaps rate limit the restarting, so that successive restarts must be separated by at least 100 seconds?

Instead of rendering with a background | plugin | overlay stack, merge the background and plugin surfaces into one, which takes buffers from the plugin if available, and buffers created by swaylock otherwise.

When running swaylock --command 'program', the screen locker shows a background frame (white by default) until the background plugin program provides its first frame. Instead, Swaylock-plugin should wait (up to say, 200ms) for the background program to submit a frame.

Instead of running the command once to draw all outputs, running an independent copy of the command to provide a surface for each individual output would be more flexible.