I used media-video/pipewire-0.3.22 quite successfully with pipewire-pulse (with occasional bluetooth hiccups) as per https://bugs.gentoo.org/744622. Now just updating to 0.3.24 leaves pavucontrol and any other media user without media device. I'm on HDA Intel PCH. Stopping pipewire-pulse and starting pulseaudio, all devices are available again. Reproducible: Always
Additional info: comparing the output of pa-info with pipewire-pulse 0.3.22 and 0.3.24 I get (excerpt): 18c18 < Client Index: 51 --- > Client Index: 33 22c22 < Server Name: PulseAudio (on PipeWire 0.3.22) --- > Server Name: PulseAudio (on PipeWire 0.3.24) 26,28c26,28 < Default Sink: alsa_output.pci-0000_00_1f.3.analog-stereo < Default Source: alsa_input.pci-0000_00_1f.3.analog-stereo < Cookie: 65ab:d791 --- > Default Sink: @DEFAULT_SINK@ > Default Source: @DEFAULT_SOURCE@ > Cookie: 73ac:67e2 35c35 < #rt.prio = 20 --- > #rt.prio = 88 So the default source/sink names are placeholders. Don't know yet at which stage they are supposed to be filled in - during compilation?
Please check if you have /usr/bin/pipewire-media-session installed and running - for systemd it now requires: systemctl --user enable pipewire-media-session.service pipewire and pipewire-pulse should remain as sockets, though. For OpenRC it can be started by uncommenting the appropriate line near the end of /etc/pipewire/pipewire.conf but I suspect that in that case you should have observed this earlier, too, so I'm hoping you're a systemd user. ;) I hope this helps.
I'm sorry, I was doing some other things before replying and missed your update. I'll install the tree version and check what's going on with that but you have probably correctly identified what broke your audio.
Sorry once more (this time for triple posting) - it turns out that @FOO@ are used not just by Meson but also PipeWire and in this case they should get replaced at runtime by pipewire-media-session, so my initial recommendation stands. Sorry for the rapid fire confusion.
(In reply to Niklāvs Koļesņikovs from comment #4) > Sorry once more (this time for triple posting) - it turns out that @FOO@ are > used not just by Meson but also PipeWire and in this case they should get > replaced at runtime by pipewire-media-session, so my initial recommendation > stands. Sorry for the rapid fire confusion. Thanks, correct - previously pipewire-media-session was started automatically, but not any longer. https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#pipewire-not-loading also hints that enabling this is essential. I guess for the time being, those who upgrade must also change their config accordingly. I'm marking this issue as resolved.
Thank you for confirming this fixed it. Hopefully the ebuild will get updated soon'ish.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b08c84f511f0c75e07bba317ca281a5d9d63ab12 commit b08c84f511f0c75e07bba317ca281a5d9d63ab12 Author: Niklāvs Koļesņikovs <80783143+pinkflames@users.noreply.github.com> AuthorDate: 2021-03-16 22:01:02 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2021-04-12 21:55:34 +0000 media-video/pipewire: Bump to 0.3.25 & ebuild overhaul This overhaul improves the instructions shown after merging and now provides a sys-auth/realtime-base inspired limits.d file for better user experience. The user ID (UID) range used was chosen to match what SDDM accepts as a valid non-system UID range. This has known shortcomings with very large values in enterprise deployments but this was deemed the least bad of all the imperfect options. Updates SRC_URI to use the official repository hosted by The freedesktop project instead of the GitHub mirror. Patches Meson files to correctly handle docdir per FHS/Gentoo policy. Replaces the old jack IUSE with jack-client for allowing PW to act as a JACK 2 client, while the emulation code is now always enabled, since it has no dependencies nor adverse effects on anything. When systemd USE flag is not set, now automatically enables starting of pipewire-pulse and pipewire-media-session binaries, since most people installing PipeWire will want to do that anyway. Adds instructions to inform users of the change and directs them to Gentoo Wiki with details specific to their setups. Always disables FFmpeg and Vulkan, and removes the respective IUSE, and comments out their *DEPEND, because Vulkan feature is only useful to developers, and FFmpeg code has had no major developments since May 2020 - upstream disables both by default. Removes dead code that no longer was doing anything and correctly adds RDEPEND on supported Bluetooth audio codecs with the associated IUSE flags. As well as adds RDEPEND on sys-libs/ncurses[unicode] that was previously missing and ensures that disabled libsndfile IUSE does not silently disable building of the pw-cat tool, leading to surprising mismatch between upstream documentation and actually installed binaries. Also turns the warning about failed mlock(), that upstream now disables, back on - to known for sure that 256k is really enough for everyone. Closes: https://bugs.gentoo.org/777288 Closes: https://bugs.gentoo.org/777837 Closes: https://bugs.gentoo.org/779058 Signed-off-by: Niklāvs Koļesņikovs <89q1r14hd@relay.firefox.com> Closes: https://github.com/gentoo/gentoo/pull/19965 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> media-video/pipewire/Manifest | 1 + ...pewire-0.3.25-enable-failed-mlock-warning.patch | 12 ++ .../files/pipewire-0.3.25-fix-docdir-path.patch | 32 +++ .../pipewire-0.3.25-non-systemd-integration.patch | 18 ++ media-video/pipewire/metadata.xml | 13 +- media-video/pipewire/pipewire-0.3.25.ebuild | 236 +++++++++++++++++++++ 6 files changed, 310 insertions(+), 2 deletions(-)
