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

[Andreas B. Mundt]

Here we go ....

On Tue, Jan 19, 2016 at 04:22:50PM -0300, Felipe Sateler wrote:
> On 19 January 2016 at 14:58, Andreas B. Mundt <andi at debian.org> wrote:

> > Exactly.  Any ideas how to continue?
>
> Lets get a verbose log. Please create/edit ~/.config/pulse/daemon.conf and
> add the following content:
>
> log-target = file:/home/<youruser>/pulse.log
> log-time = yes
>

No log messages appear in "/home/<youruser>/pulse.log" with that
change.  However, I tried a few things and finally got something in
the log by adding:

          extra-arguments = --log-target=file:/home/<username>/pulse-client.log

in "/etc/pulse/client.conf".  The content after running the torified
command and killing it as well as pulseaudio are 509859 lines like:

        (   0.000|   0.000) E: [pulseaudio] socket-server.c: accept(): Bad address
...
        (   3.241|   0.000) E: [pulseaudio] socket-server.c: accept(): Bad address

Does this give any clue?  Perhaps I should switch on some more
verbosity ...

Thanks,

        Andi