Re: getting started with pipewire
On Thu, Jan 09, 2025 at 07:39:29 -0500, Haines Brown wrote:
> I have pipewire-pulse intstalled, not puleaudio.
Maybe change that?
hobbit:~$ dpkg -l | grep pulse
ii libpulse-mainloop-glib0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries (glib support)
ii libpulse0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries
ii libpulse0:i386 16.1+dfsg1-2+b1 i386 PulseAudio client libraries
ii libpulsedsp:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio OSS pre-load library
ii pipewire-pulse 0.3.65-3+deb12u1 amd64 PipeWire PulseAudio daemon
ii pulseaudio 16.1+dfsg1-2+b1 amd64 PulseAudio sound server
ii pulseaudio-utils 16.1+dfsg1-2+b1 amd64 Command line tools for the PulseAudio sound server
> $ wireplumber
> Failed to connect to PipeWire
I'm afraid I'm not familiar with these commands. But I get this:
hobbit:~$ wireplumber
C 08:56:02.434125 GLib (null):(null):(null): Failed to set scheduler settings: Operation not permitted
^CM 08:56:09.483224 wireplumber ../src/main.c:372:signal_handler: stopped by signal: Interrupt
M 08:56:09.484381 wireplumber ../src/main.c:364:on_disconnected: disconnected from pipewire
It "hung" after the first line of output, and then I pressed Ctrl-C
several seconds later to kill it. Audio still worked afterward so I
don't think I broke anything.
> $ wpctl status
> Could not connect to PipeWire
hobbit:~$ wpctl status
^C
It just "hung" with no output.
After I pressed Ctrl-C, my audio stopped working. I'm never going
to do this one again!
> # systemctl --user restart wireplumber.service
> Failed to connect to bus: No medium found
That shouldn't have been done as root. I think.
I'm not doing that one.
Now I get to try to figure out how to fix my audio. :( :( :(
Reply to: