This is well before X comes into play. X only kicks in after plymouth is done.
Might be a plymouth bug but maybe more likely to be something with the kernel framebuffer initialization. Probably best to start analysis from the kernel and work your way up to find the cause. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1051035 Title: MacBookAir3,1 has screen corruption on boot between Grub and Login (no Pylmouth Ubuntu logo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051035/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
