Like the poster in comment #16, I only started experiencing this problem after installing (and later purging) ClamAV. I wonder if this is pure coincidence, or if something that gets installed with ClamAV triggers the issue. Note: ClamAV was installed when claws-mail-clamd-plugin was installed (which I've also since purged).
I've reinstalled plymouth, but the error remains.
3.11.0-19-generic #33~precise1-Ubuntu SMP Wed Mar 12 21:16:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
(linux-generic-lts-saucy)
Like the poster in comment #16, I only started experiencing this problem after installing (and later purging) ClamAV. I wonder if this is pure coincidence, or if something that gets installed with ClamAV triggers the issue. Note: ClamAV was installed when claws-mail- clamd-plugin was installed (which I've also since purged).
I've reinstalled plymouth, but the error remains.
3.11.0-19-generic #33~precise1-Ubuntu SMP Wed Mar 12 21:16:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux generic- lts-saucy)
(linux-
$ apt-cache policy plymouth archive. ubuntu. com/ubuntu/ precise- updates/ main amd64 Packages dpkg/status 8.2-2ubuntu30 0 archive. ubuntu. com/ubuntu/ precise/main amd64 Packages
plymouth:
Installed: 0.8.2-2ubuntu31.1
Candidate: 0.8.2-2ubuntu31.1
Version table:
*** 0.8.2-2ubuntu31.1 0
500 http://
100 /var/lib/
0.
500 http://
dmesg:
[ 70.411380] init: plymouth-stop pre-start process (3290) terminated with status 1