From 7097f102339611908b25c639913651e1529538b6 Mon Sep 17 00:00:00 2001 From: Xiao Pan Date: Mon, 2 Jun 2025 23:01:33 -0700 Subject: Globally disable pipewire.socket user unit I don't want to use pipewire. I don't want pipewire.service to start. Even though I disabled pipewire.service, pipewire.service will still be somehow started by pipewire.socket after first time I ran `mpva` after boot. So I decided to disable it globally with `sudo systemctl disable --global pipewire.socket`. Note, `systemctl --user disable pipewire.socket` does not work because it is globally enabled in post_install function in .install script in PKGBUILD package see [0]. Thanks to [1] I know the correct way is to use --global to remove global user unit, which removes /etc/systemd/user/sockets.target.wants/pipewire.socket symlink. [0] https://gitlab.archlinux.org/archlinux/packaging/packages/pipewire/-/blob/main/pipewire.install?ref_type=heads#L1-4. [1] https://github.com/systemd/systemd/issues/18271 --- home/xyz/.config/myconf/syue | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'home/xyz/.config') diff --git a/home/xyz/.config/myconf/syue b/home/xyz/.config/myconf/syue index c0f64fc1..41742797 100644 --- a/home/xyz/.config/myconf/syue +++ b/home/xyz/.config/myconf/syue @@ -2,6 +2,5 @@ UNIT FILE STATE PRESET ssh-agent.service enabled enabled xdg-user-dirs-update.service enabled enabled p11-kit-server.socket enabled enabled -pipewire.socket enabled enabled -4 unit files listed. +3 unit files listed. -- cgit v1.2.3-70-g09d2