Bug 537780

Summary:	setup-pulseaudio --disable does not actually disable PulseAudio
Product:	[openSUSE] openSUSE 11.2	Reporter:	Lubos Lunak <llunak>
Component:	Sound	Assignee:	Scott Reeves <sreeves>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P2 - High	CC:	binner, gp, lnussel, lslezak, tiwai, zajec5
Version:	Factory
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Lubos Lunak 2009-09-09 15:50:50 UTC

Running 'setup-pulseaudio --disable' (which is what Yast does to disable PA) does not actually disable PA. After next (KDE) desktop startup, the pulseaudio daemon is still running.

Additionally, it seems that 'setup-pulseaudio --status' does not initially give correct value.

Both of these seem to be caused by the fact that setup-pulseaudio writes status to /etc/sysconfig/sound, but this is nowhere used. I suggest the start-pulseaudio-x11 script checks this and does not start anything if disabled.

Yast should also probably call this script during installation to set up the proper initial status (I will create another bugreport for this).

Comment 1 Takashi Iwai 2009-09-14 09:44:12 UTC

The suggestions sounds reasonable.  Scott, any chance to fix it?

Meanwhile, it's not too difficult to make PA to work together with others, just use the default ALSA PCM definition instead of grabbing the hw device...

Comment 2 Ladislav Slezák 2009-09-22 12:43:20 UTC

I have fixed the Yast config problem (bug #537784).

Scott, could you look at it? This is quite important, having fixed the Yast part is useless without PA setup fix.

Comment 3 Lubos Lunak 2009-09-28 18:47:50 UTC

See SR#21254 for my patches fixing this.

Comment 4 Scott Reeves 2009-10-02 05:38:20 UTC

hmm, I guess if we are going to rely on the setup-pulseaudio script being run it could use some work. I would think the mplayer section should not exist - we should just setup the default alsa plugin to be pulse and then have mplayer talk to the default. I have no idea what would be needed for the xine and openal section.

Takashi - do you have thoughts on this.

Comment 5 Takashi Iwai 2009-10-02 06:15:19 UTC

mplayer's default behavior is somehow odd.  It first probes OSS, ALSA, then rest.  And, because of SPDIF support, mplayer would choose another ALSA PCM device depending on the usage.

So, for PA, basically it's safer to change the default setup in the config file.

The openal was recently changed to openal-soft, and this has a system-wide config file in /etc/openal/alsoft.conf.  The drivers section corresponds to it.

I also have no idea whether xine has a system-wide config file, too.

Comment 6 Ladislav Slezák 2010-04-12 14:21:03 UTC

(Removing the dependency so bug #537784 can be closed as FIXED.)

Comment 7 Rafał Miłecki 2010-07-20 11:01:13 UTC

So, can we close this? Lubos?

Comment 8 Lubos Lunak 2010-07-20 11:49:41 UTC

I'm fine with closing this, but I don't know why it has been kept open.

Comment 9 Scott Reeves 2010-08-10 20:51:13 UTC

It can be closed as fixed...