Mic92/stockholm
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

tv slock service: conflicts picom service

Browse Source 
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.
This commit is contained in:
tv 2021-01-15 23:30:37 +01:00
parent 5f8532b51d
commit a68e8e39f6
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
tv/3modules/slock.nix
View File

@ -28,6 +28,9 @@ in {
}); });
''; '';
systemd.services."slock-${cfg.user.name}@" = { systemd.services."slock-${cfg.user.name}@" = {
conflicts = [
"picom@%i.target"
];
environment = { environment = {
DISPLAY = ":%I"; DISPLAY = ":%I";
LD_PRELOAD = pkgs.runCommandCC "slock-${cfg.user.name}.so" { LD_PRELOAD = pkgs.runCommandCC "slock-${cfg.user.name}.so" {
@ -61,6 +64,8 @@ in {
restartIfChanged = false; restartIfChanged = false;
serviceConfig = { serviceConfig = {
ExecStart = "${pkgs.slock}/bin/slock"; ExecStart = "${pkgs.slock}/bin/slock";
ExecStopPost =
"+${pkgs.systemd}/bin/systemctl start xsession@%i.target";
OOMScoreAdjust = -1000; OOMScoreAdjust = -1000;
Restart = "on-failure"; Restart = "on-failure";
RestartSec = "100ms"; RestartSec = "100ms";