[Bug 982889] Re: X trying to start before plymouth has finished using the drm driver
William Pietri
william-launchpad.net at scissor.com
Wed Jun 5 17:39:07 UTC 2013
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
[most package items ok]
debsums: missing file /etc/init/plymouth-log.conf (from plymouth package)
debsums: missing file /etc/init/plymouth-upstart-bridge.conf (from plymouth package)
/etc/init/plymouth.conf OK
debsums: missing file /etc/init/plymouth-stop.conf (from plymouth package)
/etc/init/plymouth-ready.conf OK
debsums: missing file /etc/init/plymouth-splash.conf (from plymouth package)
And the precise command I used to fix the problem was:
% sudo apt-get --reinstall -o Dpkg::Options::=--force-confmiss install plymouth
That put back the missing files.
I also did "sudo debsums -s" to make sure nothing else important was
missing.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/982889
Title:
X trying to start before plymouth has finished using the drm driver
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/982889/+subscriptions
More information about the kubuntu-bugs
mailing list