Comment 23 for bug 1082742

Just for the sake of it, I got this problem and it had nothing to do with plymouth. It was caused by a 13.04 update which removed /etc/X11/xorg.conf.d along with exynos5.conf. I just had to do this:
- get into ChromeOS shell (Ctrl-Alt-[←])
- log in as chronos, then sudo su -
- make some directory (mkdir /tmp/x) and mount my SDcard root partition on it (mount /dev/mmcbkl1p7 /tmp/x)
- chroot to it (chroot /tmp/x)
- recreate the xorg.conf.d directory: mkdir /etc/X11/xorg.conf.d
- recreate the exynos5.conf file:
cat > /etc/X11/xorg.conf.d/exynos5.conf <<EOZ
Section "Device"
Identifier "Mali FBDEV"
Driver "armsoc"
Option "fbdev" "/dev/fb0"
Option "Fimg2DExa" "false"
Option "DRI2" "true"
Option "DRI2_PAGE_FLIP" "false"
Option "DRI2_WAIT_VSYNC" "true"
# Option "Fimg2DExaSolid" "false"
# Option "Fimg2DExaCopy" "false"
# Option "Fimg2DExaComposite" "false"
Option "SWcursorLCD" "false"
EndSection

Section "Screen"
Identifier "DefaultScreen"
Device "Mali FBDEV"
DefaultDepth 24
EndSection

EOZ

- exit from the chroot: exit
- umount the chroot: umount /tmp/x
- reboot to Ubuntu