ubiquity crashed with KeyError in get_autopartition_choice(): None

Bug #1034954 reported by Fabio Marconi
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Dimitri John Ledkov
Quantal
Fix Released
High
Dimitri John Ledkov

Bug Description

Hallo
It crash just after the auto partitioning.
I choose to install alongside windows 8, changed graphically the dimension of the partition, confirmed.
It continue a little bit then the crash occours.
Thanks
Fabio

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.11.19 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CasperVersion: 1.320
Date: Thu Aug 9 15:01:00 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.2mu
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120809.1)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/4220/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--greeter', '--only']
SourcePackage: ubiquity
Title: ubiquity crashed with KeyError in get_autopartition_choice(): None
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Related branches

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
Howard Chan (smartboyhw)
Changed in ubiquity (Ubuntu):
status: New → Confirmed
description: updated
description: updated
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/1034954

tags: added: iso-testing
Revision history for this message
Carla Sella (carla-sella) wrote :

Same happened to me. I was testing this iso: http://cdimage.ubuntu.com/daily-live/20120809.1/quantal-desktop-i386.iso on a virtualbox virtual machine with windows 7 already installed.
When I moved the slider bar that separates the grey sections of the hard drive on witch to install ubuntu and clicked installed now ubiquity crashed.

Revision history for this message
Greg Faith (gregfaith) wrote :

Same here testing Lubuntu quantal desktop i386 installing along side full dsrive install of Lubuntu

Revision history for this message
Dale Beaudoin (twocamels) wrote :

exactly same problem from quantal-desktop-daily Aug 9th/2012

tags: added: ubi-partman
Changed in ubiquity (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I can reproduce this crash with the following steps:
1. Start ubiquity on a system with an existing OS and proceed to the partitioner
2. Select install Ubuntu alongside <OTHER OS> and click on continue
3. On partition size step, click on continue.

Changed in ubiquity (Ubuntu Quantal):
importance: Medium → High
assignee: nobody → Canonical Foundations Team (canonical-foundations)
Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu Quantal):
assignee: Canonical Foundations Team (canonical-foundations) → Dmitrijs Ledkovs (dmitrij.ledkov)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.11.21

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

  * Fix a typpo when checking if crypto option was selected (LP: #1035167).
  * Correct a mistake in refactoring: Do not clear drive selection, just
    before switching to install interface, instead guard by checking for
    correct current page. (LP: #1034954).
  * Mark optional options as invisible by default (LP: #1035514).
 -- Dmitrijs Ledkovs <email address hidden> Mon, 13 Aug 2012 18:08:43 +0100

Changed in ubiquity (Ubuntu Quantal):
status: Triaged → Fix Released
Revision history for this message
Ron Mitchell (rm2892) wrote :

Attempting to do test case uri-001 on an Intel Macbook - (Intel Core Duo - 2.4 Ghz processor, 4 Gig Ram - 250 Gig hard drive). Using Lubuntu AMD 64+Mac Desktop. Build of August 21 2012.

Crash occurred, as described above while executing the step "Allocate drive space". The system already installed was an earlier build of Lubuntu 12.10. Auto paritioning proposed partitioning roughly 50/50 between new system and old. Clicked on "forward" and the system crashed.

Ron Mitchell

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

@rm2892
was it possible to file a new bug?
Can you run ubiquity by starting it from terminal
$ ubiquity --debug
And can you attach /var/log/syslog & /var/log/installer/debug?

Revision history for this message
Ron Mitchell (rm2892) wrote :

Yes I will try that.

Just attempted the same test case again, this time with Fedora 14 installed as my "System YY" - ie Fedora was installed on the full disk.

Ran Lubuntu from the Live Disk (AMD64+Mac) and got to the box headed "Installation Type". This time is recognized that Fedora 14 was installed and didn't even offer the choice of resizing partition. It offered only:

Replace Fedora release 14(Laughlin)) with Lubuntu

Something else

I'll be back to you when I've tried your suggestion.

Ron Mitchell

Revision history for this message
Ron Mitchell (rm2892) wrote :

See bug number 1040996.

Not sure that the attachments will give you the information you need. Following the problem experienced above,
Didn't see Dmitrijs' message until after I'd reformatted the hard drive and installed Fedora 14 so as to have a system sufficiently different from the Lubuntu I was attempting to install.

I probably should have left the previous Lubuntu system alone.
Ron Mitchell

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.