The gnome disks program is not parted, and also the reason you could not
create a partition is because you did not have a partition table. You
must create a partition table first, then create a partition in the
disk, then dd your filesystem into THAT.
** Changed in: parted (Ubuntu)
** Changed in: grub2 (Ubuntu)
Assignee: Marcos Nascimento (wstlmn) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807537
Title:
failure in fsck option of advanced boot
To
costales writes:
> Would this hack fix the issue? (Add/Remove xhost +si:localuser:root to the
> launcher)
> I don't know if this could means something dangerous in Wayland.
I'm not sure if it will fix things run as root via pkexec but it will if
you manually run gui programs as root. There's
Upstream concluded that the bug lies in udisks. It needs a similar fix
to one it got before to wait for the changes to propagate before
returning from resize. Unmount needs a similar waiter.
** Also affects: udisks2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
It turns out that just trying to unmount an fs is broken. Apparently
resize mounts the fs first for some reason, then when it tries to
unmount, it can't.
** Summary changed:
- Resize is broken
+ Unmount is broken
** Description changed:
- Try to resize an ext4 partition with the gnome disks
Nevermind, it still doesn't work on the right disk. While the disk is
not mounted initially, by the time unuse_data_iterate() is called, it
has been mounted for some reason. I'm thinking there is a race
condition where something mounts the fs temporarily and unmounts it, and
during the time it
Man this cold must really be messing with my head. I had the wrong
drive selected and actually was trying to resize the root partition.
** Changed in: gnome-disk-utility (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
So I ran it under gdb and set a breakpoint to find how unmount_cb() is
being called and traced the problem back up to unuse_data_iterate(). It
calls gdu_utils_is_in_use_full(), which incorrectly identifies the mount
point of the filesystem as "/". So it looks like either it is finding
the wrong
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
** Summary changed:
- After QEMU execution with keyboard passthrough, key mappings are lost
+ Unplugging and re-plugging keyboard forgets xmodmap
** Package changed: qemu (Ubuntu) => xorg (Ubuntu)
** Changed in: xorg (Ubuntu)
Status: Invalid => New
--
You received this bug notification
Can you run sudo efibootmgr -vv and post the output?
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789471
Title:
Isn't that just a workaround? There is still an underlying bug in the
iPXE network driver isn't there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using
*** This bug is a duplicate of bug 1772374 ***
https://bugs.launchpad.net/bugs/1772374
** This bug has been marked a duplicate of bug 1772374
ubiquity need mount point /sys/firmware/efi/efivars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On 9/7/2018 3:06 AM, Paddy Landau wrote:
> If you are arguing that /boot shouldn't be encrypted, this is a direct
> contradiction of what you wrote earlier that malware can be loaded into
> the ESP; so why couldn't malware be loaded into /boot?
It can. Encrypting it does not stop that.
> Please
If your goal is secure boot, then you need signature verification.
Encryption is not required for that. Encryption is for data privacy,
and as I said before, nothing you consider private should be in /boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
How is this something relied on for building images? As it stands, such
a boot entry is non functional since it doesn't tell grub to set up a
loop mapping to the underlying file so the "disk" won't be found. If
you are building an image and later transferring that image to bare
metal, then it
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
Having *any* unsigned kernel should not fail the upgrade process. At
best, a debconf warning should be presented.
** Changed in: grub2 (Ubuntu)
Status: Opinion => New
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a
Please choose the memtest option from the boot menu and let it run for
at least 15 minutes and let us know if it finds any errors.
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also what does getconf PAGESIZE say under the broken kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788321
Title:
swapon failed: invalid argument
To manage notifications about this bug go
This doesn't happen on amd64. Do you also have to re-run mkswap when
switching back to the older, working kernel, or does simply using the
other kernel let you run swapon on the same file that doesn't work with
the newer kernel?
** Changed in: linux (Ubuntu)
Status: Incomplete =>
You have a broken third party startup script installed named "nifi".
You will need to remove it.
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1772374 ***
https://bugs.launchpad.net/bugs/1772374
** This bug has been marked a duplicate of bug 1772374
ubiquity need mount point /sys/firmware/efi/efivars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
That's really weird. I didn't even think grub showed up on a second
monitor at all. What if you press C to go to the command line and type
a few characters? As you type do they show up differently?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
** This bug has been marked a duplicate of bug 1788727
upgrade crashing due to unsigned kernels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
Your USB stick contains a mix of bionic and xenial. Before reusing it
for another release, you need to clean the old one off.
** Changed in: grub-installer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
** This bug has been marked a duplicate of bug 1788727
upgrade crashing due to unsigned kernels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
15.04 reached end of life years ago. Are you still seeing this on a
currently supported release?
** Changed in: apport (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI, you can use manual partitioning and mount the ESP of your choice in
/efi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396379
Title:
installer uses first EFI system partition found even when
Actually it looks like it's gnome-disk-utility that does the unmount and
throws the error. I can't for the life of me figure out this rat nest
of code though. In gduresizedialog.c, resize() calls
gdu_utils_ensure_unused() and passes it unmount_cb(), which appears to
be what is throwing that
Public bug reported:
Try to resize an ext4 partition with the gnome disks utility. It throws
an error saying it can't unmount the filesystem because it isn't
mounted. This is on 18.04.
** Affects: udisks2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Changed in: gnome-disk-utility (Ubuntu)
Status: New => In Progress
** Changed in: gnome-disk-utility (Ubuntu)
Assignee: (unassigned) => Phillip Susi (psusi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed it.
** Tags added: patch
** Patch added: "debdiff.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1789693/+attachment/5182282/+files/debdiff.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
*** This bug is a duplicate of bug 1788727 ***
https://bugs.launchpad.net/bugs/1788727
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1788727, so it is being marked as such. Please
This appears to have been fixed at some point over the last 8 years.
There is now an "other" option that opens another dialog that includes
udf as an option.
** Changed in: gnome-disk-utility (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are
In the years since this was reported, it appears to have been fixed.
There have been substantial changes to the dialog and everything now
seems to fit.
** Changed in: gnome-disk-utility (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member
Public bug reported:
A volume label is an optional feature, but the dialog box greys out the
next button unless you type something in the label field.
** Affects: gnome-disk-utility (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
You haven't happened to fix this in the last 8 years have you Ted? ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575542
Title:
resize2fs does not respect flex_bg
To manage notifications about
This should have expired long ago.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/724512
Title:
Radeon video card runs too hot
To
Looking back at this 5 years later it seems that I misread the man page.
With no options it is supposed to require a kernel image to load and
execute. If you just want to execute the already loaded image, you run
kexec -e.
** Changed in: kexec-tools (Ubuntu)
Status: Confirmed => Invalid
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What are the command line parameters of this grub-mount? What kind of
partitions do you have on your disk? Can you attach an strace to this
process?
** Changed in: grub (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Your usb stick is corrupt; you will need to recreate it and may want to
verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1772374 ***
https://bugs.launchpad.net/bugs/1772374
** This bug has been marked a duplicate of bug 1772374
ubiquity need mount point /sys/firmware/efi/efivars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
** Summary changed:
- package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed
grub-efi-amd64 package post-installation script subprocess returned error exit
status 1
+ upgrade crashing due to unsigned kernels
--
You received this bug notification because you are a member
Then I would suggest you run the memtest option for at least 15 minutes.
Your logs say the data was corrupt, so if it isn't corrupt on the disk,
it got corrupted in memory:
Aug 15 02:29:36 ubuntu kernel: [ 942.369736] SQUASHFS error: zlib
decompression failed, data probably corrupt
Aug 15
Can you run sudo efibootmgr -vv and post the output? Also dmesg | tail
after that.
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 8/21/2018 9:34 PM, Daniel van Vugt wrote:
> Phillip,
>
> Mutter is not just a binary, but is also the library which provides ALL
> the graphics for the login screen and gnome-shell. So yes Ubuntu does
> use mutter for everything :)
Ohh... I thought it was an alternative light weight
Can you try it and see if that is the case? ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609900
Title:
After QEMU execution with keyboard passthrough, key mappings are lost
To manage
I'm not sure there is any legitimate case for booting $RELEASE1 and
trying to have the installer install $RELEASE2. And even if there were,
you can't do that now anyhow. It should be as simple as having apt-
cdrom check lsb_release, and only look in that pool directory instead of
searching them
*** This bug is a duplicate of bug 1772374 ***
https://bugs.launchpad.net/bugs/1772374
** This bug has been marked a duplicate of bug 1772374
ubiquity need mount point /sys/firmware/efi/efivars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1772374 ***
https://bugs.launchpad.net/bugs/1772374
** This bug has been marked a duplicate of bug 1772374
ubiquity need mount point /sys/firmware/efi/efivars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What you are talking about is signature verification. You need the
firmware to verify the signature on the kernel and initrd, using a
custom self signing key only. That is unrelated to whether /boot is
encrypted or not.
--
You received this bug notification because you are a member of Ubuntu
You will need to report that to the mint developers.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788346
Title:
Ubiquity crashes
On 8/21/2018 12:29 PM, Mathieu Trudel-Lapierre wrote:
> This has to do with grub not grokking the metadata format on disk, which
> is avoidable by using metadata 0.90.
What? Grub understands all of the metadata formats.
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1788167 ***
https://bugs.launchpad.net/bugs/1788167
** This bug has been marked a duplicate of bug 1788167
Erro na instalação do grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Your hard disk appears to have been unplugged during the install. You
may have a loose or bad SATA cable.
** Changed in: grub-installer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
I tried wayland and the session just failed and went right back to the
low resolution login screen, which is Xorg. I tried wayland a second
time and just get a permanent busy cursor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1772374 ***
https://bugs.launchpad.net/bugs/1772374
** This bug has been marked a duplicate of bug 1772374
ubiquity need mount point /sys/firmware/efi/efivars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You tried to install grub to /dev/nvme0, which is not partitioned.
Either install grub to /dev/nvme1 or partition nvme0. Also your log is
full of errors like this, which indicate something is wrong with your
motherboard or a peripheral:
Aug 20 20:48:35 ubuntu kernel: [4.884548] pcieport
*** This bug is a duplicate of bug 1772374 ***
https://bugs.launchpad.net/bugs/1772374
** This bug has been marked a duplicate of bug 1772374
ubiquity need mount point /sys/firmware/efi/efivars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
*** This bug is a duplicate of bug 1766945 ***
https://bugs.launchpad.net/bugs/1766945
** This bug has been marked a duplicate of bug 1766945
(EFI on top of legacy install) choosing "replace" or "resize" options in
partitioning may lead to an install failure
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
*** This bug is a duplicate of bug 1772374 ***
https://bugs.launchpad.net/bugs/1772374
** This bug has been marked a duplicate of bug 1772374
ubiquity need mount point /sys/firmware/efi/efivars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That was two Vs: -vv. Also after getting this error, can you run dmesg
and check the last one or two lines to see if they give any more
information?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please attach /var/log/apt/term.log
** Changed in: util-linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787799
Title:
package bsdutils
"extix" is not an official Ubuntu flavor, and so is not supported here.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583394
instead.
This did not used to happen, and probably started when I upgraded the
server from 16.04 to 18.04 a while back and I just haven't been testing
VMs since then.
** Changed in: qemu (Ubuntu Bionic)
Assignee: (unassigned) => Phillip Susi (psusi)
--
You received this bug
** Description changed:
+ [Impact]
+
+ After upgrading from 16.04 to 18.04, users are unable to type a | or >
+ in their virtual machines when accessing them via vnc. This happened
+ because upstream added a key to the keymap that can also produce these
+ symbols and exists only on European
** Patch added: "fix-pipe.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1787267/+attachment/5179261/+files/fix-pipe.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787267
Ok, it seems to have optional dependencies that I had installed when
trying to build the code from the debian git repo. Rebuilt in a clean
chroot and it works great! Also noticed that the > key is affected,
becoming < instead. This simple patch fixes it.
--
You received this bug notification
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the grub menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubiquity (Ubuntu)
Assignee: AMIT KUSHWAHA (amitkushwaha) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/7175
Title:
something should confirm that the
*** This bug is a duplicate of bug 1783996 ***
https://bugs.launchpad.net/bugs/1783996
** This bug has been marked a duplicate of bug 1783996
[efi on top of legacy] Show a warning that installation will fail if user
doesn't create an ESP partition or fallback to grub-pc
--
You received
*** This bug is a duplicate of bug 1783996 ***
https://bugs.launchpad.net/bugs/1783996
** This bug is no longer a duplicate of bug 1704510
Partman should warn about not having an EFI system partition
** This bug has been marked a duplicate of bug 1783996
[efi on top of legacy] Show a
*** This bug is a duplicate of bug 1783996 ***
https://bugs.launchpad.net/bugs/1783996
** This bug is no longer a duplicate of bug 1704510
Partman should warn about not having an EFI system partition
** This bug has been marked a duplicate of bug 1783996
[efi on top of legacy] Show a
*** This bug is a duplicate of bug 1783996 ***
https://bugs.launchpad.net/bugs/1783996
** This bug is no longer a duplicate of bug 1704510
Partman should warn about not having an EFI system partition
** This bug has been marked a duplicate of bug 1783996
[efi on top of legacy] Show a
*** This bug is a duplicate of bug 1783996 ***
https://bugs.launchpad.net/bugs/1783996
** This bug is no longer a duplicate of bug 1704510
Partman should warn about not having an EFI system partition
** This bug has been marked a duplicate of bug 1783996
[efi on top of legacy] Show a
*** This bug is a duplicate of bug 1783996 ***
https://bugs.launchpad.net/bugs/1783996
** This bug is no longer a duplicate of bug 1704510
Partman should warn about not having an EFI system partition
** This bug has been marked a duplicate of bug 1783996
[efi on top of legacy] Show a
*** This bug is a duplicate of bug 1783996 ***
https://bugs.launchpad.net/bugs/1783996
** This bug is no longer a duplicate of bug 1704510
Partman should warn about not having an EFI system partition
** This bug has been marked a duplicate of bug 1783996
[efi on top of legacy] Show a
*** This bug is a duplicate of bug 1783996 ***
https://bugs.launchpad.net/bugs/1783996
** This bug is no longer a duplicate of bug 1704510
Partman should warn about not having an EFI system partition
** This bug has been marked a duplicate of bug 1783996
[efi on top of legacy] Show a
1 - 100 of 12989 matches
Mail list logo
