On Fri, Apr 10, 2015 at 07:29:57PM -0400, Anthony DeRobertis wrote: > If you do a README.Debian update to fix that typo, here is another > thing to add—this makes bb work on my PA system: > > pasuspender -- env PULSE_SERVER= bb > > pasuspender makes PulseAudio release the sound hardware, then setting > PULSE_SERVER= to blank makes bb not connect to PA (falling back to ALSA > instead, which works).
That's very nice, thanks! It makes me wonder; would it make sense, instead of disabling the music by default, to have a wrapper that runs bb with this hack, so that the music can work? (Otherwise the user need to find and read the README to find out about this, which is not ideal...) Of course, the devil is in the details: implementing this solution would require pasuspender, hence pulseaudio-utils; however having bb depend on pulseaudio-utils would be strange as the hack is only needed because of pulseaudio itself. Ideally the wrapper could be smarter and only disable the music when pulseaudio seems in use but pasuspender is not installed, but that's not so easy because bb does not seems to have flags to control the music from the command-line when running it. So I don't know if that's a reasonable idea, but I wanted to make the suggestion. -- Antoine Amarilli
signature.asc
Description: Digital signature
