Kubuntu flight 7 installer crash + mount point selection bug

[dtattersall]

Apple Powerbook G4 1.67 Ghz, 1 G ram;
Kubuntu Dapper Drake flight 7

There are two bugs, the second is probably more serious.

While doing the install, I got through step 5,6 (selected manual partition) and then I wanted to change something at the "select partition mount points" section (see second problem) and clicked back a few times. On clicking forward again, I guess the radio button had been reset to the "Resize IDE1 master..." option, and when I clicked forward, the installer crashed with the following trace:

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 1174, in watch_debconf_fd_helper_read
    self.debconf_callbacks[source](source, debconf_condition)
  File "/usr/lib/python2.4/site-packages/ubiquity/filteredcommand.py", line 143, in process_input
    if not self.process_line():
  File "/usr/lib/python2.4/site-packages/ubiquity/filteredcommand.py", line 81, in process_line
    return self.dbfilter.process_line()
  File "/usr/lib/python2.4/site-packages/ubiquity/debconffilter.py", line 256, in process_line
    widget.subst(question, key, value)
  File "/usr/lib/python2.4/site-packages/ubiquity/components/partman.py", line 72, in subst
    self.frontend.set_autopartition_resize_min_percent(
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 1467, in set_autopartition_resize_min_percent
    self.new_size_scale.setMinValue(min_percent)
AttributeError: Wizard instance has no attribute 'new_size_scale'

The second bug happens on the "select mount point" screen. I accidentally filled in three mount points, so a fourth, blank, set of mount point dropdown boxes appeared. However, after changing the mount points back to

/
swap
[blank]
[blank]

The installer would not let me continue, giving me the "two mount points are the same" error. I assume the installer is incorrectly considering [blank] as a mount point. It seems like an easy "&& selection != blank" fix, but I don't know python.

There's also a spelling mistake in the english version in a partitioning warning I saw something like "...will lost all data", the "lost" should be "lose"

[Colin Watson (cjwatson)]

(It really does help me if you file separate bugs in separate reports rather than filing one big report for everything, by the way ...)

Thanks for your report. Your first bug is also bug 43015; your second is also bug 46402. Both are fixed in the Dapper release candidate.

I've looked for the "will lost all data" string you mention and unfortunately I cannot find it. If you can get me the exact text, then please file a separate bug with that.