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

Bug #1632151 reported by Dimitri John Ledkov
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
New
Undecided
Unassigned
Yakkety
New
Undecided
Unassigned
Zesty
New
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

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

 * 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
  <email address hidden>
  <email address hidden>
  Requires=getty.target

Related branches

Revision history for this message
Martin Pitt (pitti) wrote :

This is very similar to bug 1567194, and that one was not easy to fix. My gut feeling is that this applies to tty1 as well and it is a duplicate.

Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Dimitri, or anyone else affected,

Accepted ubiquity into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/18.04.5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in ubiquity (Ubuntu Bionic):
status: New → Fix Committed
tags: added: verification-needed verification-needed-bionic
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Tue, 10 Apr 2018 11:17:42 -0400

Changed in ubiquity (Ubuntu Bionic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.