ubiquity crashed with InstallStepError in configure_bootloader()

Bug #376210 reported by bobble
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: ubiquity

downloaded official 904 netbook remix img file.
burnt to 1gb usb stick using diskimager?
booted from usb stick into 904 to check ok working
clicked install icon in 904 desktop
installed to 8gb sd card plugged into machine
got this error near the end of installsaying can't write to bootloader of the 8gb sd card
acer aspire one, 160gb hd, with easypeasy (804) already dual booting on master 160gb hd with XP
boot order was usb stick, sd usb cdrom, hd

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
MediaBuild: Ubuntu-Netbook-Remix 9.04 "Jaunty Jackalope" - Release i386 (20090421)
Package: ubiquity 1.12.12
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/5721/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Tags: ubuntu-unr
Title: ubiquity crashed with InstallStepError in configure_bootloader()
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Revision history for this message
bobble (bobhall106) wrote :
tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
Evan (ev) wrote :

Could you please try again with a Karmic daily-live CD (http://cdimage.ubuntu.com/daily-live/current/)? I just ran through an install to a SD card and it worked fine. Make sure in the advanced dialog (on the summary page) that the bootloader is installing to /dev/mmcblk0. Let me know if it wasn't already set to.

If the install fails, please attach /var/log/syslog and /target/boot/grub/device.map to this bug report.

Thanks!

Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
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.