I would say more users use alsamixer to fix their sound, rather than screwing it up.
So it seems to me like the suggested solution will make things worse (and we will probably be overwhelmed with regression bug reports). I would say it would be better to expose users to the alsamixer layer, at least if we're talking Karmic time frame. An use case could be that one user likes to have his sound card's "3D effect" on, while another wants it to be off. This is not exposed through pulseaudio atm. How will both users be able to configure their systems right, without one of them having to use alsamixer every time he logs in? -- Move to pulse audio is not resetting volume levels at ALSA level https://bugs.launchpad.net/bugs/418620 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
