Thank you for taking the time toreport this bug and help to improve Ubuntu.
plymouth is not a splash screen, it's an I/O multiplexer which supports multiple outputs - including graphical splash. It is an essential component of the boot process in Lucid regardless of whether the boot splash is of interest, and cannot be disabled.
The bug here is with slim integration with plymouth. The slim package needs to be converted to use an upstart job instead of an init script, as gdm, kdm, xdm, and lxdm all have been, so that plymouth can be told to stop when slim is starting. As long as slim uses a sysvinit script instead of an upstart job, this is not possible.
Thank you for taking the time toreport this bug and help to improve Ubuntu.
plymouth is not a splash screen, it's an I/O multiplexer which supports multiple outputs - including graphical splash. It is an essential component of the boot process in Lucid regardless of whether the boot splash is of interest, and cannot be disabled.
The bug here is with slim integration with plymouth. The slim package needs to be converted to use an upstart job instead of an init script, as gdm, kdm, xdm, and lxdm all have been, so that plymouth can be told to stop when slim is starting. As long as slim uses a sysvinit script instead of an upstart job, this is not possible.