ubi-console-setup failing on yakkety images

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

On Xubuntu 16.10 amd64, I also have this message. The message complete is : "ubi-console-setup failed with exit code 1. Further information may be found in /var/log/syslog. Do you want to try running this step again before continuing ? If you do not, your installation may fail entirely or may be broken"

How we can have access to /var/log/syslog ?

I've selected "Continue anyway" and it seems to work. The installation continues.

After clicking on "Continue anyway" the installation has continued and now I'm able to boot on Yakkety Yak without significant problems. But, the error message is scaring.

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

attached syslog from xubuntu installer

After quitting the install - got this as well

"[Errno 2] No such file or directory: '/target/lib/modules/4.4.0-21-generic/kernel/drivers/net/ethernet/intel/igbvf/igbvf.ko'"

Also note that once I've closed that message - get the "We're sorry; the installer crashed. After you close this window, we'll allow you to file a bug report ... " warning - which doesn't actually close.

Same problem for the May 8 build at http://cdimage.ubuntu.com/daily-live/current/.

Note that if you 'Continue' then the installer runs, installs and system reboots correctly to a working system.

additional crash on installing

Normally selecting continue on crash allows yakkety to be installed. now when it gets teh configure time zone, i get an additional "Installer Crashed" error. The iso then goes into a live session to try again

From a failed Kubuntu Install.

Screenshot: http://i.imgur.com/7S6K9wB.png

appears fixed now

Yes, seems fixed here with kubuntu daily iso.

So that would be fixed with resolution of this bug?

https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1587555

Based on the recent comments (and the fact that I was unable to reproduce this issue the last time I installed Yakkety), I believe this can be marked Fix Released.