ubiquity crashed with KeyError in plugin_on_next_clicked(): 'resize'

Oh, shortly prior to this I got a warning that Compiz had crashed but my system didn't have enough memory to report it. Both errors show up in /var/crash:

Both errors show up here:

ubuntu@ubuntu:~$ ls /var/crash
_usr_bin_compiz.999.crash _usr_lib_ubiquity_bin_ubiquity.0.crash

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.

OK, reproducing this was fairly easy. I started with this arrangement on sdb (my testing drive):

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
 2 38.4GB 80.0GB 41.7GB extended
 5 38.4GB 77.4GB 39.0GB logical ext4
 6 77.4GB 80.0GB 2665MB logical linux-swap(v1)

So once again the whole disc was occupied. I booted choosing "Try Ubuntu" to get to the live desktop, then chose to install. I then ran through the "alongside" install process without error and then hit "Back" before the process completed just to expedite testing. After quitting the process I used Gparted to delete sdb5 and tried to use the "alongside" option again. At that point I got the same error that resulted in this bug report.

Next I wanted to see what happened if I chose "Install Ubuntu" rather than "Try Ubuntu" so I rebooted and upon trying "install alongside" the "spinning wheel" would just spin forever instead of progressing. After several minutes I just pressed alt>sysreq>k, then chose to boot classic w/o effects and used Gparted to create a blank ext2 partition where the unallocated space had been. Then upon restarting and choosing "Install Ubuntu" the "alongside" option proceeded as it should. But once again I quit the install before it completed just to expedite reporting on this bug.

I wonder if I should try this with sda disconnected but that seems rather pointless. I'll wait for Evan Dandrea or someone that really knows ubiquity to request more info ;^)

I'd almost bet that Evan Dandrea provided the answer to this in bug 652852 comment #30:

"This is back in Natty, but the UI isn't complete."

Perhaps this deserves a mention in the Natty Alpha 3 release notes?

If so I should clarify that this only occurs if unallocated space is available and the "install alongside other operating systems" option is selected. If the install process is being run after selecting the "Install Ubuntu" option from the boot menu clicking on "install alongside" results in an infinitely "spinning wheel". If the install process is started from the live desktop clicking on "install alongside" results in the apport crash report I used to report this.

This bug was fixed in the package ubiquity - 2.5.23

---------------
ubiquity (2.5.23) natty; urgency=low

  [ Evan Dandrea ]
  * Ensure we always have an automatic partitioning option selected.
  * Merge in latest change to apt-clone from Michael Vogt:
    - Current apt_pkg API methods.
    - Better command line argument parsing.
    - Set DPkg::Chroot-Directory (LP 727758).
  * Do not attempt to proceed to a second page with the biggest_free
    option (LP: #727842, LP: #652852). This will change once we have an
    interface for the biggest_free option.
  * If the partition table is full and a copy of Windows exists, replace the
    resize option with a copy of wubi.exe to the Windows startup folder,
    followed by a reboot.
  * Temporary fix for translations with carriage returns (LP: #730498).
  * Update translations from Launchpad.
  * Automatic update of included source packages: console-setup
    1.57ubuntu10.

  [ Colin Watson ]
  * Set Dir::Media::MountPath as well as Acquire::cdrom::mount (in line with
    base-installer), and pass all the options set by configure_apt to
    python-apt as well so that attempts to install packages from python-apt
    will behave consistently (LP: #727783).

  [ Julien Lavergne ]
  * bin/ubiquity-dm:
   - Wait lxsession before launching the panel, to have theming support.
     (LP: #684802)
  * src/panel/panel.c
   - Load lxpanel background for the panel when it's available.
 -- Evan Dandrea <email address hidden> Mon, 07 Mar 2011 09:16:26 +0000

continuos crash install (via usb or dvd)

no solution yet

New download, new ISO file, OLD CRASH yet.

@ Carlos,

You've yet to include what iso you're using.

What version and flavor of Ubuntu are you trying to install?

ISO ? daily (yesterday and now today)

Quantal
Relase- Beta 1, same error
Beta 2 -Idem

-(

Hardware - Dell Inspiron (ultrabook)

+ Info

installation via USB

I think you should file a new bug report. I'd guess that you're getting an automated ubiquity crash report so just don't accept it being a duplicate and you should be able to produce a new bug report that will collect crash info.

That is, you should get a list of possible duplicates but there should also be an option to say something like, "No, I need to file a new bug". Then maybe mention that it may be a regression of bug 727842.

I hope that helps.

I reported new bug as you pointed.

thank you Erick