ubiquity crashed with InstallStepError in configure_plugins() in Ubuntu 10.04 VM in VirtualBox 3.2.4, Ubuntu 9.10 Host
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Linux |
Fix Released
|
Medium
|
|||
| Virtualbox |
Fix Released
|
Unknown
|
|||
| ubiquity |
Fix Released
|
Unknown
|
|||
| ubiquity (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: ubiquity
1) lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04
2) apt-cache policy ubiquity
ubiquity:
Installed: 2.2.24
Candidate: 2.2.24
Version table:
*** 2.2.24 0
500 http://
100 /var/lib/
2.2.23 0
500 http://
3) What I expected to happen is that when I tried to perform a fresh install of Ubuntu 10.04 VM in VirtualBox 3.2.4 (Ubuntu 9.10 Host) it installs successfully with no problem.
4) What happens instead is the install failed.
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ubiquity 2.2.24
ProcVersionSign
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Mon Jun 7 15:34:45 2010
ExecutablePath: /usr/lib/
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/bin/python /usr/lib/
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/
PythonArgs: ['/usr/
SourcePackage: ubiquity
Title: ubiquity crashed with InstallStepError in configure_plugins()
UserGroups:
| Changed in virtualbox: | |
| status: | Unknown → New |
| Changed in ubiquity: | |
| status: | Unknown → New |
| Changed in ubiquity: | |
| status: | New → Fix Released |
| Changed in virtualbox: | |
| status: | New → Fix Released |
| Changed in linux: | |
| status: | Unknown → Confirmed |
| Changed in linux: | |
| importance: | Unknown → Medium |
| Changed in linux: | |
| status: | Confirmed → Fix Released |

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 #530283, 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.