[Bug 1362333] Re: After reboot of Ubuntu installation, password for LVM encryption is not accepted

[Andy Whitcroft]

Ok fuller debug indeed confirms that the client reads the type of the
message (ANSWER), and then attempts to read the size of the said answer.
That is not yet present, so it gets EAGAIN because this is a NONBLOCKing
socket.  This is does not like and aborts the connection in failure,
leading the server to report connection loss.

In short we are hitting normal behaviour, multiple writes and multiple
reads can occur in any order.  The correct fix is for the consumer to
buffer the partial data, and to continue when the full data is
available, this is non-trivial because the data we are trying to buffer
as different form depending on type.  Ideally we would start each
message with a length, such that we could buffer it before introspecting
it.

For now we can also avoid this by ensuring the server write is performed
as a single operation.  As long as we are below the buffering limits we
will guarentee to only see the initial command type byte if the answer
is also present.

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

Title:
  After reboot of Ubuntu installation,  password for LVM encryption is
  not accepted

Status in “plymouth” package in Ubuntu:
  Confirmed
Status in “ubiquity” package in Ubuntu:
  Confirmed

Bug description:
  I have tried several times to perform an installation of Gnome Ubuntu x64 (Utopic Beta 1  26/08/2014 ISO), after reboot, you are asked to insert your passphrase, but it is not accepted it keeps on displaying that the passphrase is not correct even though I am inserting the correct one, and so booting of Ubuntu Gnome isn't possible after install.
  I have performed the installation on a Virtualbox VM and I still have it if you need something else.
  I am attaching the /var/log directory of the /dev/sda5 LVM volume that I could manage to unencrypt, when unencrypting it manually the password was accepted and /dev/sda5 mounted, so I am sure the password I was trying to insert was the correct one.
  This is the test I was carrying out when I detected this bug:
  http://iso.qa.ubuntu.com/qatracker/testcases/1451/info.
  This is the ISO I tested on: http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/20140826/utopic-desktop-amd64.iso.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1362333/+subscriptions