ubiquity crashed with KeyError in layout_reverse(): 'it'

Bug #1027620 reported by Fabio Marconi
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Colin Watson
Quantal
Fix Released
High
Colin Watson

Bug Description

TEST CASE:
1. Start ubiquity and proceed to the keyboard layout page
2. Click on 'Detect Keyboard Layout'
3. Answer to the questions in the detection dialog

ACTUAL RESULT:
At the end the following crash occurs:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/plugin.py", line 48, in wrapper
    return target(self, *args, **kwargs)
  File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 80, in calculate_result
    layout = keyboard_names.layout_reverse(l, keymap[0])
  File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 152, in layout_reverse
    return kn.layout_reverse(lang, value)
  File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 100, in layout_reverse
    return self._layout_rev[value]
KeyError: 'it'

Hallo
Testing today build 20120722 amd64 desktop.
I select English as language and it propose English as layout for keyboard.
I click on -Detect keyboard layout- button and followed the instructions, when the operation was ended it crash.
Thanks
Fabio

ProblemType: CrashDistroRelease: Ubuntu 12.10
Package: ubiquity 2.11.17
ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7
Uname: Linux 3.5.0-5-generic x86_64
ApportVersion: 2.4-0ubuntu4
Architecture: amd64
CasperVersion: 1.320
Date: Sun Jul 22 15:18:42 2012
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
InterpreterPath: /usr/bin/python3.2muLiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/21588/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']SourcePackage: ubiquity
Title: ubiquity crashed with KeyError in layout_reverse(): 'it'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

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

tags: added: iso-testing
description: updated
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Confirmed with 20120722 and a 'us' layout

Changed in ubiquity (Ubuntu Quantal):
assignee: nobody → Canonical Foundations Team (canonical-foundations)
status: New → Confirmed
importance: Medium → High
description: updated
Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu Quantal):
assignee: Canonical Foundations Team (canonical-foundations) → Colin Watson (cjwatson)
Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu Quantal):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.11.18

---------------
ubiquity (2.11.18) quantal; urgency=low

  * Don't bother keeping track of keyboard model names and identifiers, as
    nothing in ubiquity uses them right now.
  * Fix reversed uses of methods mapping between keyboard layout/variant IDs
    and human-readable names, and improve method naming and documentation to
    make this mistake less likely in future (LP: #1027207, #1027620).
  * Automatic update of included source packages: debian-installer-utils
    1.91ubuntu3, flash-kernel 3.0~rc.4ubuntu9, netcfg 1.68ubuntu15.
 -- Colin Watson <email address hidden> Mon, 23 Jul 2012 11:02:13 +0100

Changed in ubiquity (Ubuntu Quantal):
status: Fix Committed → Fix Released
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.