[Touch-packages] [Bug 1435126] Re: slow boot: systemd-fsck Cannot communicate fsck progress to fsckd: Broken pipe

2015-03-26 Thread ronwilhoite
For what it is worth, I've rebooted a few times since re-installing from a daily iso and this problem has not happened again. I see the Kubuntu logo flash on startup, and shutdown, and boot times are back in the 15s range. No fsck errors in the journal. -- You received this bug notification be

[Touch-packages] [Bug 1435126] Re: slow boot: systemd-fsck Cannot communicate fsck progress to fsckd: Broken pipe

2015-03-24 Thread ronwilhoite
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)

[Touch-packages] [Bug 1435126] [NEW] slow boot: systemd-fsck Cannot communicate fsck progress to fsckd: Broken pipe

2015-03-22 Thread ronwilhoite
Public bug reported: The computer eventually boots after a long delay. Possibly related, plymouth does not display the Kubuntu logo, or anything else, during this time. The top two entries for systemd-analyze blame are: 30.570s systemd-fsck@dev-disk-by\x2duuid-03562ae0\x2d19b0\x2d4e47\x2d9d17\x