Installing lubuntu 16.10 onto a HTPC build. Installer crashed during install.

Bug #1669972 reported by Andrew Robinson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub-installer (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Downloading updates during install of 16.10 from image on USB.

Gigabyte B150-GSM mITX board BIOS F20 - i3 6100 - 8Gb generic 2133 RAM - SSD that was going spare.

I'll try skipping that step and updating manually after.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.14
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CasperVersion: 1.379
Date: Sat Mar 4 20:30:25 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcEnviron:
 LANGUAGE=en_NZ.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_NZ.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Andrew Robinson (aeon-lakes) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in grub-installer (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrew Robinson (aeon-lakes) wrote :

Did the install without downloading updates; rebooted; then apt-get update; apt-get install.

I now have a working Lubuntu install. And very snappy it is too. :-)

apt-ghetto (apt-ghetto)
summary: - Installing lubuntu onto a HTPC build. Installer crashed during install.
+ Installing lubuntu 16.10 onto a HTPC build. Installer crashed during
+ install.
Revision history for this message
apt-ghetto (apt-ghetto) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1639374, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.