[Bug 665789] Re: plymouth breaks 'read' in initramfs

[Marc MERLIN]

It likely is the same, yes.

Personally, I stopped caring. I got tired of ubuntu shoving things like plymouth down our throats and came to realize that it was my fault for realizing that ubuntu was not the appropriate distribution for my needs anymore.
It's meant for people who don't tinker with their systems, like windows like interactions with their computer, and it's often hard to change its behaviour as well as being a WONTFIX to make the distribution more configurable (like making plymouth optional).

So, I just went back to debian, and I'm happy camper. This doesn't fix
this bug, but it fixes my problem :)

As a side note, things like upstart and plymouth would have gone so much
better if they had been carefully documented instead of being rolled out
"mostly working and very undocumented" like they were. Thankfully at
least upstart now has pretty decent documentation, so better late than
never on that front.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/665789

Title:
  plymouth breaks 'read' in initramfs

Status in “initramfs-tools” package in Ubuntu:
  Invalid
Status in “plymouth” package in Ubuntu:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/665789/+subscriptions