Bug#859926: ping: 859926: breaks with pulse-audio as output when spawned by speechd-up from init system
Control: tags -1 buster-ignore Hi, On Sun, May 21, 2017 at 09:08:44PM +0200, Paul Gevers wrote: > Any progress on this issue? Seems like nobody is working on it. It also > looks like the underlaying issue (pulseaudio & speech-dispatcher > combination) has been known for years and hasn't received much > attention. Is the solution just not possible because it requires a > choice for the default of pulseaudio between non-secure and working, or > secure and non-working (given the goals and designs of the tools > involved)? And currently the behavior is more secure and thus not > working out of the box for pulseaudio users (but working for alsa users)? > > Maybe the "solution" is to acknowledge the situation, disable the init > scripts by default (at least of speechd-up, although that would also > cause alsa users to not have speechd-up) and describe it properly in the > documentation (I originally wrote debconf, but I don't think that is > allowed), such that the user can be told how to fix it (I don't know, > but it seems that starting pulseaudio as system user may solve the issues). > > Obviously, if we are convinced that what I describe above is correct, > then we could add some detection for alsa vs pulseaudio into the loop > (no idea how that would work and unsure which package(s) should do that). Unfortunately, it doesn't look like this will be fixed for buster... Ivo
Bug#859926: ping: 859926: breaks with pulse-audio as output when spawned by speechd-up from init system
Hi all, Any progress on this issue? Seems like nobody is working on it. It also looks like the underlaying issue (pulseaudio & speech-dispatcher combination) has been known for years and hasn't received much attention. Is the solution just not possible because it requires a choice for the default of pulseaudio between non-secure and working, or secure and non-working (given the goals and designs of the tools involved)? And currently the behavior is more secure and thus not working out of the box for pulseaudio users (but working for alsa users)? Maybe the "solution" is to acknowledge the situation, disable the init scripts by default (at least of speechd-up, although that would also cause alsa users to not have speechd-up) and describe it properly in the documentation (I originally wrote debconf, but I don't think that is allowed), such that the user can be told how to fix it (I don't know, but it seems that starting pulseaudio as system user may solve the issues). Obviously, if we are convinced that what I describe above is correct, then we could add some detection for alsa vs pulseaudio into the loop (no idea how that would work and unsure which package(s) should do that). Paul signature.asc Description: OpenPGP digital signature
