[pulseaudio-discuss] [systemd-devel] user unit blocking login shell from popping out because wanted by default target?

Arun Raghavan arun at accosted.net
Tue Jan 12 19:13:51 PST 2016

On 13 January 2016 at 02:19, Lennart Poettering <lennart at poettering.net> wrote:
> On Sun, 10.01.16 22:25, Tom Yan (tom.ty89 at gmail.com) wrote:
>> So I am recently experiencing some issue with pulseaudio (which I
>> already filed a bug report:
>> https://bugs.freedesktop.org/show_bug.cgi?id=93651) that it takes a
>> long time to start.
>> The thing is, I am thinking whether it exposed a problem of systemd as
>> well. For example:
>> Jan 10 21:31:33 localhost systemd[257]: Starting Sound Service...
>> Jan 10 21:31:33 localhost systemd[257]: Started D-Bus User Message Bus.
>> Jan 10 21:31:39 localhost systemd[257]: Started Sound Service.
>> Jan 10 21:31:39 localhost systemd[257]: Reached target Default.
>> Jan 10 21:31:39 localhost systemd[257]: Startup finished in 5.830s.
>> As you can see, because of pulseaudio, it takes about 6 seconds to
>> reach the default target.
>> The reason I realise that pulseaudio is having this issue, is because
>> I can actually "experience" the 6 seconds after I entered my password
>> in the tty, if I have pulseaudio.service enabled. The login shell only
>> pops up after the default target has been reached.
> Why would it wait for that?
> Also, PA taking 6s to start is quite something...

Yeah, that's clearly a (separate) bug, being tracked at:

-- Arun

More information about the pulseaudio-discuss mailing list