ubiquity hung during install of april 2 daily amd64

Bug #1163502 reported by sojourner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

this has been a recurring problem . see comment for more info.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.14.1 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CasperVersion: 1.330
Date: Tue Apr 2 18:21:16 2013
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
sojourner (itsmealso2) wrote :
Revision history for this message
sojourner (itsmealso2) wrote :

I was attempting to install the april 2 amd64 daily to participate in the beta final test event . the first try there was a permissionns problem with /var/cache/debconf/passwords.dat . I made that file read-write for all and ran the installer again and when it hung I waited 20 minutes , quit ubiquity and ran ubuntu-bug .

description: updated
Revision history for this message
sojourner (itsmealso2) wrote :

update I have 6 drives many partitions and installs , I disconnected the drive with the win 8 install and the installation of the daily completed with no problem .

Revision history for this message
Brian Murray (brian-murray) wrote :

I don't see any errors in the log file regarding communicating with any of the drives.

Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1163502

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.