diff options
| author | tv <tv@krebsco.de> | 2021-01-15 23:30:37 +0100 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2021-01-15 23:30:37 +0100 |
| commit | 455ad96eca5d7c30b6115aeb81cc1c9b6f1321c8 (patch) | |
| tree | 6bf9b971dfec7fc48f177f39c840bf8d2879f4ca /lib/types.nix | |
| parent | fd077450adba6a1efdb20ca230bf2cec0b8013f2 (diff) | |
tv slock service: conflicts picom service
When picom is running, slock will show the screenshot of the locked
screen after DPMS changes state to `on'.
https://bbs.archlinux.org/viewtopic.php?id=256547 seems related, but the
suggested fix (adding `no-fading-openclose = true;` to picom's config)
didn't help.
With this commit, the picom service gets "suspended" while the slock
service is running.
Diffstat (limited to 'lib/types.nix')
0 files changed, 0 insertions, 0 deletions