ubiquity crashed with InstallStepError in configure_ma()

Bug #445187 reported by Saverio J Marasco (Sam)
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

This has been going on here for some time. Ubuntu 8.o4 ran fine. 8.10 ran fine. When I did update to 9.04 it borked. I was still able to boot to Vista 64 bit. I had been installing Ubuntu 32 bit. After 9.04 borked I reinstalled 8.10, and it worked for a while, then crashed. Vista still booted ok, but only with it's own loader. Grub was gone. Attempt to reinstall 8.10 failed with this dang ubiquity error. I tried uninstalling Grub. re-installing grub. Always the ubiquity error. Then I tried re-installing Windows (thinking that would overwrite the boot sector) and Yes Vista booted fine. Then I tried 8.10 then 9.04 64 bit. The dang grub problem was still there. I had the partition program re-format the partition I used for "/". nope. I do not want to re-format the "/home" partition. I'll lose all my data.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
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/6924/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with InstallStepError in configure_ma()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups:

Revision history for this message
Saverio J Marasco (Sam) (sammorxman) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #234835, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
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.