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 | a68e8e39f6c844f921176875ab79e69b4c66871a (patch) | |
| tree | 29891820fe26c2af723b86627801c9f1b9574531 /lass/1systems/red | |
| parent | 5f8532b51d6132157197dffde04a0a3d34982901 (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 'lass/1systems/red')
0 files changed, 0 insertions, 0 deletions