Didier - the slow boot and those 'cannot communicate' messages happened several times. However those seem to have gone away now, and boot time is much better than it was, although still slower than before this started:
~ $ systemd-analyze Startup finished in 10.061s (kernel) + 9.968s (userspace) = 20.030s I'm running from an SSD, and would normally see boot times in the 9-12s range. There is nothing in /var/crash related to plymouth. ~ $ systemctl status plymouth-start.service ● plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/lib/systemd/system/plymouth-start.service; enabled; vendor preset: enabled) Active: inactive (dead) since Mon 2015-03-23 22:10:11 EDT; 10h ago Process: 321 ExecStartPost=/bin/plymouth show-splash (code=exited, status=0/SUCCESS) Process: 316 ExecStart=/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS) Main PID: 320 (code=exited, status=0/SUCCESS) Mar 23 22:10:11 gazp6 systemd[1]: Starting Show Plymouth Boot Screen... Mar 23 22:10:11 gazp6 systemd[1]: Started Show Plymouth Boot Screen. I still don't see the Kubuntu logo on startup, but I do see it during the shutdown process. I can of course live without the logo on startup and the slightly longer boot times. The fsck errors are what prompted me to report this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1435126 Title: slow boot: systemd-fsck Cannot communicate fsck progress to fsckd: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1435126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
