Comment 20 for bug 106380

nullack, no, it's not possible to query the hardware to set the mixer element yet. Either we mute it by default and risk a (smaller) proportion of users experiencing one regression, or we leave it unmuted by default and risk a(n increasingly larger) proportion of users experiencing the opposite regression. There's no magic bullet, and not even the udev work being done in upstream git can help [yet].

Given the number of users experiencing this issue, we should mute the control in the initscript and just accept the fallout.