Control: tags -1 moreinfo

Hello Bogdan,


On Jan 10, 2017 07:39, "Bogdan Vatra" <bogdan.va...@kdab.com> wrote:

Package: pulseaudio
Version: 9.0-5
Severity: important

--- Please enter the report below this line. ---
For some time (~1month) pulseaudio doesn't work anymore on my system (after
I
upgrade my os ~1mounth ago). Until now I just removed it because didn't had
time to check. But today I've installed libpulse0-dbgsym and
pulseaudio-dbgsym
packages and I could trace (more or less) the problem.

$ gdb pactl
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 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...(no debugging symbols found)...done.
(gdb) set args stat
(gdb) r
Starting program: /usr/bin/pactl stat
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
^C
(gdb) bt
#0  0x00007ffff727cb2a in __waitpid (pid=pid@entry=990,
stat_loc=stat_loc@entry=0x7fffffffd8f8, options=options@entry=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:29
#1  0x00007ffff7b98d00 in context_autospawn (c=c@entry=0x5555557647c0) at
pulse/context.c:751
#2  0x00007ffff7b9900f in try_next_connection (c=c@entry=0x5555557647c0) at
pulse/context.c:843
#3  0x00007ffff7b99c7d in pa_context_connect (c=0x5555557647c0,
server=<optimized out>, flags=<optimized out>, api=0x0)
    at pulse/context.c:1042
#4  0x0000555555557a04 in main ()

As you can see it's hanged in context_autospawn, sadly I have no idea what
to
do next (besides removing it again) :).


This suggests the server is failing to start. Is there a pulseaudio process
running?(my guess is not) Could you start pulseaudio manually in verbose
mode to see what it says?

pulseaudio -vvvv --log-target=file:pa.log

And then please attach pa.log to this report

Saludos,
Felipe Sateler

Reply via email to