about summary refs log tree commit diff
diff options
context:
space:
mode:
authorVincent Ambo <tazjin@tvl.su>2024-09-03T20·43+0300
committerclbot <clbot@tvl.fyi>2024-09-03T22·34+0000
commita9403664e1db1d5c6d9b1edd6649f228bcbd0c24 (patch)
tree7ca92ae94930fcc0cafefd4539ae7ecd1b54afa2
parent632e74e4357f371446678d177fe578fd3c193836 (diff)
fix(tazjin/nixos): always start pipewire before niri r/8649
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
-rw-r--r--users/tazjin/nixos/modules/desktop.nix4
1 files changed, 4 insertions, 0 deletions
diff --git a/users/tazjin/nixos/modules/desktop.nix b/users/tazjin/nixos/modules/desktop.nix
index 973e1b39db19..f3cde6326c58 100644
--- a/users/tazjin/nixos/modules/desktop.nix
+++ b/users/tazjin/nixos/modules/desktop.nix
@@ -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 = { };