Bug#829642: pulseaudio 9 breaks SPDIF/iec958 and Intel HDMI audio on ASUS B85-Pro motherboard

[Mike Hommey]

On Tue, Jul 05, 2016 at 09:49:42AM -0400, Felipe Sateler wrote:
> On 5 July 2016 at 02:57, Mike Hommey <mh at glandium.org> wrote:
> > On Tue, Jul 05, 2016 at 11:21:32AM +1200, Adam Warner wrote:
> >> Package: pulseaudio
> >> Version: 9.0-1
> >> Severity: serious
> >> Justification: keep out of testing. Workaround is to downgrade to the
> >> version in testing
> >>
> >>
> >> Installation is x86-64 stock sid/unstable as of an hour ago
> >> (with libwebrtc-audio-processing-0 held after downgrade to
> >> pulseaudio 8.0-2+b2)
> >>
> >> Before pulseaudio upgrade:
> >>
> >> $ pacmd list-sinks | grep name:
> >>       name: <alsa_output.pci-0000_00_1b.0.iec958-stereo>
> >>       name: <alsa_output.pci-0000_00_03.0.hdmi-stereo>
> >
> > I have a similar issue, but it fixed itself after I downgraded and
> > upgraded again.
> >
> > With pa 9.0:
> > $ pacmd list-sinks | grep name:
> >         name: <alsa_output.pci-0000_00_1b.0.analog-stereo>
> 
> Was this after a reboot?

Yes.

> >
> > With pa 8.0:
> > $ pacmd list-sinks | grep name:
> >         name: <alsa_output.pci-0000_00_03.0.hdmi-stereo>
> >         name: <alsa_output.pci-0000_00_1b.0.analog-stereo>
> >
> > More than that, the pacmd list-sinks output didn't have any "ports" in
> > the output with pa 9.0, which prevented me from switching to headset
> > instead of speakers.
> >
> > Now, the interesting thing is that I downgraded to 8.0, killed the
> > pulseaudio daemon(s), tested that it worked as before the upgrade,
> > then went back to 9.0, killed the pulseaudio daemon again, and it still
> > worked. This would suggest some sort of race condition at boot time.
> 
> Could it be that the upgrade process did not include
> module-pulseaudio-udev the first time?

Do you mean module-udev-detect? I /think/ that's not it, because I do
have a default.pa.dpkg-old that I /think/ comes from that pulseaudio 9.0
install, after I added "load-module module-switch-on-connect" because I
thought it was my problem, and that config contains module-udev-detect.

I can't be sure 100%, though.

Mike