[Bug 563916]

[Gitlab-migration]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/plymouth/plymouth/issues/23.

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

Title:
  [details.so] No prompt for [S]kip or [M]anual recovery on server boot
  (or without "splash")

Status in Plymouth:
  Unknown
Status in Release Notes for Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in plymouth source package in Lucid:
  Fix Released
Status in plymouth source package in Maverick:
  Fix Released

Bug description:
  Stable release update justification:

  Impact: Mount failures of any kind on server installations (i.e. with the plymouth 'details' plugin) hang the boot process rather than producing a visible prompt.  This is serious - you have no idea what's going on and no obvious way to fix it.
  Development branch: plymouth 0.8.2-2ubuntu4 implemented the display_message method in the details plugin, fixing this.
  Patch: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/563916/+attachment/1742442/+files/plymouth_0.8.2-2ubuntu2.2.debdiff
  TEST CASE: Install an Ubuntu 10.04 server.  Edit /etc/fstab to cause a mount to fail (a good way is to mount a nonexistent device, or you could deliberately break a filesystem in some way).  When you next boot, you should see messages from mountall rather than silent inactivity.
  Regression potential: Obviously test that normal boots still work.  Desktop installations shouldn't have been changed by this, but I think it would be a good idea to double-check that.

  Original report follows:

  Binary package hint: mountall

  On 10.04 servers, as of beta2, when for any reason mountall fails to
  mount some partition (for example because you created a snapshot on a
  LVM volume as in bug 563902), the boot will hang without a prompt for
  [s]kipping or [m]anually fix the situation. However pressing M or S
  still works...

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