livecd installer crashes in Ubuntu Dapper (6.06) Flight 7
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:/
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:/
Traceback (most recent call last):
File "/usr/lib/
return callback(source, debconf_condition)
File "/usr/lib/
if not self.process_
File "/usr/lib/
return self.dbfilter.
File "/usr/lib/
if not input_widgets[
File "/usr/lib/
('ubiquity/
File "/usr/lib/
dialog = gtk.Dialog(title, transient, gtk.DIALOG_MODAL, tuple(buttons))
RuntimeError: first member of each text/response id pair must be a string
As bug #45708 gives exactly the same error report as this bug, I think it's OK to mark both bugs as "Confirmed".