plymouth 0.9.0 can not use framebuffer for terminal: none
Some users without proper kms/drm support (e.g. virtualbox, proprietary drivers, embedded) are unable to use plymouth's fallback to framebuffer renderer.
1) lsb_release -rd
Description: Ubuntu Utopic Unicorn (development branch)
2) apt-cache policy plymouth
*** 0.9.0-0ubuntu3 0
3) Way to always repeat a bug:
a. Take a daily Utopic ISO and install in VirtualBox (enable vbox's 3D support)
$ echo FRAMEBUFFER=y | sudo tee /etc/initramfs-
$ sudo update-initramfs -u
4) Expected result:
System have a bit slower but nice looking splash from the early boot.
After some investigation I think I may found the culprit for this breakage...
Lookin at the plymouth's log first thing that stands out is:
That one will fail as we don't have a proper kms support, so plymouth goes on trying other renderes:
And the thing that stands out here is "(terminal: none)".
(Not a dev but I bet that somewhere in the codepath he got a Null while trying to figure out what tty he could use.)
Stupid Workaround: Forcefully replace plymouth (0.9.0-0ubuntu3) utopic package with plymouth (0.8.8-0ubuntu17) precise
Please advise how to continue with resolving this issue.