Precise ubiquity not offering resize option

[Erick Brunzell]

I'm testing the Ubuntu i386 20120325 image and I decided to review all installation options, naturally using Oneiric behavior as a comparison, and I'm a bit surprised to see that I'm NOT offered an auto-resize option with a fairly simple dual-boot. Screenshot attached, and more testing to follow.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.2 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CasperVersion: 1.312
Date: Sun Mar 25 14:15:50 2012
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120325)
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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

[Jane Atkinson (irihapeti)]

This isn't the only way in which the side-by-side (dual boot) option allows no user input. One doesn't get to choose drives, either, if one has more than one. See bug 964331. I don't mind saying that it scared the **** out of me when that happened.

[Launchpad Janitor (janitor)]

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

[Erick Brunzell (lbsolost)]

I'm marking this invalid. Quite simply I was tired, and I've been testing alternate images and netboot mini.iso's along with live images lately and I got a bit confused :^(

After seeing Jane's warning I decided to try some "safer" hardware to do some retesting and I've refreshed my memory using the "new" ubiquity and I think we're OK. I will say however that the debian-installer is easier and less scary to use.

I'll comment at bug 964331 separately. Sorry for any confusion I may have created.