It sounds like this was fixed a few years ago so I'm closing it. If you
can still reproduce it on a current release, feel free to reopen it.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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/1329810
Title:
I could not reproduce this bug anymore on the latest daily utopic iso, I
am not absolutely sure yet, I have to do a final test to be sure this
was really resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubiquity (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1329810
Title:
Btrfs /boot partition has no UUID
To manage notifications about this
Chris, thanks for having a look, but it is clearly reproducible, I have
even recorded the whole setup process using virtualbox, to make sure it
is not related to me:
https://drive.google.com/file/d/0B-
ihXi2hkCPfdm5rSlk4dWxHLUE/edit?usp=sharing
I forget to demonstrate blkid at the end, though, I
Comments 8-12 are the information added from the virtualbox setup
demonstrated in the screencast (see #7) and was automatically attached
by apport-collect, hence the additional description here.
** Tags removed: ident-mismatch
--
You received this bug notification because you are a member of
apport information
** Tags added: apport-collected
** Description changed:
Do the following to reproduce the problem: Using the installer create a
/boot partition (primary) using btrfs as file system. When the install
is finished and you boot up the system, the fstab entry for /boot looks
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the
No, that is not a problem of my install media ... I knew why I did not
attach the logs initially. The problem is clearly reproducible with an
official media using manual install (no preseeding, no qemu for
installing). The media I used for the install the log files come from
was remastered (I
Using ubuntu-14.04-desktop-amd64.iso installing with a custom layout to
UEFI VM, partitions are EFI System partition (vfat), boot (btrfs), and
root (btrfs), with no swap partition, each btrfs volume has a UUID and
it's used in the fstab. So I can't reproduce this bug.
--
You received this bug
** Attachment added: apport.ubiquity.mocj9v_c.apport
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1329810/+attachment/4131156/+files/apport.ubiquity.mocj9v_c.apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Preseed file used for the installation the apport debug information is
from.
** Attachment added: install.seed
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1329810/+attachment/4131066/+files/install.seed
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
Do the following to reproduce the problem: Using the installer create a
/boot partition (primary) using btrfs as file system. When the install
is finished and you boot up the system, the fstab entry for /boot looks
like this:
- /dev/sdb1 /boot btrfs defaults 0 2
13 matches
Mail list logo
