As of subiquity 22.04.1 I see no problem. So let't put this to "Fix
committed".
Actually a volume group "ubuntu-vg-1" with a distinct name is created on
the second install:
sda8:00 232.9G 0 disk
├─sda1 8:10 1G 0 part
├─sda2
For the LP description issue, I have opened
https://github.com/canonical/subiquity/pull/1263.
For the comment about a duplicate ubuntu-vg entry, I can't reproduce that
problem.
** Changed in: subiquity (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
** Changed in: subiquity
** Changed in: subiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968160
Title:
subiquity 22.02.2+git180.1b7ab29e: corrupt partitioning menu
To
@Dan, no I caught my error when seeing the list of partition usages. I
did not destroy my preexisting installation on /dev/nvme0n1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968160
Title:
@Heinrich, when you selected the wrong disk, how far did you get? Did
you say Continue on the dialog titled "Confirm destructive action"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968160
Title:
My installation on /dev/nvme0n1 does not use any volume group.
So I wonder why in the subiquity display volume group "ubuntu-vg" was
shown for /dev/nvme0n1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On /dev/nvme0n1 the volume group is called ubuntu-vg.
When installing on /dev/sda the same volume group name is chosen.
This does not make sense. A different group name should be used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
