ubiquity crashed when it could not unmount a parition and thus the migration assistant could not run

Bug #272874 reported by Thomas Lunde
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

1) ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10

2) ubuntu@ubuntu:~$ apt-cache policy ubiquity
ubiquity:
  Installed: 1.9.17
  Candidate: 1.9.17
  Version table:
 *** 1.9.17 0
        500 http://archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
ubuntu@ubuntu:~$

3) The installer to complete.

4) The installer crashed. Here's what was going on:

I'd written the Intrepid Alpha 5 to a USB stick using liveusb and then booted with that. For some reason a hard drive (not the usb stick) got mounted from /dev/sdb1 to /cdrom When going through the Installer, at about step 8 or so, the ubiquity wanted to umount /cdrom (so that it could run the migration assistant?). The Continue button brought up that dialog again. The Go Back button allowed the last confirmation screen to be shown and the install to start.

Later, after formatting partitions etc etc, ubiquity made the same complaint (need to unmount a partition -- I forget if it asked for /dev/sdb1 or /cdrom ). Again, the Continue button re-raised the same dialog. This time, however, the Go Back button made the installer crash.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.5
Package: ubiquity 1.9.17
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/8096/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with InstallStepError in configure_ma()
Uname: Linux 2.6.27-3-generic x86_64
UserGroups:

Tags: apport-crash
Revision history for this message
Thomas Lunde (tlunde) wrote :
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.