Comment 3 for bug 727842

So far I can report that this crash only occurred if I chose "install alongside", choosing either "whole disc" or "manual partitioning" worked OK. Now, I'd done a successful "alongside" install earlier beginning with my test drive (sdb) "full" as I explained here:

https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/657397/comments/6

This time I wanted to see if we'd made any changes toward restoring the "Use largest continuous free space" option so I began with this partitioning scheme (note: sda was identical in both tests):

ubuntu@ubuntu:~$ sudo parted -l
Model: ATA WDC WD5000AAKS-0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 32.3kB 43.3GB 43.3GB primary ext3 boot
 2 43.3GB 86.2GB 42.8GB primary ext3
 3 86.2GB 129GB 43.0GB primary ext3
 4 129GB 500GB 371GB extended
18 129GB 151GB 21.8GB logical ext4
14 151GB 172GB 21.1GB logical ext4
15 172GB 193GB 21.1GB logical ext4
16 193GB 215GB 21.4GB logical ext4
17 215GB 236GB 21.4GB logical ext4
13 236GB 258GB 22.0GB logical ext4
12 258GB 280GB 21.6GB logical ext3
11 280GB 301GB 21.7GB logical ext4
10 301GB 323GB 21.8GB logical ext4
 5 323GB 378GB 55.1GB logical ext3
 6 378GB 432GB 53.6GB logical ext3
 7 432GB 487GB 54.9GB logical ext3
 8 487GB 498GB 10.7GB logical ext3
 9 498GB 500GB 2517MB logical linux-swap(v1)

Model: ATA WDC WD800JB-00JJ (scsi)
Disk /dev/sdb: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 32.3kB 38.4GB 38.4GB primary ext3 boot

So the only difference between the two tests was that I began the first with a "full" sdb, and I began the second with about 40GB of free space on sdb.

It appears that the compiz crash has nothing to do with this because I got the same compiz crash error while performing a successful manual partitioning install, but it completed OK w/o ubiquity crashing.

I'll have to repeat at least two more "alongside" installs, or at least run through the installer options with a full sdb and an sdb with free space again to see if that's what reproduces this behavior. So this may take a while.

IMHO this should not be a reason to delay an Alpha 3. I'd hope most testers have the knowledge to work around minor bugs like this.