AFAIK pipewire is activated by systemd.socket, so
$ systemctl --user stop pipewire pipewire-pulse
will work. Just stop current instance and systemd user daemon will
create a new one when needed.
(using systemctl --user restart [...] should also work)
在 2022-09-21星期三的 12:26 +0100,Patrick O'Callaghan写道:
After a recent update, tracer said I should restart pipewire:
$ sudo tracer -a
You should restart:
* These applications manually:
pipewire
pipewire-pulse
Logging out and in had no effect, nor does there appear to be a
systemd
unit installed:
$ systemctl |grep pipewire
$
Although there are unit files in the RPM:
$ rpm -ql pipewire|grep service
/usr/lib/systemd/user/filter-chain.service
/usr/lib/systemd/user/pipewire.service
/usr/lib/systemd/user/filter-chain.service
/usr/lib/systemd/user/pipewire.service
The man pages for pipewire, pipewire.conf, pw-cli and pw-mon are not
helpful.
Any ideas?
poc
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue