Hi, 'Twas brillig, and David Henningsson at 05/04/11 13:03 did gyre and gimble: > As I discussed with Tanu Kaskinen yesterday, we should do something > about when one profile path prevents another from using the hw volume > capabilities. However, with Ubuntu a few weeks from release, I went for > the workaround approach and created a separate profile for the devices > instead to minimise regression potential. > So, until this is fixed the right way, feel free to use the attached patch. > > Bug reference: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/671560 I've pushed this for now. I hope we do get a proper fix for the underlying problem, but I'd rather this was used for the time being (party because I've had a few queries from folks over the last few days about this, and also suffer from it with some h/w I have). I also added a new vendor/product id on top of the ones you had. While the work around is good, it's obviously not the best solution to the problem, so I hope someone can find time to look at it properly at some point. Cheers Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
