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

[Andreas B. Mundt]

Control: tags -1 - moreinfo

Hi Felipe,

thanks for your debugging hints.

On Mon, Jan 18, 2016 at 09:56:27AM -0300, Felipe Sateler wrote:
> On 17 January 2016 at 09:09, Andreas B. Mundt <andi.mundt at web.de> wrote:

> > when playing a stream using a music player with torsocks like:
> >
> >       torify mpg321 http://mp3stream1.apasf.apa.at:8000
> >
> > it happens sometimes that no music is played, instead the log is
> > flooded with identical messages like:
> >
> >         pulseaudio[3148]: [pulseaudio] socket-server.c: accept(): Bad address

[...]

> > I've not figured out yet when it works, it seems to fail only the
> > first time after reboot.  Once pulseaudio is killed and tried again, it
> > seems to work, also after stopping and starting again there where no
> > issues so far.


> Could you attach a verbose log of when the problem happens?
>
> https://wiki.ubuntu.com/PulseAudio/Log

I tried to fetch a log.  However, whenever I run pulseaudio like

  LANG=C pulseaudio -vvvv --log-time=1 > ~/pulseverbose.log 2>&1

it worked fine.  Removing ~/.config/pulse/client.conf and executing

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

the normal way again resulted in the flooded log.  I switched back and
forth several times and it was always the same, even with  "-vvvv
  --log-time=1" removed from the pulseaudio command.

So there must be some difference in the way pulseaudio works one way
or the other which influence the error.

Best regards,

     Andi