fix(tazjin/nixos): always start pipewire before niri
According to discussions in the Niri issue tracker, pipewire must be started before niri in order for screen sharing to work. Why? No idea. Change-Id: Id4ff890dd2536b3cc98b14992cd799d257eec9be Reviewed-on: https://cl.tvl.fyi/c/depot/+/12431 Reviewed-by: tazjin <tazjin@tvl.su> Autosubmit: tazjin <tazjin@tvl.su> Tested-by: BuildkiteCI
This commit is contained in:
parent
632e74e435
commit
a9403664e1
1 changed files with 4 additions and 0 deletions
|
@ -48,6 +48,10 @@
|
|||
# Do not restart the display manager automatically
|
||||
systemd.services.display-manager.restartIfChanged = lib.mkForce false;
|
||||
|
||||
# pipewire MUST start before niri, otherwise screen sharing doesn't work
|
||||
systemd.user.services.pipewire.wantedBy = [ "niri.service" ];
|
||||
systemd.user.services.pipewire.before = [ "niri.service" ];
|
||||
|
||||
# swaylock needs an empty PAM configuration, otherwise it locks the user out
|
||||
security.pam.services.swaylock = { };
|
||||
|
||||
|
|
Loading…
Reference in a new issue