Instillation crashes mid instillation upon pressing continue of account details setup,

Bug #1008255 reported by josiah lloyd
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Low
Harald Sitter
Precise
Fix Released
Low
Stéphane Graber

Bug Description

[rational]
Crashes the installer if the user presses continue.

[test case]
1) Get a Kubuntu desktop image
2) Install and when reaching the account details setup, press continue

2) shouldn't crash the installer anymore

[regression potential]
Fix has been in quantal for a while and fix is obvious. There's only one path leading to that specific bit of code and that bit was guaranteed to always crash, so it really can't get any worse.

happens anytime tried installing, Even on multiple computers and multiple instilation disks, Unable to install Kubuntu, Has Wiped windows partitions

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.16
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu5
Architecture: i386
CasperVersion: 1.315
Date: Sun Jun 3 15:15:14 2012
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --
LiveMediaBuild: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
josiah lloyd (josiahlloyd) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

It looks like the crash happens here:

Jun 3 22:01:10 kubuntu ubiquity[3130]: log-output -t ubiquity setxkbmap -model pc105 -layout us -option
Jun 3 22:01:10 kubuntu ubiquity[3130]: debconffilter_done: ubi-console-setup (current: ubi-console-setup)
Jun 3 22:01:10 kubuntu ubiquity[3130]: Step_before = page
Jun 3 22:01:10 kubuntu ubiquity[3130]: switched to page Form
Jun 3 22:07:52 kubuntu ubiquity[3130]: debconffilter_done: ubiquity.components.install (current: ubi-usersetup)
Jun 3 22:07:59 kubuntu ubiquity[3130]: Exception in KDE frontend (invoking crash handler):
Jun 3 22:07:59 kubuntu ubiquity[3130]: Traceback (most recent call last):
Jun 3 22:07:59 kubuntu ubiquity[3130]: File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 957, in on_next_clicked
Jun 3 22:07:59 kubuntu ubiquity[3130]: self.dbfilter.ok_handler()
Jun 3 22:07:59 kubuntu ubiquity[3130]: File "/usr/lib/ubiquity/plugins/ubi-usersetup.py", line 806, in ok_handler
Jun 3 22:07:59 kubuntu ubiquity[3130]: self.ui.hostname_error(make_error_string(self.controller, errors))
Jun 3 22:07:59 kubuntu ubiquity[3130]: AttributeError: 'Page' object has no attribute 'controller'
Jun 3 22:07:59 kubuntu ubiquity[3130]:

tags: added: kubuntu
Revision history for this message
Harald Sitter (apachelogger) wrote :

What is the hostname you enter when installing?

Seems that it fails compliance validation and then triggers the crash.

Changed in ubiquity (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Rienk de Vries (rienk-w200) wrote :

Thanks Harald !

Your remark triggered the solution for me. I had the same issue when installing, the errors in lines #957 and #806.
First this happened when trying to install a 32 bit Kubuntu 12.04 from a USB stick, and today again when trying to install a _x64 Kubuntu 12.04 from a cd. (at first I thought I had a corrupted image or download)

I guess the User Menu does not like spaces. At first, when filling in my full name (Rienk <space> de <space> Vries), and also a computername containing a space, the installer will crash. I assume because the installer sets the hostname by taking whatever one puts in the computer name field, and when there is a space there, one will wind up with an invalid hostname.

Right now Kubuntu is installing, after having filled in those textboxes without using any spaces.

Cheers,
Rienk

Revision history for this message
Harald Sitter (apachelogger) wrote :

Ah, sensible enough. I have a fix and will try to get it deployed as soon as possible. There is just a simple coding error that is triggered when the hostname fails validation (which it would do in case of spaces as a hostname with spaces is not allowed on Linux).

Thanks for the information.

Changed in ubiquity (Ubuntu):
assignee: nobody → Harald Sitter (apachelogger)
status: Incomplete → In Progress
Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu):
status: In Progress → Fix Committed
Changed in ubiquity (Ubuntu Precise):
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Colin Watson (cjwatson)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.11.7

---------------
ubiquity (2.11.7) quantal-proposed; urgency=low

  [ Colin Watson ]
  * Remove hardcoded paths to xfsettingsd and various accessibility tools.
  * Automatic update of included source packages: clock-setup 0.112ubuntu1,
    debian-installer-utils 1.91ubuntu1, flash-kernel 3.0~rc.4ubuntu4,
    partman-base 156ubuntu1, partman-basicfilesystems 74ubuntu1,
    partman-btrfs 9ubuntu1, partman-ext3 70ubuntu1, preseed 1.51ubuntu1.

  [ Harald Sitter ]
  * Fix bogus attribute access in usersetup plugin leading to crashes with
    the KDE frontend (LP: #1008255)

  [ Oliver Grawert ]
  * adjust arm bootloader installation, we have not used this part of ubiquity
    in some years and everything was outdated
 -- Colin Watson <email address hidden> Tue, 26 Jun 2012 11:12:34 +0100

Changed in ubiquity (Ubuntu):
status: Fix Committed → Fix Released
description: updated
Changed in ubiquity (Ubuntu Precise):
status: Triaged → In Progress
assignee: Colin Watson (cjwatson) → Stéphane Graber (stgraber)
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello josiah, or anyone else affected,

Accepted ubiquity into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubiquity/2.10.18 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in ubiquity (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

SRU verification for Precise:
I have verified that the version of ubiquity 2.10.18 in -proposed fixes the issue.

Marking as verification-done

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.10.19

---------------
ubiquity (2.10.19) precise-proposed; urgency=low

  * Automatic update of included source packages: base-installer
    1.122ubuntu7.1, debian-installer-utils 1.88ubuntu2.1, flash-kernel
    2.28ubuntu42.2. (one-time update from precise-proposed) (LP: #1021293)
 -- Stephane Graber <email address hidden> Mon, 30 Jul 2012 10:36:51 -0400

Changed in ubiquity (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.