livecd installer crashes in Ubuntu Dapper (6.06) Flight 7

Bug #45771 reported by Blujuice
This bug report is a duplicate of:  Bug #43012: crash creating partman question dialog. Edit Remove
12
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Everytime I try to install Ubuntu Dapper Flight 7 using the livecd installer, it crashes about 2 seconds after the confirmation dialog (when reformatting the two empty partitions, the installer crashes about 2 seconds after it finishes formatting) and shows me an error report (see below). I'm installing it on to empty (but already formatted) partitions (root: 7,25 GB/ext3; swap: 1GB/swap) and the error occurs no matter if I choose "Reformat Partition" or if I don't reformat the partitions.

This bug is very similiar to bug #45708 and gives exactly the same error report, but unlike #45708, the installer neither screws up my MBR nor deletes any partitions. (That's why I don't think this bug is a duplicate of #45708, though it gives exactly the same error report.)

Before flight 7, I tried beta 1&2, and with both of them, a very similar error occured, with the only difference that the installer crashed without even giving an error report. This bug was reported as bug #39734 and bug #40819 and according to the ubuntu-annouce mailing list ( https://lists.ubuntu.com/archives/ubuntu-announce/2006-May/000080.html ), it was fixed with flight 7, but on my computer, the only thing that's fixed in flight 7 is that the installer now shows an error report instead of crashing "silently".

I'm using an Intel Pentium 4 ("Northwood", 3,0 Ghz, FSB800, Hyper Threading), Intel 875P Chipset, ATI Radeon 9800 Pro and the Dapper Flight 7 x86 32bit livecd and this is the error report the installer shows (as mentioned above, it's exactly the same error report as in #45708):

----------

We're sorry; the installer crashed. Please file a bug report at https://launchpad.net/distros/ubuntu/+source/ubiquity/+filebug and a developer will attend to the problem as soon as possible. To help the developers understand what went wrong, include the following detail in your bug report:

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 1084, in watch_debconf_fd_helper
    return callback(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 219, in process_line
    if not input_widgets[0].run(priority, question):
  File "/usr/lib/python2.4/site-packages/ubiquity/components/partman_commit.py", line 123, in run
    ('ubiquity/text/go_back', 'ubiquity/text/continue'))
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 1463, in question_dialog
    dialog = gtk.Dialog(title, transient, gtk.DIALOG_MODAL, tuple(buttons))
RuntimeError: first member of each text/response id pair must be a string

Blujuice (blujuice)
description: updated
Revision history for this message
Blujuice (blujuice) wrote :

As bug #45708 gives exactly the same error report as this bug, I think it's OK to mark both bugs as "Confirmed".

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

Thanks for your report. This is also bug 43012, and is fixed in current daily builds.

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.