Plymouth killing my boot time

[oshunluvr]

For the last few months I've experienced a noticeably longer boot time. It hasn't bothered me enough to look into it, but this morning I dug a bit.

stuart@office:/var/log$ sudo systemd-analyze blame
         28.504s plymouth-read-write.service
         27.038s plymouth-quit-wait.service
         20.248s plymouth-quit.service
         16.990s plymouth-start.service

Clearly, plymouth is killing me. That's a whole minute and a half.

I've seen some similar bugs reported but none of them apply exactly nor do the fixes work.

Is anyone else seeing this delay?

[oshunluvr]

Removing "splash" from the boot line removes the delay. I can live with that, but IMO plymouth has been a huge PITA since it was introduced.

[claydoh]

I don't see it here

72ms plymouth-quit.service
72ms plymouth-quit-wait.service
17ms plymouth-start.service
11ms plymouth-read-write.service

is there any process shown in 'critical-chain' that might be holding Plymouth back or something?

[Don B. Cilly]

Well, why not get rid of splash (and quiet while you're at it)?
It's better than watching TV

I mean, anything is better than watching TV, but... splash screens, once you've seen then once... or twice... ;-)

[vinnywright]

just to add to ,,,,

vinny@vinny-Bonobo-Extreme:~$ systemd-analyze blame
       29.063s plymouth-start.service
       24.653s systemd-journal-flush.service
       17.747s plymouth-read-write.service
       17.581s dev-sda6.device
        8.552s udisks2.service

then further down

896ms plymouth-quit.service
896ms plymouth-quit-wait.service

VINNY

[vinnywright]

Also as I think I remember you (@oshunluvr) saying in a another thread just removing the "quiet splash" will not let me see all the beautiful boot messages flying by , I must remove the "vga=0x034d $vt_handoff" as well then all the beautiful boot messages will show ,,,,,,,at least @hear

and the only "plymouth" in the systemd-analyze blame output is wayyyyy at the bottom

VINNY