I've been testing this in qemu, with two different virtual machines
(built with the same default settings), one doing Scenario 1, then
Scenario 2, one the other way around.
I'm using the same preseed; with the exception that "d-i partman-
auto/choose_recipe select boot-crypto" is commented out (it shouldn't be
necessary, but I also testing without commenting it), and using /dev/vda
rather than /dev/sda as a target device.
I'm unable to get precisely the message "No modifications can be made to
the device Encrypted volume (sda5_crypt) for the following reasons: In
use by LVM volume group ubuntu-vg." when installing with scenario 2 if I
follow your steps precisely. I do get a message about creating the key
file, followed by a "An error occurred while configuring encrypted
volumes. The configuration has been aborted.". I am then left at the
partman dialog. In indeed appears to happen independently of any
previous installation artefacts on the disk.
However, if I re-run the same installer step for Scenario 2 (ie. fully
automated), but with the addition of "automatic-ubiquity" which behaves
the same as passing --automatic to ubiquity in Scenario 1, then the
installation completes successfully.
Could you please try again, with adding 'automatic-ubiquity' for
scenario 2; and report here whether it solves the problem?
Thanks!
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386153
Title:
Inconsistent behaviour between 2 ways of launching Ubiquity
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1386153/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
