ubiquity crashed with IOError in chroot_setup()

Bug #573473 reported by Robert Reese on 2010-05-02
54
This bug affects 7 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: ubiquity

Attempted repeatedly to install Ubuntu 10.04 LTS x64 Desktop (Lucid Lynx) via USB drive (Live CD) with three different solutions and two different downloaded ISOs from two different mirrors.

The target machine's harddrive is partitioned several times and contains Windows 7 Premium as well as Linux Mint 8 x64; I am attempting to install x64 Desktop into a dedicated 45GB partition that will be mounted as / as well as import two accounts - one from Windows and one from Linux Mint.

The installer gets to the point were it says it is configuring the hardware and crashes.... it does not always give me an opportunity to report the crash.

Hardware:
ASUS Eee PC 1201N
Intel ATOM 330 (x64 dual core)
1GB RAM
250 GB harddrive (using 45GB partition formatted as ext4 during install)

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ubiquity 2.2.24
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Sat May 1 17:38:33 2010
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/3414/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with IOError in chroot_setup()
UserGroups:

visibility: private → public
tags: removed: need-duplicate-check
tags: added: ubiquity-2.2.24
Changed in ubiquity (Ubuntu):
status: New → Confirmed
qweqq (qweqq) wrote :

After ubiquity crashed I saw that on /target there were two partitions mounted - the install destination partition and my Debian root partition. /target/home was also used as a mount point for my Debian home partition. Is it possible that when configuring hardware the setup chroots in the wrong /target ?

I didn't do anything else except running the installer, selecting to choose partitions manually, chose one partition for root and clicked install. (haven't specified to mount my debian home partition as /home).

Will try installing with the alternate cd image.

qweqq (qweqq) wrote :

The previous comment was meant for this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/249659

Sorry.

Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers