ubiquity crashed with InstallStepError in configure_bootloader()

Bug #291738 reported by togga
6
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

I have a fakeraid system and wanted to install intrepid on a extended partition on the fake-raid. To do this I
1. Booted up the intrepid desktop AMD64 live CD
2. installed "dmraid" and run "dmraid -r" to enable the raid devicce
3. run "gparted" and freed 20Gb storage at the end of the fakeraid by resizing a ntfs partition
4. used gparted to also create an extended partition : "/dev/mapper/nvidia___becjjdgf3"
5. on this extended patition I created one 2Gb swap partition and an 18Gb ext3 partition
6. run ubiquity to install system using the swap partition and the 18Gb partition as "/" mountpoint
7. ran into the crash

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.5
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/10653/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
togga (togga) wrote :
Revision history for this message
togga (togga) wrote :

Installing Intrepid using the alternate CD on the partitions made with gparted [on the live desktop CD since the alternate CD install can't shrink ntfs partitions] worked. So there seems to be a difference between the two install methods that make Ubiquity crash.

Revision history for this message
togga (togga) wrote :

 I think this bug is prematurely marked as a duplicate of bug 260001 - I actually read that bug report before filing this. My crash has different symptoms. That said, there is a possibility that the root cause are same or related but mothing in the comments on bug 260001 indicates that.

Why do you think this bug is a duplicate?

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.