I read the document, but it didn't really explain the bug; I understand how the logic works, but I don't understand how pulseaudio makes the error. Unless, of course, the db data is suddenly wrong, or if there is a bug in pa's implementation of the logic on this hardware. It's curious, though, that this did work in the past.
It also seems that the regression has caused the "fade" and "balance" controls (accessed from gnome-volume-control) to be entirely dysfunctional. This was not the case before. Finally, why is the importance only wishlist? (And why won't-fix in lucid?) The bug fulfils the criteria for medium: moderate and confusing impact on core program; problem with non-essential hardware. -- [lucid regression] HDA: pulseaudio volume control sets alsa master to 0 when still at 15% (incorrect db data?) https://bugs.launchpad.net/bugs/533921 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
