On 15 February 2016 at 16:11, Rodrigo Campos <rodr...@sdfg.com.ar> wrote: > Now with 812...@bugs.debian.org on "Cc:" > > On Mon, Feb 15, 2016 at 07:11:04PM +0000, Rodrigo Campos wrote: >> On Mon, Feb 15, 2016 at 03:53:07PM -0300, Felipe Sateler wrote: >> > On 15 February 2016 at 13:23, Rodrigo Campos <rodr...@sdfg.com.ar> wrote: >> > > On Mon, Feb 15, 2016 at 12:58:58PM -0300, Felipe Sateler wrote: >> > >> >> > >> You can work around this by disabling the x11 publish module, via >> > >> disabling the autostart of start-pulseaudio-x11 (by removing/moving >> > >> away the /etc/xdg/autostart/pulseaudio.desktop file). >> > > >> > > Ohh, I can confirm that this workaround works. >> > > >> > > >> > > Let me know if you need more info or I can help you with testing the fix >> > >> > I don't think there is anything we can do on the debian side. Maybe >> > you can raise the issue upstream and see whether they come up with a >> > way to support your use case? I don't think I want to deviate from >> > upstream in this respect. >> >> I was not asking to deviate from upstream, just fix the bug.
Well, the behavior comes from upstream, so if we change something we would be deviating. Moreover, I'm not sure what you are experiencing is actually a bug, or it is simply an unsupported configuration (due to better behaved alternatives existing). Pulseaudio is correctly discovering an existing server, and so it refuses to start. Whether the old behavior was OK or not, is only a call upstream can make. >> Would you forward >> it upstream, then? No, sorry. When feedback will be requested by upstream then I won't be able to provide it. The only way, then, is for you to file the bug to the upstream bugzilla: http://bugs.freedesktop.org -- Saludos, Felipe Sateler
