Restarting pipewire

[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

[Doug Herr]

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

[Patrick O'Callaghan]

On Wed, 2022-09-21 at 07:01 -0700, Doug Herr wrote:
> 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

That restarted pipewire-pulse, but not the existing pipewire processes,
which continue as before.

poc

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 -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Patrick O'Callaghan]

On Wed, 2022-09-21 at 22:19 +0800, [e-mail] wrote:
> 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)

That last one did it, thanks.

poc