plymouth 0.9.0 can not use framebuffer for terminal: none

[nadrimajstor]

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)
Release: 14.10

2) apt-cache policy plymouth
plymouth:
  Installed: 0.9.0-0ubuntu3
  Candidate: 0.9.0-0ubuntu3
  Version table:
 *** 0.9.0-0ubuntu3 0
        500 http://rs.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
        100 /var/lib/dpkg/status

3) Way to always repeat a bug:
  a. Take a daily Utopic ISO and install in VirtualBox (enable vbox's 3D support)
  b. Execute:
    $ echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
    $ sudo update-initramfs -u
  c. Reboot

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:

[ply-device-manager.c:641] create_seat_for_terminal_and_renderer_type:creating seat for /dev/dri/card0 (renderer type: 1) (terminal: /dev/tty7)

That one will fail as we don't have a proper kms support, so plymouth goes on trying other renderes:

[ply-device-manager.c:641] create_seat_for_terminal_and_renderer_type:creating seat for /dev/fb0 (renderer type: 2) (terminal: none)

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.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Wimpress  (flexiondotorg)]

This following bug reports look relevant.

  * https://bugs.freedesktop.org/show_bug.cgi?id=80553
  * https://bugs.gentoo.org/show_bug.cgi?id=517572