Takashi Iwai wrote:
At Mon, 25 Jul 2011 09:16:33 +0200, Ludwig Nussel wrote:
Vincent Untz wrote:
I'm fixing this, see https://bugzilla.novell.com/show_bug.cgi?id=707703 for a small discussion. With the fix, when the pulseaudio package is installed/updated, relevant configuration files are updated based on the PULSEAUDIO_ENABLE setting.
On the one hand people are complaining about SuSEconfig and we try to get rid of it. On the other hand we introduce scripts like pulseaudio-setup that are even worse. IMO that script needs to be removed. Instead the apps it tries to configure must be patched to probe for PA (ie without autospawn) and use it when available. That way applications started in a PA enabled session use PA but when started in a session without PA transparently fall back to alsa/OSS. That's how e.g. openal-soft behaves.
FYI, I implemented it for alsa-lib pulse plugin. Now it falls back to the system-default (e.g. dmix) when the connection to PA failed.
Nice. Does that mean it's safe now to enable alsa-plugins-pulse unconditionally? Ie without the special asound-pulse.conf? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org