Installer crashed during installation

Bug #1587555 reported by Kev Bowring
140
This bug affects 16 people
Affects Status Importance Assigned to Milestone
clock-setup (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
ubiquity (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre

Bug Description

Not sure what went on.

Installing in qemu/kvm.

Had the ubi-console error previously reported - continued as before - crash this time.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CasperVersion: 1.376
Date: Tue May 31 17:15:29 2016
InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160531)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Kev Bowring (flocculant) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1587555

tags: added: iso-testing
Revision history for this message
sudodus (nio-wiklund) wrote :

I can confirm this bug. It affects me, when I try to install Xubuntu Yakkety 32-bit manually, selecting 'Something else' at the partitioning window.

The crash seemed to happen during or near configuration of time zone.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Kev Bowring (flocculant) wrote :

tried it a couple of times - didn't see it here anywhere close to tz config

Revision history for this message
Christopher Patrick (cpatrick08) wrote :

I have this problem with Ubuntu Mate Daily Live build 20160606

Revision history for this message
David Pearson (akxwi-dave) wrote :

I also have this on 64 and 32 bit versions of Xubuntu 16.10 daily.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Found what the issue is. Given that it's the most obvious (and critical) crash in syslog let's make use of this bug report to fix it; and I'll report a new one for the console-setup issue.

affects: ubiquity (Ubuntu) → clock-setup (Ubuntu)
Changed in clock-setup (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
importance: Undecided → High
status: Confirmed → In Progress
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Turns out this is breaking in ubiquity because we don't get initscripts installed on the rootfs (since procps now depends on init-system-helpers instead).

For d-i installs this doesn't exactly break, but it's still a good idea to check for the file to exist before we try to modify it. Looks like in the d-i case, some other script may be creating an empty file before clock-setup runs.

On ubiquity, no such empty file is created, and we use a "copy" of 10clock-setup; so there needs to be an update to both packages.

Changed in ubiquity (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package clock-setup - 0.126ubuntu2

---------------
clock-setup (0.126ubuntu2) yakkety; urgency=medium

  * finish-install.d/10clock-setup: guard against rcS not existing on disk
    when we try to update it. (LP: #1587555)

 -- Mathieu Trudel-Lapierre <email address hidden> Wed, 08 Jun 2016 13:42:48 -0400

Changed in clock-setup (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Ivan D. Sanders (vandelsand) wrote :

So this is a work around:

Install Ubuntu Desktop 16.04.

Code:

# sudo do-release-upgrade -d

That will upgrade you to 16.10. This does not fix the bug, but it works to get 16.10.

Revision history for this message
Gene Soo (genesoo77072) wrote :

Tried KDE 16.04 LTS install and command above.
No Joy.

Command Results follow:
gene@U1610KDEDLYX:~$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
No new release found
gene@U1610KDEDLYX:~$ uname -r
4.4.0-21-generic
gene@U1610KDEDLYX:~$ uname -a
Linux U1610KDEDLYX 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Ivan D. Sanders (vandelsand) wrote :

Worked for me with regular Ubuntu (Unity).

username@machine_name:~$ uname -r
4.4.0-23-generic
username@machine_name:~$ uname -a
Linux machine_name 4.4.0-23-generic #41-Ubuntu SMP Mon May 16 23:04:25 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
username@machine_name:~$

Revision history for this message
Ivan D. Sanders (vandelsand) wrote :
Revision history for this message
Gene Soo (genesoo77072) wrote :

I suspect there is something missing like needing to add Development Repos to current GA Repos. I don't know what these are so if you have that info, that would make the Workaround successful.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 16.10.2

---------------
ubiquity (16.10.2) yakkety; urgency=medium

  * scripts/clock-setup-apply: guard against missing rcS file on the rootfs.
    (LP: #1587555)
  * autopilot/ubiquity_autopilot_tests/*: remove unused imports for pyflakes.
  * tests/pyflakes.exclude: update exclusions to remove autopilot entries
    just fixed, and add the full module path to the others.
  * Automatic update of included source packages: apt-setup
    1:0.104ubuntu5, base-installer 1.158ubuntu3, clock-setup
    0.126ubuntu2, console-setup 1.142ubuntu4, netcfg 1.135ubuntu6,
    partconf 1.50, partman-auto-lvm 59ubuntu1, partman-ext3 86ubuntu1,
    partman-lvm 113.

 -- Mathieu Trudel-Lapierre <email address hidden> Thu, 09 Jun 2016 10:43:50 -0400

Changed in ubiquity (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
sudodus (nio-wiklund) wrote :

The bug-fixes in and around Ubiquity have trickled down to the iso files now, and it works again to install Lubuntu from a desktop iso file.

Thanks for squashing this nasty bug :-)

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.