[opensuse-factory] Coming change: PulseAudio configuration enforced by default
Hi, For a while now, it has been possible to enable/disable PulseAudio by setting the PULSEAUDIO_ENABLE variable in /etc/sysconfig/sound and by calling the setup-pulseaudio helper. However, by default, there was no such PULSEAUDIO_ENABLE variable in /etc/sysconfig/sound (fillup wasn't called), and on new installs, this setting was not propagated to various files. This resulted in no real enforcement of the PA configuration. 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. This might impact people who either had a customized sound configuration for PulseAudio (ie, PA disabled for, say, libao but enabled for alsa), or for people who had manually disabled PulseAudio with just the setup-pulseaudio helper: PULSEAUDIO_ENABLE will be set to "yes" if it's not already defined, and that will forcefully enable PA everywhere. The solution is to edit /etc/sysconfig/sound and set PULSEAUDIO_ENABLE to either "no" (which means "don't use PulseAudio") or "custom" (which means "do not touch the PulseAudio-related configuration). This should also get mentioned in release notes for 12.1. What's the best way to make sure this happens? Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag, 22. Juli 2011, 18:06:54 schrieb Vincent Untz:
This should also get mentioned in release notes for 12.1. What's the best way to make sure this happens?
Filing a bug report against component "release notes" Greetings, Stephan -- Sent from openSUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Fredag den 22. juli 2011 18:06:54 skrev Vincent Untz:
The solution is to edit /etc/sysconfig/sound and set PULSEAUDIO_ENABLE to either "no" (which means "don't use PulseAudio") or "custom" (which means "do not touch the PulseAudio-related configuration).
Will it still be possible to turn the stuff off, with YaST or the 'setup- pulseaudio' script? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le vendredi 22 juillet 2011, à 19:55 +0200, Martin Schlander a écrit :
Fredag den 22. juli 2011 18:06:54 skrev Vincent Untz:
The solution is to edit /etc/sysconfig/sound and set PULSEAUDIO_ENABLE to either "no" (which means "don't use PulseAudio") or "custom" (which means "do not touch the PulseAudio-related configuration).
Will it still be possible to turn the stuff off, with YaST or the 'setup- pulseaudio' script?
Yes, no change there. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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. 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
Le lundi 25 juillet 2011, à 09:16 +0200, Ludwig Nussel a écrit :
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.
I agree that it'd be better to not have pulseaudio-setup. However, the issue is not so much an issue with various apps, than the fact that the alsa and libao libraries would need to detect PA and use it when it's there (which implies potentially ignoring some other configuration bits). Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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. The feature is included now in OBS multimedia:libs/alsa and alsa-plugins. Once after some tests, I'll submit to FACTORY. Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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
At Wed, 27 Jul 2011 08:53:00 +0200, Ludwig Nussel wrote:
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?
/etc/asound-pulse.conf is still needed since alsa-plugins-pulse is an add-on package, but /etc/alsa-pulse.conf (how confusing!) can be merged to the default configuration, yes. That is, alsa-plugins-pulse will be activated automatically when the package is installed. So far, it's activated only when $ALSA_CONFIG_PATH=/etc/alsa-pulse.conf is set (which was done in setup-pulseaudio script). One remaining problem is that PA library always spews an error message when a connection failed from a client and there is no way to suppress it. This is annoying behavior, and should be fixed in PA side. Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Takashi Iwai wrote:
At Wed, 27 Jul 2011 08:53:00 +0200, Ludwig Nussel wrote:
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?
/etc/asound-pulse.conf is still needed since alsa-plugins-pulse is an add-on package, but /etc/alsa-pulse.conf (how confusing!) can be merged to the default configuration, yes. That is, alsa-plugins-pulse will be activated automatically when the package is installed. So far, it's activated only when $ALSA_CONFIG_PATH=/etc/alsa-pulse.conf is set (which was done in setup-pulseaudio script).
One remaining problem is that PA library always spews an error message when a connection failed from a client and there is no way to suppress it. This is annoying behavior, and should be fixed in PA side.
AFAICS you don't pass PA_CONTEXT_NOAUTOSPAWN. Ie the lib will try to start the daemon then. It would only fail if pulseaudio is actually uninstalled. By passing PA_CONTEXT_NOAUTOSPAWN the connection just silently fails if the daemon isn't running. 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
At Wed, 27 Jul 2011 09:19:31 +0200, Ludwig Nussel wrote:
Takashi Iwai wrote:
At Wed, 27 Jul 2011 08:53:00 +0200, Ludwig Nussel wrote:
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?
/etc/asound-pulse.conf is still needed since alsa-plugins-pulse is an add-on package, but /etc/alsa-pulse.conf (how confusing!) can be merged to the default configuration, yes. That is, alsa-plugins-pulse will be activated automatically when the package is installed. So far, it's activated only when $ALSA_CONFIG_PATH=/etc/alsa-pulse.conf is set (which was done in setup-pulseaudio script).
One remaining problem is that PA library always spews an error message when a connection failed from a client and there is no way to suppress it. This is annoying behavior, and should be fixed in PA side.
AFAICS you don't pass PA_CONTEXT_NOAUTOSPAWN. Ie the lib will try to start the daemon then. It would only fail if pulseaudio is actually uninstalled. By passing PA_CONTEXT_NOAUTOSPAWN the connection just silently fails if the daemon isn't running.
Good point. This can be set conditionally when the fallback option is set. I'll add the patch now. thanks, Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (5)
-
Ludwig Nussel -
Martin Schlander -
Stephan Kulow -
Takashi Iwai -
Vincent Untz