summaryrefslogtreecommitdiff
path: root/home/xyz/.local/bin/alarm
diff options
context:
space:
mode:
authorXiao Pan <xyz@flylightning.xyz>2025-06-02 23:01:33 -0700
committerXiao Pan <xyz@flylightning.xyz>2025-06-02 23:01:33 -0700
commit7097f102339611908b25c639913651e1529538b6 (patch)
treee775ed822b20cc95e57ad21f80130322a23bb7e6 /home/xyz/.local/bin/alarm
parent0fb285b14d3659bc580ef4c1361b3f6de5887490 (diff)
Globally disable pipewire.socket user unitHEADmaster
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
Diffstat (limited to 'home/xyz/.local/bin/alarm')
0 files changed, 0 insertions, 0 deletions