I spoke to Daniel Chen on irc about this bug and he indicated that capturing the file '/var/lib/alsa/asound.state' before and after upgrading would be helpful. He also said the following:
15:19 < crimsun> bdmurray: I briefly spoke with someone in +1 about writing a script to parse the state file (/var/lib/alsa/asound.state) parameters on dist-upgrade (well, really between different ALSA-driver versions). This is likely the culprit you guys are seeing - particularly if it's reproducible simply on dist-upgrade (from foo to hardy) in the cli with aplay or paplay
I spoke to Daniel Chen on irc about this bug and he indicated that capturing the file '/var/lib/ alsa/asound. state' before and after upgrading would be helpful. He also said the following:
15:19 < crimsun> bdmurray: I briefly spoke with someone in +1 about writing a script to parse the state file (/var/lib/ alsa/asound. state) parameters on dist-upgrade (well, really between different ALSA-driver versions). This is likely the culprit you guys are seeing - particularly if it's reproducible simply on dist-upgrade (from foo to hardy) in the cli with aplay or paplay
and:
15:21 < crimsun> bdmurray: http:// wiki.steenbe. nl/extra/ alsachk (by osteenbergen); I don't know if that URL remains valid