On Mon, 09 Oct 2023 17:22:38 +0100
Patrick O'Callaghan wrote:
> On Mon, 2023-10-09 at 06:38 -0700, stan via users wrote:
> > systemctl --user restart pipewire pipewire-pulse wireplumber
>
> Thanks. Didn't find wireplumber, but it worked without it.
I think that wireplumber is an optional pack
On Mon, 2023-10-09 at 06:38 -0700, stan via users wrote:
> systemctl --user restart pipewire pipewire-pulse wireplumber
Thanks. Didn't find wireplumber, but it worked without it.
poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe
On Mon, 09 Oct 2023 14:12:41 +0100
Patrick O'Callaghan wrote:
> Can pipewire be properly restarted (after an update) without logging
> out and in again? I'm using Plasma, if it matters.
I use this to restart the sound systems after they are updated.
It seems to work. You have to run it as the u
Can pipewire be properly restarted (after an update) without logging
out and in again? I'm using Plasma, if it matters.
poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora
On Wed, 2022-09-21 at 22:19 +0800, yanq...@fedoraproject.org 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 -
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
> >
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'Call
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 a
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 t
