Ubuquity crashed during fresh installation on a partition in an external GUID drive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I prepared a USB hard drive GUID-formatted on MacOS X 10.9 with a HFS+ (with journaling turned on) in it.
Then I boot in (EFI) Ubuntu live USB made with mac-linux-loader.
I made room in the hard drive using gparted there to "Install Ubuntu 13.10."
(I performed several reboots because of unexpected freeze of the installer.)
I chose "else" and made root ext4 (around 16GB) and linux-swap (around 8GB) in that room, with the "boot-loader" on /dev/sdc (the hard disk.)
I created an initial user and logged into Ubuntu One. After that, I left the computer (MacBook Pro 15" Retina early-2013).
When I came back, I touched the computer to wake up its screen, and I found the crash message.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity 2.15.26
ProcVersionSign
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
CasperVersion: 1.336ubuntu1
Date: Tue May 6 20:00:15 2014
InstallCmdLine: BOOT_IMAGE=
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac (20131016.1)
MarkForUpload: True
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_
LANG=ja_JP.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | added: ubiquity-upgrade |
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 1316575
and any other logs that are relevant for this particular issue.