ubiquity gtk frontend crashes when configuring Ubuntu Mint to install using preexistent home cryptographed (and mounted) partition

[paranaense]

Binary package hint: ubiquity

When installing Ubuntu Mint, I had a crash during the partitioning process.
I have sda1 with 2GB for swap. First problem. I can't inform the partitionner that I want that to be encripted.
Then I have sda2 with 20 GB that will be formated so the shitty OpenSuse leaves and Linux Mint comes.
Then I have sda3 with 256 GB of /home encrypted partition that I DON'T want to be formated.
The installer isn't intuitive, since it doesn't ask me to give the pass to mount the partition, so it can search the filesystem type and suggest me something like keeping or formating it. I had to quit installation, mount the partition, and rebegin the instalation so the partitioner would recognize the partition.
Then the other non intuitive issue came. Both sda3 and the device mapper with the same unencryped sda3 appered in the list. I didn't know exatly which one to set as HOME without formating. I chose the "mapper" one and as soon as I clicked on the EDIT button, it crashed.
Here's the information provided by the instalation program:
Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 2105, in on_partition_list_edit_activate
    self.partman_edit_dialog(devpart, partition)
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 1879, in partman_edit_dialog
    for script, arg, option in partition['method_choices']:
KeyError: 'method_choices'

*******
mint@mint ~ $ lsb_release -rd
Description: Linux Mint 8 Helena - Main Edition
Release: 8

[paranaense (tuliouel)]

Launch pad only allowed me to attach one file. Here is the partman one.

[paranaense (tuliouel)]

The version of the ubiquity package is 2.0.8-1mint4.
Thanks.

[paranaense (tuliouel)]

Same problem happens with ubuntu 9.10

[Simon Quigley (tsimonq2)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 523817

and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]