What I would like to remind to the community is that this bugreport was initially referring to the treatment PA gives to ALSA-using software. As of now, the problem still persists on a vanilla installation of Hardy, and can be reproduced using steps in the beginning of this report. The workaround for this bug is also in the same report, it works, yet it's not installed by default, thus rendering Ubuntu backwards-incompatible with a huge amount of software. The question is, what do we do for our users not to have to google up this bugreport to make their systems usable? Should we add this issue to release-notes, perhaps? Should we provide users with a convenient way to fix things from the very beginning?
Alexander's point is the same of PA developers I've contacted on this matter, and it's understandable. The problem is that the de-facto standard in Linux is ALSA, and many professionals-targeted software (JACK, Audacity, etc.) is not likely to have PA support in any visible future (I have contacted the developers as well). My personal concern is about unexperienced end-users: if we cannot make things automatically work for them (I really don't see why it should be not possible, but then nor am I a developer), how can we provide them quickly accessible and easy to find information of working solutions (be it uninstalling PA, or whatever)? -- Default ALSA device must use PulseAudio, otherwise ALSA applications may fail https://bugs.launchpad.net/bugs/198453 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
