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

[Andy Whitcroft]

Debugging the issue some I can say that (for me) the issue seems to be
when the server sends the answer response to the client.  It is running
in "ply_boot_connection_send_answer" when it gets a SIGPIPE in the
middle, implying the client has gone:

  ply_boot_connection_send_answer()
  {
  [...]
      if (!ply_write (connection->fd,
                      PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ANSWER,
                      strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ANSWER)) ||
          !ply_write_uint32 (connection->fd,
                             size) ||
          !ply_write (connection->fd,
                      answer, size))
          ply_trace ("could not finish writing answer: %m");
  [...]

Now the client does wait for the server to respond before exiting
blocking until the user hits return, and it reports a failure was sent.
This however could come out for a lost connection also.  The fact that
it does wait hints that the response triggers the closure.  Need more
debug as to what if anything is received.

-- 
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