Ubiquity crashes prior to keyboard configuration in 15.04

[Martin Wimpress ]

As best as I can tell, if anything other than a US keyboard layout is selected from the boot menu, ubi-console-setup will crash prior to the keyboard configuration. The dialogue displayed says:

    ubi-console-setup failed with exit code 2. Further information maybe found in /var/log/syslog.

There are the relevant lines from /var/log/syslog:

Jan 7 23:30:39 ubuntu ubiquity: /var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open /etc/default/keyboard
Jan 7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap -layout gb -option
Jan 7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup (current: ubi-console-setup)
Jan 7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: ('ubi-console-setup', 2)

The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If you choose Try Again it is possible to complete the install. If you choose Continue Anyway the installer will progress and eventually crash completely as which point apport was able to harvest the attached logs.

WORKAROUND: After you see the "ubi-console-setup crashed" dialog, open a terminal and do

  sudo rm /etc/default/keyboard
  sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

then click "Continue anyway" in the dialog. This should prevent the crash at the end of installation.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.2
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.347
Date: Wed Jan 7 23:36:41 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150107)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu Foundations Team Bug Bot (crichton)]

Exception during installation:
Jan 7 23:36:01 ubuntu /plugininstall.py: Traceback (most recent call last):
Jan 7 23:36:01 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1765, in <module>
Jan 7 23:36:01 ubuntu /plugininstall.py: install.run()
Jan 7 23:36:01 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 78, in wrapper
Jan 7 23:36:01 ubuntu /plugininstall.py: func(self)
Jan 7 23:36:01 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 204, in run
Jan 7 23:36:01 ubuntu /plugininstall.py: self.configure_plugins()
Jan 7 23:36:01 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 570, in configure_plugins
Jan 7 23:36:01 ubuntu /plugininstall.py: self.run_plugin(plugin)
Jan 7 23:36:01 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 547, in run_plugin
Jan 7 23:36:01 ubuntu /plugininstall.py: "Plugin %s failed with code %s" % (plugin.NAME, ret))
Jan 7 23:36:01 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: Plugin console_setup failed with code 1
Jan 7 23:36:01 ubuntu /plugininstall.py:

[Launchpad Janitor (janitor)]

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

[Alistair Buxton (a-j-buxton)]

Reproduced with Xubuntu daily. It only seems to happen if you choose "install now" rather than "try xubuntu".

[Brian Murray (brian-murray)]

There's also this:

Jan 7 23:36:01 ubuntu ubiquity: setupcon: None of /etc/default/keyboard nor /root/.console-setup exists.

[Anthony Wong (anthonywong)]

Also happens on Ubuntu Kylin daily.

[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/1408495

[Elfy (elfy)]

confirm the comment in post #4 with xubuntu

If I 'try again' install appears to then proceed correctly

[Martin Pitt (pitti)]

Indeed this looks strange on the live CD:

c------------ 1 root root 0, 0 Jan 14 18:21 keyboard
c------------ 1 root root 0, 0 Jan 14 18:21 keyboard.pre-ubiquity

An inaccessible character device is certainly not intended here?

[Martin Pitt (pitti)]

Confirmed that the broken /etc/default/keyboard does NOT happen when starting the live system, but happens when ubiquity is about to configure keyboard.

[Martin Pitt (pitti)]

I added a workaround to the description to prevent the complete failure at the end.

[jerrylamos (jerrylamos)]

Permissions on /etc/default/keyboard were:
c------------

while on the default were
-rw-r--r--r

So workaround copying resulted in
-rw-r--r--
so install completed.

BTW, this is US so this is what keyboard looked like:

ubuntu@ubuntu:~$ cat /etc/default/keyboard
# Check /usr/share/doc/keyboard-configuration/README.Debian for
# documentation on what to do after having modified this file.

# The following variables describe your keyboard and can have the same
# values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
# in /etc/X11/xorg.conf.

XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS=""

# If you don't want to use the XKB layout on the console, you can
# specify an alternative keymap. Make sure it will be accessible
# before /usr is mounted.
# KMAP=/etc/console-setup/defkeymap.kmap.gz

which went on to code 2 and fail.

Your workaround worked.

Maybe the bug is the permissions
-c----------instead of
-rw-r--r--

Having said that, I didn't copy the permissions, could even have been
c----------

Maybe all I had to do was change permissions?

[Jack Bowling (jbinpg)]

On 2015-01-14 04:47 PM, jerrylamos wrote:
> Permissions on /etc/default/keyboard were:
> c------------
>
> while on the default were
> -rw-r--r--r
>
> So workaround copying resulted in
> -rw-r--r--
> so install completed.

<snip>

Confirmation of successful install of Vivid using Martin's keyboard
workaround. - Jack

[Mathieu Trudel-Lapierre (cyphermox)]

It looks like any moving of a file which comes from the read-only underlying filesystem. It doesn't behave the same when one deletes a file instead of moving.

It seems like it's probably a bug in overlayfs, so I'm adding a task for linux so the kernel team can take a look.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1408495

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Mathieu Trudel-Lapierre (cyphermox)]

ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2119 F.... pulseaudio
CasperVersion: 1.347
DistroRelease: Ubuntu 15.04
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150116)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: ubiquity
PackageArchitecture: amd64
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.18.0-9-generic N/A
 linux-backports-modules-3.18.0-9-generic N/A
 linux-firmware 1.140
RfKill:

Tags: vivid vivid ubiquity-2.21.4 ubuntu
Uname: Linux 3.18.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.7.5-20140531_171129-lamiak
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-utopic
dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20140531_171129-lamiak:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-utopic
dmi.sys.vendor: QEMU

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

apport information

[Mathieu Trudel-Lapierre (cyphermox)]

This seems like a duplicate of bug 1410480.

[jerrylamos (jerrylamos)]

Problem is the file permissions for /etc/default/keyboard on the vivid .iso are

ls -l /etc/default/keyboard

c---------

Won't work. No way ubiquity can use the file.

On previous vivid, tahr, etc. file permissions are:

-rw-r--r--

works fine.

[jerrylamos (jerrylamos)]

bug #1410480, overlayfs v1: renaming existing file uses chardev whiteout (should be symlink)

seems to have nothing at all to do with ubiquity install failures which is this bug here.

I've verified tahr 14.04 booted /etc/default/keyboard has file permissions

-rw-r--r--

while later 15.10 has file permissions

c---------

no wonder ubiquity can't even access it.

which is nonsense. What's that got to do with bug #1410480 about chardev whiteout?