On Wed, Sep 21, 2022, at 4:26 AM, Patrick O'Callaghan wrote: > 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? Found this in earlier post... [host@non-root-user]$ systemctl restart pipewire-pulse.service --user _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
