[Bug 1727816] Re: cannot enter encryption password in GUI

[stuartbh]

Steve, et alia:

Your welcome, I am happy to take the time to report bugulance in Ubuntu
so it can be markedly improved. Moreover, I marked this as a security
based bug since it involves an issue with the entrance of a password,
thus one would think it obvious to be impactive to security! I had no
idea if it was because some rouge software was installed or what, just
that it seemed patently dysfunctional on a prima facia basis. I also was
not entirely sure if security based developers were involved with its
code management or not.

The foregoing notwithstanding, I have been using Ubuntu for many years
(ever since RedHat Workstation was withdrawn from marketing) and
appreciate the goodness of Debian coupled with the ease of use Ubuntu
adds (while subtracting the extremism of some of the Debian folks that
make it difficult to install).

I can try to install 17.04 and see what occurs as well as to see if
kernel replacement under 17.10 manages to effectuate different
functionality.

Thank you for looking into it so quickly.


V/R,

Stuart

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

Title:
  cannot enter encryption password in GUI

Status in Ubuntu:
  New
Status in plymouth package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 17.10 Desktop on a Dell XPS 2720, under which VirtualBox 5.2.0 is running.
  Within VirtualBox I installed a 2nd level 17.10 Desktop and checked off encryption during installation (forcing LVM to be used). The install went flawlessly, then I tried to reboot and it asked for the password (in GUI mode) to access the encrypted disk, but when I typed it no asterisks came up and it never accepted my typing.

  However, when I booted in recovery mode (textually) it asked for the
  password in text, I entered it, Ubuntu accepted it, then I hit resume
  boot up and it booted up into the GUI. This bug seems NOT to be
  present in a bare metal environment only when running under VirtualBox
  (I have not tested other virtualization technologies, just VirtualBox
  5.2.0)

  
  Thanks,

  Stuart

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