David C. Rankin wrote:
Now it takes more resources than Xorg -- even though there is no firefox started or running.
It openSUSE bundled pipewire with the pipewire.service from upstream -- there would be no problem, I could simply stop and disable the serive, but openSUSE omits that file and pipewire is simply spinning away.
Looking at my newly installed 15.2 system, the pipewire package comes with both pipewire.service and pipewire.socket: toshiba1:~ # l /usr/lib/systemd/user/pipewire.* -rw-r--r-- 1 root root 819 Aug 7 00:41 /usr/lib/systemd/user/pipewire.service -rw-r--r-- 1 root root 130 Jun 10 11:53 /usr/lib/systemd/user/pipewire.socket ISTR a posting saying pipewire is a user service, which fits with those two files. So, let's see: per@toshiba1:~> systemctl --user status pipewire.socket ● pipewire.socket - Multimedia System Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor preset: disabled) Active: active (listening) since Mon 2020-10-05 21:15:35 CEST; 2 days ago Listen: /run/user/1000/pipewire-0 (Stream) Yup, all present and accounted for. To stop that socket, something like this might do the trick: systemctl --user disable --now pipewire.socket -- Per Jessen, Zürich (12.4°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org