pipewire-0.3.45 broke on kernels compiled w/ CONFIG_SND_VERBOSE_PROCFS=N due to upstream issue https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2094 However, even though upstream has since patched this, it looks like SND_VERBOSE_PROCFS should still be suggested to allow pipewire to detect if the device is busy. I suggest adding an EWARN/EINFO to the ebuild so that users might be nudged towards enabling SND_VERBOSE_PROCFS for enhanced functionality Reproducible: Always
Thanks!
Upstream has clearly stated that requiring CONFIG_SND_VERBOSE_PROCFS was not intended and that the required information should be obtainable without it. I tried looking at the commit in question but I was not able to determine, if there's any benefit from CONFIG_SND_VERBOSE_PROCFS. And, if yes, where or how it would show. For now I'd suggest trying to gather more information before telling Gentoo users to reconfigure their kernels without more direct evidence for that being upstream recommendation/suggestion.
Upstream indicates that the requirement on CONFIG_SND_VERBOSE_PROCFS was fixed in https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/97a5fe80c1d0fb0d8173a61a87051053cff7a5c2
I also had this exact issue and it took me a while to figure out a workaround. It seems that at a minimum CONFIG_SND_PROC_FS=y is required, not necessarily CONFIG_SND_VERBOSE_PROCFS=y. This was not the case in pipewire-0.3.44 and earlier, at least in my testing. I was able to reproduce this behavior on 2 different machines.
(In reply to Kenton Groombridge from comment #4) > I also had this exact issue and it took me a while to figure out a > workaround. It seems that at a minimum CONFIG_SND_PROC_FS=y is required, not > necessarily CONFIG_SND_VERBOSE_PROCFS=y. This was not the case in > pipewire-0.3.44 and earlier, at least in my testing. I was able to reproduce > this behavior on 2 different machines. Even in newer versions?
pinkflames >wtay: Gentoo has a question whether CONFIG_SND_PROC_FS=y is now a required kernel >configuration, since one user is reporting that 0.3.44 and older versions worked >without it >but that current versions need at least that option enabled wtay >no.. Well.. did I ask a bad/misunderstood question or is there something else going on?
