*** This bug is a duplicate of bug 1567194 ***
    https://bugs.launchpad.net/bugs/1567194

This bug was fixed in the package ubiquity - 18.04.5

---------------
ubiquity (18.04.5) bionic; urgency=medium

  [ Steve Langasek ]
  * Don't block plymouth-quit-wait on the ubiquity greeter; we want ttys to
    be able to start in parallel for debuggability of ubiquity.  Blocking
    plymouth-quit is sufficient to ensure ordering.
  * scripts/start-ubiquity-dm: start on vt1 now instead of vt7, consistent
    with grub, plymouth, and gdm in 18.04.  Tested on Ubuntu Desktop with
    both "Try" and "Install" options. (LP: #1632151)

  [ Heber Parruci ]
  * autopilot: Update tests to match new UI for Updates and software page.

  [ Mike Gabriel ]
  * debian/control: Drop gir1.2-appindicator3-0.1. A11y support
    is not using AppIndicator anymore (LP: #1760701)

  [ Mathieu Trudel-Lapierre ]
  * Automatic update of included source packages: partman-crypto
    86ubuntu2, partman-lvm 123.

 -- Mathieu Trudel-Lapierre <cypher...@ubuntu.com>  Tue, 10 Apr 2018
11:17:42 -0400

** Changed in: ubiquity (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

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

Title:
  When ubiquity is in maybe-ubiquity or only-ubiquity, there is no way
  to access tty2-6

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to