Bug#910512: pulseaudio: Pulseaudio takes longer to start than default systemd timeout

[Mr riaas mokiem]

 I think I've got the log. I had to edit the main pulseaudio.service file because it was saying something about "bad unit" when I used the suggested command. And I could only find the logs in the main journalctl output (not with --user or --unit or --user-unit) so I just grepped on pulseaudio which is why the logs also contain some other lines (like dbus for pulseaudio). 

I made one log with the default timeout of systemd, showing that it times out, pulseaudio_system_log_timeout.txtI made another one where I set the timeout to 5 minutes, pulseaudio_system_log.txt
I hope this helps. It seems that the startup time went from below 90 seconds (default systemd timeout) to a bit more than 2 minutes. So I'm not sure if there was something else slowing down this startup even before I noticed this timeout.

    On Wednesday, October 10, 2018, 3:28:31 PM GMT+2, Felipe Sateler <fsateler at debian.org> wrote:  
 
 Control: severity -1 importantControl: tags -1 moreinfo
Hi,
On Sun, Oct 7, 2018 at 11:21 AM Riaas Mokiem <riaasm at yahoo.com> wrote:

Package: pulseaudio
Version: 12.2-2
Severity: grave
Justification: renders package unusable



Lowering severity since it does not appear to affect everyone. 
Dear Maintainer,

Pulseaudio is taking longer to start up than the default 90 seconds that 
systemd allows for a service. This means that Pulseaudio does not work on 
startup and no matter how much you try to restart it (through systemd), 
it won't start up correctly. 

Not sure if this is the cause, but this happened after a recent upgrade that 
removed consolekit and upgraded the linux kernel from 4.18.0-1 to 4.18.0-2
I changed the timeout of pulseaudio.service to 5 minutes which allowed
Pulseaudio sufficient time to start up correctly. 

I have pretty decent hardware though, so I would have expected the default
timeout for Pulseaudio to be more than sufficient. It has been sufficient 
on this hardware until now. I'm not sure what's relevant for Pulseaudio, but
my system uses the motherboard's onboard sound chip (Realtek ALC S1220A) on
an AMD Ryzen system.

I'm not sure why Pulseaudio is suddenly taking so much longer to start (or maybe
systemd shortened the default timeout). But it's worth noting that for some 
reason I still had HDMI audio output, even with pulseaudio timed out. This is
something that actually hadn't worked before and I haven't really tested it
since the kernel with amdgpu dc has been available. Not sure if that's relevant.
 

Possibly. Could you attach a verbose log?
$ systemctl --user --runtime edit pulseaudioAdd the following lines to the file[Service]ExecStart=/usr/bin/pulseaudio --daemonize=no -vvvv

Then restart pulseaudio, and get the log with `journalctl --user-unit pulseaudio --since "$when_you_restarted_pulseaudio"`
 -- 
Saludos,
Felipe Sateler  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pulseaudio-devel/attachments/20181013/57820b0a/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pulseaudio_system_log_timeout.txt
URL: <http://alioth-lists.debian.net/pipermail/pkg-pulseaudio-devel/attachments/20181013/57820b0a/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pulseaudio_system_log.txt
URL: <http://alioth-lists.debian.net/pipermail/pkg-pulseaudio-devel/attachments/20181013/57820b0a/attachment-0003.txt>