From a9403664e1db1d5c6d9b1edd6649f228bcbd0c24 Mon Sep 17 00:00:00 2001 From: Vincent Ambo Date: Tue, 3 Sep 2024 23:43:28 +0300 Subject: 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 Autosubmit: tazjin Tested-by: BuildkiteCI --- users/tazjin/nixos/modules/desktop.nix | 4 ++++ 1 file changed, 4 insertions(+) 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 = { }; -- cgit 1.4.1