It says to start of by doing:
# touch /etc/pipewire/media-session.d/with-pulseaudio
The problem is that I have no /etc/pipewire/ although it is installed:
$ pipewire --version
pipewire
Compiled with libpipewire 0.3.65
Linked with libpipewire 0.3.65
but rather I have /usr/share/pipewire but it contains no
media-session.d/.
Do I need to re-install? Find newer directions?
0.3.65 is the version on Debian 12. Why are you following the
instructions for Debian 11 if you are on Debian 12?
https://charlescurley.com
https://charlescurley.com/blog/
Thanks to your heldp, with the help of the correct guide it seems I was able to install
pipewire successflly. To apply it I had to reboot.
$ pipewire
[E][00304.248813] mod.protocol-native | [module-protocol-:
731 lock_socket()] server 0x55cd2eef45e0: unable to
lock lockfile '/run/user/1000/pipewire-0.lock':
Resource temporarily unavailable (maybe another daemon is
running)
[E][00304.248890] pw.conf | [ conf.c: 594
load_module()] 0x55cd2eedc160: could not load mandatory module
"libpipewire-module-protocol-native": Resource temporarily
unavailable
[E][00304.248930] default | [ pipewire.c: 125 main()]
failed to create context: Resource temporarily unavailable
On 08/01/2025 00:08, Haines Brown wrote:
I have no idea how to use pipewire. Do you simply run the comand $ pipewire to
get an interface like alsamixer?
Why are you trying to start pipewire manually? Systemd should do it for you as a part of user session. It is not an application with GUI.
On 08/01/2025 00:08, Haines Brown wrote:
I have no idea how to use pipewire. Do you simply run the comand $ pipewire to
get an interface like alsamixer?
Why are you trying to start pipewire manually? Systemd should do it for you as a part of user session. It is not an application with GUI.
You should have some mixer applet in your desktop environment. Another
option is pavucontrol.
Check
systemctl --user --failed
and other systemctl commands to inspect status of pipewire units.
In my case pipewire just works. There was some issue immediately after I replaced pulseaudo, but it disappeared before I figured out what happened.
I have pipewire-pulse intstalled, not puleaudio.
$ wireplumber
Failed to connect to PipeWire
$ wpctl status
Could not connect to PipeWire
# systemctl --user restart wireplumber.service
Failed to connect to bus: No medium found
$ 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. :( :( :(
On Thu, Jan 09, 2025 at 09:00:24 -0500, Greg Wooledge wrote:
$ wpctl status
Could not connect to PipeWire
hobbit:~$ wpctl status
I tried everything I could immediately think of, including logging out
and back in, but none of it worked until I ended up rebooting like a goddamned Windows user.
Moral of the story: NEVER EVER run "wpctl". Fucking thing doesn't even
have a man page.
But at least I have audio again now.
Sent: Thursday, January 09, 2025 at 9:15 AM
From: "Greg Wooledge" <greg@wooledge.org>
To: debian-user@lists.debian.org
Subject: Re: getting started with pipewire
On Thu, Jan 09, 2025 at 09:00:24 -0500, Greg Wooledge wrote:
$ 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. :( :( :(
I tried everything I could immediately think of, including logging out
and back in, but none of it worked until I ended up rebooting like a goddamned Windows user.
Moral of the story: NEVER EVER run "wpctl". Fucking thing doesn't even
have a man page.
But at least I have audio again now.
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
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 154:11:02 |
| Calls: | 10,383 |
| Files: | 14,054 |
| Messages: | 6,417,843 |