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

[Felipe Sateler]

Control: tags -1 - moreinfo

On 19 January 2016 at 18:35, Andreas B. Mundt <andi at debian.org> wrote:
> On Tue, Jan 19, 2016 at 06:07:33PM -0300, Felipe Sateler wrote:
>> On 19 January 2016 at 17:53, Andreas B. Mundt <andi at debian.org> wrote:
>
> [...]
>
>> > Does this give any clue?  Perhaps I should switch on some more
>> > verbosity ...
>>
>> Yes, please, and attach the full log. Sorry, I missed that part of the conf...
>>
>
> Now we have something that looks more usefull.  For the record:
>
>     cat ~/.config/pulse/daemon.conf
>     log-target = file:/home/<user>/pulse.log
>     log-time = yes
>     log-level = debug
>
>     cat ~/.config/pulse/client.conf
>     extra-arguments = --log-target=file:/home/<user>/pulse-client.log
>
> pulse-client.log is attached, pulse.log is empty.  (I had to cut
> (i.e. remove some almost identical lines) from pulse-client.log to
> make the mailserver happy).

OK, I need a few days to actually look into this (I hope to look at
this in the coming days).

BTW, can you reproduce by using

% killall pulseaudio
% torify pulseaudio --start

?



-- 

Saludos,
Felipe Sateler