Univention Bugzilla – Bug 31126
fix upstart plymouth dependencies
Last modified: 2014-06-12 09:20:09 CEST
With kdm/autostart=no on an UCC client plymouth is stopped in the boot process very early which leads to a text console login prompt (especially annoying for software updates). Reason for that is in /etc/init/plymouth-stop.conf
Probably it is an ubuntu standard to start the login manager before ending runlevel 2. In this case plymouth-stop.conf does nothing, but if plymouth-stop.conf is triggered by the stop of runlevel 2, it stops plymouth.
In UCC the start of the display manager lightdm is delayed by ucc-policy and the software-update. So lightdm never triggers plymouth-stop.conf and plymouth is stopped by the stop of runlevel 2 (under some circumstances long before the start of lightdm).
But we have also a kdm init script /etc/init/kdm.conf which triggers plymouth-stop.conf "correctly" (no plymouth stop) if kdm/autostart is not no. Unfortunately kdm/autostart=no is the standard for ucc desktop images.
(1) Remove /etc/init/kdm.conf (the default display manager is configured in /etc/X11/default-display-manager) and kdm/autostart
(2) Fix upstart dependencies for plymouth-stop.conf
Added a new ucr template /etc/init/plymouth-stop.conf. This script does no longer stop plymouth. Instead added "plymouth quit" to /etc/init/ucc-update.conf
The bootsplash is now seamless during a normal boot and when installing software updates.
UCC 2.0 has been released:
If this error occurs again, please use "Clone This Bug".