I have ALSA and PulseAudio installed, but intend to use PipeWire as principle server and so
installed that as well, although I gather pipewire is automatically installed in bookworm. I
follow the guidance of https://wiki.debian.org/PipeWire but get into trouble right at the start.

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?


--

Haines Brown

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 1 Jan 2025 12:01:52 -0500
Haines Brown <haines@histomat.net> wrote:

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?

--
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, Jan 01, 2025 at 10:31:47AM -0700, Charles Curley wrote:

0.3.65 is the version on Debian 12. Why are you following the
instructions for Debian 11 if you are on Debian 12?

Oops! The wiki did not explicitly say it was for Debian 11 and I
as not sufficiently cautious. I find many directions for Debian 12.
Hopefully things will go better after I reboot

https://charlescurley.com
https://charlescurley.com/blog/

--

Haines Brown

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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.

I assumed that once rebooted I should restart the pipewife daemon with the command as
follows. Howerver it gave me errors:

$ 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

It looks like the daemon could not be started because the pipewire daemon was aleady
running and created a lock. Does a roboot start the daemon automatically? If the daemon
is alreaduy running, how does one pipewife?

--

Haines Brown

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)