ubiquity crashed with InstallStepError in configure_ma()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubiquity
Performing fresh install using karmic i386 alpha 5 desktop install CD.
During user input the migration assistant step was skipped without prompting (step 7?)
The summary information screen included error messages relating to migration - I don't have these messages for reporting here.
During installation, after copying files to disk the migration install step started, but then ubiquity crashed, meaning install could not be completed. I didn't want to migrate any data, so it would have been better if a migration crash didn't abort the entire installation, but allowed it to continue by skipping importing of user data.
The system before installation had Windows XP installed. The intended setup after installation would be a dual boot Windows/Ubuntu system.
The migration assistant will have been able to detect existing Windows user profiles. Perhaps the crash was during the importing of this existing user data.
ProblemType: Crash
Architecture: i386
Date: Sun Sep 6 16:24:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090902.1)
Package: ubiquity 1.99.16
ProcCmdline: /usr/bin/python /usr/lib/
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: ubiquity
Title: ubiquity crashed with InstallStepError in configure_ma()
Uname: Linux 2.6.31-9-generic i686
UserGroups:
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.