Bug#811266: pulseaudio: log is flooded sometimes when combined with torsocks (torify)

[Andreas B. Mundt]

Hi Felipe,

thanks for your fast reply.

On Mon, Jan 18, 2016 at 04:16:19PM -0300, Felipe Sateler wrote:
> On 18 January 2016 at 15:54, Andreas B. Mundt <andi at debian.org> wrote:

[...]

> Hmm, so this suggests that there is some problem when autospawning
> pulseaudio. The contents of ~/.config/pulse/client.conf include only
> the autospawn setting, right? This would be consistent with the
> observation that it only breaks the first time since boot.

Yes, normally ~/.config/pulse/client.conf does not exist here.

> Can you reproduce the problem if you try using mpg321 without torify
> first, and then with torify?

Indeed.  I can reproduce always with:

         killall pulseaudio
         torify mpg321 http://mp3stream1.apasf.apa.at:8000

whereas:

         killall pulseaudio
         mpg321 http://mp3stream1.apasf.apa.at:8000
         torify mpg321 http://mp3stream1.apasf.apa.at:8000

works fine.

> Also, I see you are using systemd. You may want to try the following:
>
> 1. Set the autospawn setting to false in ~/.config/pulse/client.conf
> 2. Run (as your own user): systemctl --user enable pulseaudio.socket
> 3. Reboot and try to reproduce.

I'll try that later.

> Seems to be the autospawn setting. Torify may be changing the
> environment enough that pulseaudio cannot cope with it.

Exactly.  Any ideas how to continue?

Best regards,

     Andi