Installer crash when manually partioning the disc

Bug #45931 reported by Gerald Arnould
8
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Relevant hardware configuration :
1 internal ide hard drive (hda)
1 external usb hard drive (sda) which is plugged in.
Daily live i386 2006-05-21

Using Ubiquity, I proceed through the installation steps. When I reach step 5, I do the appropriate changes on hda, then I apply this changes.
While the changes are being applied, I right-click on the external usb hard drive icon and select "umount". Then I plug out the usb hard drive. Note that the changes on hda are still being applied at that moment.

When the changes on hda are applied, ubiquity seems to re-read the partition table of both drives, including sda even though sda does not exist anymore and crash.

Here is the traceback of the crash :
Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 120, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 54, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 266, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 734, in process_step
    self.gparted_to_mountpoints()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 867, in gparted_to_mountpoints
    self.size_widgets[-1].set_text(
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 471, in set_size_msg
    size = float(self.size[widget.split('/')[2]])
KeyError: 'sda1'

Gerald Arnould (sanji)
description: updated
Revision history for this message
Colin Watson (cjwatson) wrote :

Hmm. I think this is a bit complicated to try to fix for Dapper, especially as it has an easy workaround ("don't do that, then"). I'll revisit it for Edgy.

Changed in ubiquity:
status: Unconfirmed → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

This turned out (a) to be more straightforward than I thought and (b) to have some more serious consequences if left unfixed, so I fixed it. Bug 46395 has the details.

Changed in ubiquity:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.