[Bug 1247052] [NEW] installer ubiquity reproducibly crashes after setting up encrypted partitions alongside the ones of MacOS X 10.9
dareka
dareka337 at yahoo.com
Fri Nov 1 10:37:56 UTC 2013
Public bug reported:
Hardware is a MacBook 6.1 with OS X 10.9 installed on a 100GB partition,
leaving 150 GB of free space for Linux. The OS X partition is encrypted
via FileVault 2 (whole disk mode); apart from that, there are
unencrypted partitions for the EFI and OS X recovery.
Since Ubuntu 13.10 does not recognize OS X 10.9 being installed I cannot
use the guided partitioning ubiquity presents (since it would always use
the whole disk for Ubuntu). Thus I chose manual partitioning and created
partitions for /boot, for the physical volume for encryption, and on the
resulting mapper one for root and one for swap. Additionally, I created
a small unencrypted partition for grub, because the installer said this
would be needed (this was only the case when I did not boot the install
medium in EFI mode).
After partitioning, selecting the timezone and finally the keyboard
layout, the installer invariably crashes.
I also tried installing Kubuntu, but it failed to create the encrypted
partitions altogether. With the ubuntu server cd I did not even get past
the first dialogue, because the keyboard does not work.
Hopefully, this information will help to fix the issue. Thanks in
advance (and, of course, also in retrospect) to anyone working on
Ubuntu!
Best regards.
Marcel
P.S. It says here that "Extra debug information will be added to the bug
report automatically." — I assume all information mentioned by the
reporting guidelines has already been included by the reporting
assistant that popped up after ubiquity crashing. Please let me know if
there is any information missing.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity 2.15.26
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
CasperVersion: 1.336ubuntu1
Date: Fri Nov 1 11:05:33 2013
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
ProcEnviron:
LANGUAGE=en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug saucy ubiquity-2.15.26 ubuntu
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1247052
Title:
installer ubiquity reproducibly crashes after setting up encrypted
partitions alongside the ones of MacOS X 10.9
Status in “ubiquity” package in Ubuntu:
New
Bug description:
Hardware is a MacBook 6.1 with OS X 10.9 installed on a 100GB
partition, leaving 150 GB of free space for Linux. The OS X partition
is encrypted via FileVault 2 (whole disk mode); apart from that, there
are unencrypted partitions for the EFI and OS X recovery.
Since Ubuntu 13.10 does not recognize OS X 10.9 being installed I
cannot use the guided partitioning ubiquity presents (since it would
always use the whole disk for Ubuntu). Thus I chose manual
partitioning and created partitions for /boot, for the physical volume
for encryption, and on the resulting mapper one for root and one for
swap. Additionally, I created a small unencrypted partition for grub,
because the installer said this would be needed (this was only the
case when I did not boot the install medium in EFI mode).
After partitioning, selecting the timezone and finally the keyboard
layout, the installer invariably crashes.
I also tried installing Kubuntu, but it failed to create the encrypted
partitions altogether. With the ubuntu server cd I did not even get
past the first dialogue, because the keyboard does not work.
Hopefully, this information will help to fix the issue. Thanks in
advance (and, of course, also in retrospect) to anyone working on
Ubuntu!
Best regards.
Marcel
P.S. It says here that "Extra debug information will be added to the
bug report automatically." — I assume all information mentioned by the
reporting guidelines has already been included by the reporting
assistant that popped up after ubiquity crashing. Please let me know
if there is any information missing.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity 2.15.26
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
CasperVersion: 1.336ubuntu1
Date: Fri Nov 1 11:05:33 2013
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
ProcEnviron:
LANGUAGE=en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1247052/+subscriptions
More information about the foundations-bugs
mailing list