Installation of Ubuntu Studio 16.10 beta1 failed

[Set Hallstrom]

Installation to disk (hardware) failed during process.
I get to do all the steps; it fails after copying the files is done, during the unpacking process.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.8
ProcVersionSignature: Ubuntu 4.4.0-9134.53-lowlatency 4.4.15
Uname: Linux 4.4.0-9134-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CasperVersion: 1.378
Date: Thu Aug 25 14:25:39 2016
InstallCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Ubuntu-Studio 16.10 "Yakkety Yak" - Alpha amd64 (20160824.2)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu QA Website (ubuntuqa)]

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/1616901

[Ross Gammon (rosco2)]

Hi Set,

I have not looked at the attached logs yet, but could you please add a text description of exactly where the installation fails, and what you see when it happens?

We need the steps to reproduce it. With your notes on the ISO tracker, I see that you at least get to the "choose whether to encrypt home" step. But it fails sometime after that.

[Set Hallstrom (sakrecoer)]

I get to do all the steps; it fails after copying the files, during installation/unpacking process.

[Ross Gammon (rosco2)]

Okay. I can see errors in the debug logs relating to internationalisation issues. Di you think this is simlilar to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1611010?

A fix for that one was released 5 hours ago.

[Leonardo Honfi Camilo (lhcamilo)]

This bug also affects regular ubuntu 16.10. Downloaded and image yesterday and today (currently daily). Both seem to crash at the installation process.

The second time I followed the verbose output and it kept complaining about something not being a numerical value in * . Can't recall correctly.

[Ross Gammon (rosco2)]

OK - confirmed that it seems the same as the other bug, and confirmed that if Set sets a different keyboard layout, the install goes fine. Will mark this as aduplicate.