ubiquity crashed with InstallStepError in configure_bootloader()

Bug #303733 reported by Pietro Battiston
6
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

I absolutely don't know if this bug is a dup of 229281, 260001, 71984 or what; not only I have no clue in understanding if is so, but moreover I thought that reporting the bug as a new one would have brought the trace informations.

My partitions setup is quite messy, because I have several different installations:

Model: ATA WDC WD2500BEVS-6 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 32.3kB 68.9GB 68.9GB primary ntfs boot
 3 68.9GB 233GB 164GB extended
 9 68.9GB 78.9GB 10.0GB logical ext3
10 78.9GB 88.9GB 10.0GB logical ext3
 5 99.9GB 207GB 107GB logical ext3
 6 207GB 217GB 10.0GB logical ext3
 7 217GB 222GB 5001MB logical ext3
 8 222GB 233GB 11.1GB logical ext3
 2 240GB 250GB 10.2GB primary ntfs

Notice there is free space between 10 and 5 and between 8 and 2.

At first, partition 9 and 10 didn't exist, but between 8 and 2 there was swap. I tried making a new installation of intrepid in a new ext3 partition situated where now partition 9 is, but got this bug and was unable to complete installation. I tried several times, but the bug was always triggered.

Finally, I thought maybe ubiquity was unable to deal with double cypher partitions, and while this supposition showed later to be wrong, it luckily did help me: I deleted the swap space and the new partition (9, remember 10 still didn't exist) and tried installing again: this time, no problem, so at the moment partition 9 is a perfectly working intrepid installation.

But the bug is still here if I try to make a new intrepid installation (and unfortunately I have to, but it's a long story with other bugs affecting my intrepid experience): the data I'm attaching refers to a new (temptative of) installation to the partition 10. It fails systematically.

Every ubiquity developer probably know, but anyway: I said the supposition of ubiquity not handling /dev/sda** is wrong because I tested intrepid livecd in a virtual machine and was able to successfully install in /dev/sda13 or so.

I also thought "OK, maybe the problem is if there are more than 9 partitions AND they are not in order", but a virtual machine test showed this is wrong too.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: wl
Package: ubiquity 1.10.10
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/8484/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with InstallStepError in configure_bootloader()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups:

Tags: apport-crash
Revision history for this message
Pietro Battiston (toobaz) wrote :
Revision history for this message
Pietro Battiston (toobaz) wrote :

As requested in bug 69944 by Simon Law, I'm attaching /var/log/syslog and /var/log/partman

Notice I can replicate this bug at any time is more info is needed (but also notice it takes me half an hour at every time...)

Revision history for this message
Pietro Battiston (toobaz) wrote :

Here's syslog

Revision history for this message
Jim Rorie (jfrorie) wrote :

I had the same crash, on a nearly identical machine except that I was installing on a 320GB using the whole disk. No partitions. It was a hardware raid, but the mirror was broken at the time.

Failed to install grub.

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.