ubiquity:xenial

Last commit made on 2019-02-26
Get this branch:
git clone -b xenial https://git.launchpad.net/ubiquity
Members of Ubuntu Installer Team can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:
xenial
Repository:
lp:ubiquity

Recent commits

93de05f... by Łukasz Zemczak on 2019-02-26

releasing package ubiquity version 2.21.63.10

15e64f0... by Łukasz Zemczak on 2019-02-26

Fix changelog version, add bug number.

402df95... by Łukasz Zemczak on 2019-02-26

Fetch latest user-setup.

f812bb4... by Łukasz Zemczak on 2019-02-26

releasing package ubiquity version 2.21.63.9

1319776... by Adam Conrad on 2018-08-09

Add changelog entry for Dariusz Gadomski's debconf_ui fix.

7405d69... by Dariusz Gadomski on 2018-08-01

Implement missing methods for debconf_ui wizard.

During scenario described in LP: #1749289 a do_reboot call is executed.
This method is not implemented and leads to a system freeze due to
living the configuration in an unfinished state.

b76305d... by Adam Conrad on 2018-08-09

Revert "Fixes a systemd freeze after cancelling debconf UI."

This reverts commit 934344a176b0d4132b5e57c05d9f36272bb8a672.

c509dfa... by Dimitri John Ledkov on 2018-07-31

releasing package ubiquity version 2.21.63.8

1129725... by Dimitri John Ledkov on 2018-07-31

Drop bogus gladep file.

934344a... by Dariusz Gadomski on 2018-07-31

Fixes a systemd freeze after cancelling debconf UI.

When using systemd and performing a oem installation using a debconf_ui
frontend there is a scenario requiring a reboot to continue (more details
at LP: #1749289).

There were several causes for this:
* bin/oem-config-firstboot - 'set -e' had to be removed, because otherwise
    the script was terminated and no exit code check was done so
    code 10 return from oem-config-wrapper was not handled in the if block.
* bin/ubiquity cancelling the installation returned a code 10,
    which then lead to performing a wizard.do_reboot(). This method
    was not implemented for the debconf frontend. This caused an exception
    and exiting the process with code 1.
    Moreover, stealing the terminal control with the termios.TIOCSCTTY
    made doing input/output in oem-config-firstboot impossible, so even
    after falling into if [ $CODE -eq 10 ] block nothing was presented
    to the user.

After fixing the above issues user is presented with 3 options: to try again,
launch a shell or reboot (as originally intended in the code).

LP: #1749289