Bug#800120: pulseaudio: No sound after upgrade to pulseaudio 7.0-1

Felipe Sateler fsateler at debian.org
Mon Sep 28 11:13:40 UTC 2015


Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=92141

On 28 September 2015 at 07:03, Felipe Sateler <fsateler at debian.org> wrote:
> Control: tags -1 moreinfo
>
> Hi,
>
> On 26 September 2015 at 23:50, john <johnw.mail at gmail.com> wrote:
>> Package: pulseaudio
>> Version: 7.0-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> *** Reporter, please consider answering these questions, where appropriate ***
>>
>>    No sound after upgrade pulseaudio 7.0-1,
>>    when I run alsamixer:
>>
>>    ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect:
>>    Protocol error
>>
>>    cannot open mixer: Connection refused
>
> Could you please attach a verbose log of pulseaudio[1] and then reproduce this?
>
> Also, does pavucontrol work or only alsamixer fails?

Here are better instructions provided by upstream[1], if you could
post the information it would be great.

First, install libpulse0-dbg, pulseaudio-utils-dbg and gdb. Then
follow the steps described by upstream:


% PULSE_LOG=99 gdb --args pactl stat

That will print something like this:

GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from pactl...done.
(gdb)

You're now in the gdb prompt. Enter "break pa_memimport_get". That
symbol hasn't yet been loaded, so gdb asks you whether to add the
breakpoint when the symbol becomes available. Answer "y". Then enter
"run". The execution should soon stop at the breakpoint. From now on
enter "n" ("n" is short for "next") repeatedly until the program exits
(that will take quite some time). When the program exits, you can quit
gdb with command "quit", and then save all the terminal output and
attach it here. That should show the exact place that fails.



[1] https://bugs.freedesktop.org/show_bug.cgi?id=92141#c6


-- 

Saludos,
Felipe Sateler



More information about the pkg-pulseaudio-devel mailing list