At one point I found that I had mistakenly set Plymouth to use the text splash rather than a graphic one resulting in not seeing/noticing Plymouth during boot. Switching back to a graphic one, ubuntu-logo, I was able to see the screen.
I did my troubleshooting by breaking the boot process and working at the (initramfs) shell prompt. (see here https://wiki.ubuntu.com/DebuggingKernelBoot) At the grub menu: 1. Press 'e' to edit the boot commands. 2. At the end of the line starting with linux: a. Remove "quiet" b. Add "break=modules" 3. Press Ctrl-x to boot. - It will drop you into (initramfs) immediately after the scripts in "/scripts/init-top/" are run. - If plymouth is running you will see the splash. You can blindly type "plymouth --hide-splash<enter>" to see (initramfs) Confirm that plymouthd fails if run with --attach-to-session 4. (initramfs) /sbin/plymouthd --mode=boot --attach-to-session --pid-file=/dev/.initramfs/plymouth.pid 5. (initramfs) ps |grep `cat /dev/.initramfs/plymouth.pid` - shows that plymouthd is not running despite the presence of /dev/.initramfs/plymouth.pid Show that plymouthd runs without --attach-to-session 6. (initramfs) rm /dev/.initramfs/plymouth.pid 7. (initramfs) /sbin/plymouthd --mode=boot --pid-file=/dev/.initramfs/plymouth.pid 8. (initramfs) ps |grep `cat /dev/.initramfs/plymouth.pid` - plymouthd should be running Test plymouth splash screen and continue boot process: 9. (initramfs) plymouth --show-splash && exit - Should see plymouth splash screen and boot process should continue -- Plythouth doesn't start with --attach-to-session https://bugs.launchpad.net/bugs/502494 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
