Public bug reported:

Binary package hint: plymouth

In maverick plymouth 0.8.2-2ubuntu5.

I'll skip the amount of grief plymouth has cost me in multiple places,
it has been echoed by enough other people in bugs and blogs (long story
short, I never upgraded to lucid because of plymouth). I eventually went
to maverick and it's a tiny bit better, but as far as encryption and
initrd goes, it of course grabs the console away and stops script that
read input from working.

My encryption script did a simple 
read PASSWORD
feed password to cryptsetup

read never works because of plymouth.
I edited /usr/share/initramfs-tools/scripts/init-top/plymouth
and commented out
#printf '\033[?25l' > /dev/tty7 
#/sbin/plymouthd --mode=boot --attach-to-session 
--pid-file=/dev/.initramfs/plymouth.pid
#/bin/plymouth show-splash 

I have no idea why this is there, what purpose it serves, but now that I
removed them, I can read the encryption password from the command line
again and boot properly.

Please consider removing this if it's not absolutely necessary, and more
generally when you design system enhancements, remember those who
actually need boot messages and console access to work reliably and
couldn't care less about splash screens and eye candy that removes
access to the system when it boots.

Thanks.

** Affects: initramfs-tools (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: plymouth (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: i386 maverick

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
       Status: New

** Tags added: i386 maverick

-- 
plymouth breaks 'read' in initramfs
https://bugs.launchpad.net/bugs/665789
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

Reply via email to