Hi, On Sat, Dec 8, 2018, 10:53 Elimar Riesebieter <riese...@lxtec.de wrote:
> * Felipe Sateler <fsate...@debian.org> [2018-12-06 12:13 -0300]: > > > Control: affects -1 libasound2-plugins > > > > Including the Alsa maintainers in the loop, as this may be really a > > bug on their side. > > > > On Thu, Dec 6, 2018 at 3:51 AM Zhong Jianxin <azu...@gmail.com> wrote: > > > > > > Package: pulseaudio > > > Version: 12.2-2 > > > Severity: important > > > > > > Due to alsa-plugins upstream change here[1], after libasound2-plugins > > > 1.1.7, files in /usr/share/alsa/alsa.conf.d no longer load by default > > > > This looks borked. Why did they remove this? There is no rationale in > > the commit message. > > > > Alsa maintainers, would you consider this a bug in alsa plugins? I > > would think so, but unfortunately > > the bug tracker link in the upstream site is dead. Where would I report > that? > > Since libasound2-plugins 1.1.7-2 the files from alsa-plugins source > in /usr/share/alsa/alsa.conf.d/ are linked to /etc/alsa/conf.d. > pulse.conf should be linked by pulsausdio which installs that file. > > Did I misunderstood something? > Yes, sorry for not including the full context. The proximate problem is that pulseaudio also ships files in /usr/share/alsa/alsa.conf.d, and was thus broken by the change in alsa. However, I question whether that was a good idea at all: users don't usually need to modify these files, and making me ship the files in /etc is a bad idea, because then they would be left after remove.