Thanks, Steve. The box was set up by a vendor (Emperor Linux), so perhaps they did something custom with the splash screens when I got it 18 months ago.
Aesthetically, making something vital (UI startup) depend on something decorative (splash screens) seems odd. Perhaps future versions of this can be made more robust.
In case somebody else with a similar problem finds this bug report, I verified the problem by using debsums
Thanks, Steve. The box was set up by a vendor (Emperor Linux), so perhaps they did something custom with the splash screens when I got it 18 months ago.
Aesthetically, making something vital (UI startup) depend on something decorative (splash screens) seems odd. Perhaps future versions of this can be made more robust.
In case somebody else with a similar problem finds this bug report, I verified the problem by using debsums
% sudo debsums -a plymouth plymouth- log.conf (from plymouth package) plymouth- upstart- bridge. conf (from plymouth package) init/plymouth. conf OK plymouth- stop.conf (from plymouth package) init/plymouth- ready.conf OK plymouth- splash. conf (from plymouth package)
[most package items ok]
debsums: missing file /etc/init/
debsums: missing file /etc/init/
/etc/
debsums: missing file /etc/init/
/etc/
debsums: missing file /etc/init/
And the precise command I used to fix the problem was: :=--force- confmiss install plymouth
% sudo apt-get --reinstall -o Dpkg::Options:
That put back the missing files.
I also did "sudo debsums -s" to make sure nothing else important was missing.