Hello,
Le sam. 28 janv. 2023 à 12:00, Wouter Verhelst a écrit :
>
>
> I did not install pipewire manually; it was installed through dependencies.
>
It would be great to understand how pipewire pkgs have been pulled on your
system since I don't know which packages are installed by awesome. But
On Sat, Jan 28, 2023 at 12:19:17PM +0200, Wouter Verhelst wrote:
> If my analysis above is correct, I would suggest you tighten
> dependencies so that you can't install pipewire-pulse without a working
> pipewire audio setup.
... and for what it's worth, installing "pipewire-audio" on top of what
Hi Dylan,
On Fri, Jan 27, 2023 at 12:14:40PM +0100, Dylan Aïssi wrote:
> Hello Wouter,
>
> Le ven. 27 janv. 2023 à 11:00, Wouter Verhelst a écrit :
> >
> > The pipewire upstream troubleshooting guide suggests I look at
> > journalctl output as a first step in troubleshooting things. That
> >
Hello Wouter,
Le ven. 27 janv. 2023 à 11:00, Wouter Verhelst a écrit :
>
> The pipewire upstream troubleshooting guide suggests I look at
> journalctl output as a first step in troubleshooting things. That
> reveals:
>
> wouter@pc220518:~$ journalctl -xe | grep pipewire
> jan 27 11:04:01
Package: pipewire
Version: 0.3.64-4
Severity: important
Dear Maintainer,
The pipewire upstream troubleshooting guide suggests I look at
journalctl output as a first step in troubleshooting things. That
reveals:
wouter@pc220518:~$ journalctl -xe | grep pipewire
jan 27 11:04:01 pc220518
5 matches
Mail list logo
