config_local_arch/home/xyz/.config/myconf/syue, branch masterDevice dependent config files for Arch Linux, managed by https://git.flylightning.xyz/fsh/tree/sh/cfg (git bare repo method)https://git.flylightning.xyz/config_local_arch/atom?h=master2025-10-11T14:00:00ZI guess upstream name change2025-10-11T14:00:00ZXiao Panxyz@flylightning.xyz2025-10-11T14:00:00Zurn:sha1:0518c86acb6f8872774cda076cc1712a43231b35Globally disable pipewire.socket user unit2025-06-03T06:01:33ZXiao Panxyz@flylightning.xyz2025-06-03T06:01:33Zurn:sha1:7097f102339611908b25c639913651e1529538b6
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
now I remove pipewire-pulse2024-09-14T23:14:49ZXiao Panxyz@flylightning.xyz2024-09-14T23:14:49Zurn:sha1:02039009815b2b050ebad453179e8e93b1f871a0install pipewire-pulse for firefox mic capture2024-08-18T07:20:09ZXiao Panxyz@flylightning.xyz2024-08-18T07:20:09Zurn:sha1:8ce4ffff53f24c59ecea78379ba882507ba83d2dadd sye and syue2023-03-17T09:40:12ZXiao Pangky44px1999@gmail.com2023-03-17T09:40:12Zurn:sha1:5357184a164ca033e2c6cb65fd8d541cef6d6c7b