Bug#781869: pulseaudio: sound total hangup when program using audio suddenly dies

[Felipe Sateler]

Hi,

On 20 April 2015 at 22:56, Joshua Hudson <joshudson at gmail.com> wrote:
>> Does audio continue working while you are on tty2? Is tty2 logged in?
>
> Yes and irrelevant (happens either way) Note that tty2 is a TEXT console (no X).

I'm not sure it is irrelevant:

% grep accessible pulseverbose.log
(   0.011|   0.001) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC0 is accessible: yes
(   0.057|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC1 is accessible: yes
(   0.116|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC0 is accessible: yes
(   0.116|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC1 is accessible: yes
(   5.121|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC0 is accessible: yes
(   5.121|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC1 is accessible: yes
(  13.798|   2.826) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC0 is accessible: yes
(  13.798|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC1 is accessible: yes
(  13.820|   0.022) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC0 is accessible: yes
(  13.820|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC1 is accessible: yes
(  22.031|   8.210) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC0 is accessible: yes
(  22.031|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC1 is accessible: yes
(  22.032|   0.001) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC0 is accessible: no
(  22.032|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC1 is accessible: no
(  22.032|   0.000) D: [pulseaudio] module-udev-detect.c:
/dev/snd/controlC1 is accessible: no

So in the beginning the cards are accessible, but somewhere along the
line they become inaccessible.

When you lose sound, what does `pactl list sinks` say?

>
> I did a reproduction with echo "--MARK--" >> ~/pulseverbose.log and
> killed pulseaudio immediately after (within 5 seconds) by ^C. However
> the echo line does not appear anywhere in the log file. Tried twice.
> No good. Maybe the 5 second window is good enough.
>
> Killing pulseaudio results in a sane system but sound will not play
> until a graphics logoff/logon. Curious.

Your initial report had the following:

Init: sysvinit (via /sbin/init)

Could you try booting under systemd and see if this problem persists?
Maybe the bug is in the systemd-shim layer. Pulseaudio relies on
logind or consolekit to correctly set the ACLs on the audio devices.

-- 

Saludos,
Felipe Sateler