Bug#783974: pulseaudio: No sound on boot till pulseaudio is killed and restarted

[Felipe Sateler]

On 2 May 2015 at 12:27, L. Guruprasad <lgp171188 at gmail.com> wrote:
> On Saturday 02 May 2015 08:44 PM, Felipe Sateler wrote:
>> OK, then set log-target = journal. I see you are using systemd as
>> init, so you can do the following:
>>
>> journalctl -b /usr/bin/pulseaudio
>>
>> To get the log.
>
> guruprasad at kal-el:~$ journalctl -b /usr/bin/pulseaudio
> No journal files were found.
>
>
>> Also, I have assumed you do not have a local configuration. What are
>> the contents of ~/.config/pulse ?
>
> guruprasad at kal-el:~$ ls ~/.config/pulse/
> 21544ca2d6123577f1d4e77452766946-card-database.tdb
> 21544ca2d6123577f1d4e77452766946-default-sink
> 21544ca2d6123577f1d4e77452766946-default-source
> 21544ca2d6123577f1d4e77452766946-device-volumes.tdb
> 21544ca2d6123577f1d4e77452766946-stream-volumes.tdb
> client.conf
> cookie
>
> guruprasad at kal-el:~$ cat ~/.config/pulse/client.conf
> autospawn = no

This is the problem. Why do you have disabled autospawn?

So, a bit of background:

In pulseaudio up to version 5, the script start-pulseaudio-x11 started
pulseaudio and loaded some modules. But in version 6, systemd support
was added so that you could start pa as a user service. This meant
that starting pulseaudio from outside systemd could interfere with
starting it with inside, so start-pulseaudio-x11 was changed to no
longer start pa, instead relying on either systemd support or
autospawn to start the server. In debian we have not enabled systemd
by default because of problems with dbus, so we rely on autospawn.

All this is a fairly long way of saying that you have disabled
pulseaudio by disabling autospawn.

So please remove that client.conf file and see if it works (and undo
the changes to /etc/pulse/*).


-- 

Saludos,
Felipe Sateler