*** This bug is a duplicate of bug 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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

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

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Xenial:
Status in ubiquity source package in Yakkety:
Status in ubiquity source package in Zesty:
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:

   * When launching "Install Ubuntu" or when present with try or install
  ubuntu screen, one cannot login on tty2-6.

   * This impacts debugging facilities during installation.

   * It appears that getty.target is not required by ubiquity, therefore
  gettys on tty2-6 are not spawned, and no users are allowed to login.

  [Test Case]

   * Boot Ubuntu Desktop CD

   * Select "Install Ubuntu" in the isolinux menu, or the UEFI menu

   * When presented with ubiquity screen, press Ctrl-Alt-F2 to open up

   * Login as user "ubuntu" with no password. If login prompt never
  appears (current behaviour) this bug is still present.

  [Regression Potential]

   * I have not tested this change in the OEM mode yet

  [Potential fix]
   * Add to ubiquity.service [Unit] section

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to