Firstly, the startup manager is not where you disable PulseAudio. If you feel that is unclear, you should file a bug against gnome-session.
Secondly, disabling PA does *not* break the system. The user interface side effects are not pretty, true, but they are by no means unworkable: you can just as easily use gnome-alsamixer, alsamixer, amixer, gamix, kmix, or another mixer to control mixer settings. You've even alluded to reading about the workaround, which is to disable pulse support at compile-time in the mixer apps. Note that Intrepid/8.10 and Jaunty/9.04 both shipped with such a parameter enabled for testing purposes so that regressions could be ironed out. Thirdly, disabling autospawn is documented both in my post to ubuntu- devel-discuss and in /etc/default/pulseaudio. In effect, what you've stated is that none of the exposed knobs seem to disable pulse, unlike their descriptions. And, because of their not acting as intended, it is incredibly difficult to turn off pulse. This is precisely what the new bug title describes. So, instead of playing games with titles, I propose that you (or someone else who has more time than I do at the moment -- I am not employed by Canonical to work on Ubuntu) do the following: 1) Evaluate whether a system-wide or user-specific disabling mechanism is more appropriate. Both have pros and cons, namely any former mechanism involves elevated privileges to effect, etc., and any latter mechanism bloats the user's $HOME. 2) Override the pulseaudio-shipped alsa-lib configuration files. Note that there would not be a need to use asoundconf or asoundconf-gtk. 3) Compile gnome-media without pulse support. 4) Change the default configurations for openal-soft and libsdl1.2 to use alsa instead of pulse. 5) Back out the patches to alsa-lib and alsa-plugins that have been applied so that pulse works better. 6) Create a metapackage that depends on packages that have these actions applied, and place them in a PPA. -- Pulseaudio should be easier to disable https://bugs.launchpad.net/bugs/545854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
