If you are still experiencing this bug, please set its status back to
"confirmed".
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of
The issue seems to be fixed in the final 16.04 release. I downloaded
Xenial today (April 21st 2016, release day) and I cannot reproduce the
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553652
I would like to add that the Linux Action Show podcast spoke about this
issue on their episode 413 where they review 16.04. They say they had to
manually partition the drive to workaround this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I also get this bug.
I got it when trying to install 16.04 development branch (files on the
USB thumb drive are from April 16th 2016) over an existing 14.04 HDD.
I then replaced the HDD with a brand new SSD (with no partitions on it)
and installed that same 16.04 version with no issues.
And I
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (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/1553652
Title:
Correction on last comment. I thought I was installing to unused space
however I realized that I turned off the Machine Deletion/Reallocation
in my virtualbox scripting. The error appears to be that when the Erase
Disk and Install Ubuntu option is selected, the partition delete process
is not
i negkected to include that the target of the installation was freshly
allocated machine under virtualbox with no prior partitions in virtual
Disks being used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
