ubiquity crashed with InstallStepError in configure_bootloader()

Bug #556048 reported by Tobin Davis
38
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: ubiquity

Image from daily 20100405.

The install hardware was a Dove X0 platform with an 8G CF card in a CF<>SATA converter (tested on x86 system). Unsure where in the install it actually failed as I was out of the room during install (~25 minutes). The dmesg log indicates that the system was trying to access beyond the physical size of the device.

Will try again with a 16G SSD to see if it is reproducible on other devices.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ubiquity 2.2.14
ProcVersionSignature: Ubuntu 2.6.32-203.15-dove 2.6.32.10+drm33.1
Uname: Linux 2.6.32-203-dove armv7l
Architecture: armel
Date: Mon Apr 5 14:20:08 2010
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha armel+dove (20100405)
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/2687/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with InstallStepError in configure_bootloader()
UserGroups:

Revision history for this message
Tobin Davis (gruemaster) wrote :
tags: removed: need-duplicate-check
Tobin Davis (gruemaster)
visibility: private → public
Revision history for this message
Oliver Grawert (ogra) wrote :

seeing bug #582850 this doesnt seem to be arch specific

tags: added: ubiquity-2.2.14
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with the disk to which you are trying to install Ubuntu. I'd recommend performing a back up of your existing operating system and then investigating the situation. Measures you might take include checking cable connections for your disks and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck!

Changed in ubiquity (Ubuntu):
status: New → Invalid
importance: Undecided → Low
tags: added: hardware-error
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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