: netplan
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
** Description changed:
+ [Impact]
+ Ubuntu users who need to configure IP tunnels for their network.
+
+ [Test case]
+ 1) Sign-up / set up an Hurricane Electric tunnel at www.tunnelbroker.net.
+ 2) Configure netplan
** Description changed:
+ [Impact]
+ Documentation for netplan.
+
+ [Test case]
+ Run 'man netplan'; validate that the documentation clearly states that
setting MTU requires matching by MAC address; under the 'mtu' section.
+
+ [Regression potential]
+ None; this is limited to documentation.
+
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: netplan
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
** Changed in: netplan
Status: Triaged => Fix Released
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Fix Released
** Description changed:
- Currently DHCP appears to be an all or nothing boolean, which is
- insufficient for many network configurations.
+ [Impact]
+ DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
+
+ [Test case]
+ 1) Configure netplan for the
** Description changed:
+ [Impact]
+ Ubuntu users concerns with privacy of their IP addresses over IPv6.
+
+ [Test case]
+ 1) Configure netplan with IPv6 privacy enabled:
+
+ network:
+ version: 2
+ ethernets:
+ eth0:
+ dhcp6: true
+ ipv6-privacy: true
+
+ 2) Run 'netplan
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750392
Title:
Cannot
** Description changed:
+ [Impact]
+ Ubuntu users (especially on servers) wishing to make use of wireless devices
and configure them via netplan.
+
+ [Test case]
+ /!\ Requires a network setup with 802.1x security
+ 1) Install Ubuntu server on system that needs to connect to a wireless
network
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739578
Title:
Missing support for WPA2 Enterprise
To manage notifications about
** Package changed: nplan (Ubuntu) => netplan.io (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750392
Title:
nplan cannot enable IPv6 privacy extensions
To manage notifications about
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (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/1819507
Title:
Reassigning to mokutil and marking Fix Released:
I fixed that a few weeks ago. Mokutil reports the state it knows how to,
and that was previously only checking the state of the SecureBoot-*
variable, which is separate from the state that can be toggled in shim.
Now, mokutil looks at SecureBoot,
** Changed in: shim-signed (Ubuntu)
Status: Confirmed => Triaged
** Changed in: shim-signed (Ubuntu)
Importance: Undecided => Critical
** Changed in: shim-signed (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Also affects: shim (Ubuntu)
I
with a patched version shows
this delay can be completely eliminated by fixing the netplan-wpa
service and setting DefaultDependencies=no.
** Affects: netplan.io (Ubuntu)
Importance: Critical
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Changed
** Changed in: ubuntustudio
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818366
Title:
[FFe] Carla: Please Upload to Universe
To manage notifications
Nevermind the comment above; I fixed it myself (there's no point in
having a roundtrip just for that); uploaded the package as retrieved via
the dsc (https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/dev-
testing/+sourcefiles/carla/1.9.13-0ubuntu1/carla_1.9.13-0ubuntu1.dsc).
--
You
Please fix bug numbers to make sure you close the right bug (the FFE one
here) for the upload in changelog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818366
Title:
[FFe] Carla: Please Upload
So; who did the packaging? Ross or Erich? I'm concerned with the two
names being in changelog because it will make it hard to figure out who
did what :)
--
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 1818366 ***
https://bugs.launchpad.net/bugs/1818366
** This bug has been marked a duplicate of bug 1818366
[FFe] Carla: Please Upload to Universe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Manual testing with grub-pc and grub-efi-amd64 looks fine on x86.
Closing Fix Released so grub can migrate from -proposed.
** Changed in: grub2 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: grub2 (Ubuntu)
Status: New => In Progress
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Block grub2 (2.02+dfsg1-12ubuntu1) in disco-proposed for one last round
of manual testing.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Tags: block-proposed
** Changed in: grub2
Le ven. 1 mars 2019 07 h 34, Daniel Ducharme a
écrit :
> Bonsoir,
>
> J'ai tenté à deux ou trois reprises d'installer Ubuntu en dual boot
> mais, au moment de l'installation, Ubuntu considère que mon ordi n'a
> pas de système d'exploitation et, par conséquent, ne me propose pas
> cette
I'm not sure I understand the request. This is a paperwork bug that was
Fix Released, as libnfs was moved to the right location; it does not
really affect anything for supported releases.
If you need some changes made to packages, please file a separate new
bug with your specific request so that
** Changed in: netplan
Importance: Undecided => Critical
** Changed in: netplan
Status: Confirmed => In Progress
** Changed in: netplan
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ub
Well, this would squarely be a bind9 issue. The use of 'netplan apply'
there just means that an IP might have changed, or the state of the
interface changed enough (bringing it down, then up again, readding
static addresses, etc) that bind couldn't make sense of it.
'netplan apply' is supposed to
I can't make any sense of it. I have similar setups here; the systems
get installed (with 18.04 as well as Disco) with nvme#n#p#_crypt
devices, and those load properly.
Anything else you can add about the specifics of your system? Seems like
you used guided partitioning, just enabling disk
I've had another look; it still looks sane to me; but given that it's
network code we're importing in the bootloader, it feels like a
potential source of vulnerabilities and would be better to have it
checked by the Security team.
I've assigned it to ~ubuntu-security...
Please have a look at
** Changed in: grub2 (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787630
Title:
[
** Tags removed: verification-failed-bionic
** Tags added: verification-needed-bionic verification-needed-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790709
Title:
Backport gnu-efi 3.0.8
Yes, it's likely possible. It's actually something we've been
discussing, just need to figure out how to do it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815002
Title:
quick-boot-lvm.patch
I'm not convinced the keypress is 100% reliable. It does get better all
the time, but there are still systems on which it's just not possible to
get it working reliably, and sometimes not at all - you'll press
consistantly "too late" or "to early" and GRUB won't notice, so you
won't get the menu.
If you can still boot to Ubuntu with an older kernel (one that is
signed), here's what you can do:
1) Download http://archive.ubuntu.com/ubuntu/dists/xenial-
updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed.
2) Copy grubx64.efi.signed over
Re-verified trusty since the previous trusty comment was imprecise:
dkms 2.2.0.3-1.1ubuntu5.14.04.10
Upgrading kernel and headers follows with a loadable, properly signed
module using the MOK generated previously.
ubuntu@ubuntu:~$ dpkg -l shim-signed dkms | cat
Verification-done on xenial:
dkms 2.2.0.3-2ubuntu11.6
Upgraded kernel to hwe kernel, drivers can still be loaded from the
right versioned directory for the kernel and loads succesfully --
signature is validated fined as the kernel module is signed.
ubuntu@ubuntu:~$ dpkg -l shim-signed dkms |
Verification-done on trusty:
dkms/2.2.0.3-1.1ubuntu5.14.04.10
I've installed bbswitch on a test UEFI system, upgraded the kernel to a
newer version (ie. linux-image-hwe-trusty-generic) and was still able to
load the module in; the module in the updates/dkms directory for the
kernel version is
Verification-done on trusty:
dkms/2.2.0.3-1.1ubuntu5.14.04.10
shim-signed/1.33.1~14.04.4
I've installed bbswitch on a test UEFI system, rebooted to disable
validation in shim; then upgraded to the new packages and could verify
that shim validation was re-enabled and a MOK was enrolled in the
Verification-done on xenial:
shim-signed/1.33.1~16.04.4
dkms/2.2.0.3-2ubuntu11.6
I've installed bbswitch on a test UEFI system, rebooted to disable
validation in shim; then upgraded to the new packages and could verify
that shim validation was re-enabled and a MOK was enrolled in the
firmware,
You absolutely can change /etc/grub.d/00_header to change or remove the
code. The problem is; I don't think there is a way around us providing a
way to reach the menu for the those setups where "recordfail", the
feature that lets the boot menu start on failure, doesn't work, while
also making it
Some more questions:
- Is "Boot Order Lock" enabled on the affected system? (This is another
feature in BIOS/firmware).
- Please include the output of 'sudo efibootmgr -v'
** Changed in: grub2-signed (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
I'm unable to reproduce this. I've tried upgrading from bionic to
cosmic, or various partitioning set ups. Clearly there is something
special about some set up that can cause this kind of issue, but I'm
unsure what it could be.
Could you please tell us more about how your system was installed
** Changed in: libxmlb (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
** Changed in: libxmlb (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
MIR looks fine to me; it's a lot of code though, I'd feel much better if
it had more eyes to review. Assigning to the Security Team for a look.
It's also missing a team subscriber, but we'll fix that now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Verification-done on cosmic with grub2/2.02+dfsg1-5ubuntu8.2,
grub2-signed/1.110.2:
As expected, LVM in UEFI leads to a GRUB menu at boot, since it would
otherwise not be available. For LVMs on legacy BIOS, this does not
happen. I find this SRU is working correctly.
** Tags removed:
Verification-done on cosmic with grub2/2.02+dfsg1-5ubuntu8.2,
grub2-signed/1.110.2:
Upgrading grub in the presence of an unsigned kernel (copied existing
vmlinuz and ran 'sbattach --remove') leads to a failing upgrade, as
expected. Despite 'mokutil --export --db' returning an error "db is
empty",
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811868
@Dennis; when running the upgrade your GRUB_TIMEOUT may have been reset,
depending on what options you picked when prompted about the config
change.
Verification-done for bionic using grub2/2.02-2ubuntu8.12, grub2-signed/1.93.13:
I have run installs both with and without LVM on UEFI and on
Verification-done for bionic using grub2/2.02-2ubuntu8.12,
grub2-signed/1.93.13:
I have checked loading both signed and unsigned kernels. As expected, an
official, correctly signed kernel from the bionic archive is loaded
correctly, and a copy of the same kernel with the key removed ('sbattach
Verification-done for bionic using grub2/2.02-2ubuntu8.12,
grub2-signed/1.93.13:
I have checked that running upgrade in the presence of an unsigned
kernel leads to a failing upgrade, and if no unsigned/incorrectly signed
kernel is present the upgrade will work fine. Similarly, running
Kept a task for keepalived (Incomplete) in case it turns out there's
something we can do there.
Also added a task for systemd, since that would definitely require
development work.
Marked Invalid for netplan, as since netplan only translates config from
the YAML to what networkd or
This isn't netplan, it's systemd-networkd. Netplan only writes
configuration for the chosen renderer (in this case, systemd-networkd).
Either systemd needs to not wipe out foreign addresses (I believe there
is a PR in git for that) or keepalived should somehow interface with
systemd so they can
: In Progress => Triaged
** Changed in: gnome-remote-desktop (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Hi,
Just an advance reminder if you want to make ubiquity slideshow
changes for the Disco release: make them as soon as possible, to give
time for translators to translate them.
Kind regards,
Mathieu Trudel-Lapierre
Freenode: cyphermox, Jabber: mathieu...@gmail.com
4096R/65B58DA1 818A D123
** Description changed:
[SRU Justification]
Move to using self-signed keys for signing DKMS modules, along with the
wizard / guide to make this work properly, to let third-party modules be signed
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.
[Test case]
** Description changed:
+ [SRU Justification]
+ Move to using self-signed keys for signing DKMS modules, along with the
wizard / guide to make this work properly, to let third-party modules be signed
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.
+
+ [Test case]
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803031
Title:
error: cannot find EFI
** Also affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814575
Title:
Updates failing because "db is empty"
To manage
** Also affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2-signed (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification done with ubiquity 18.04.14.12 / partman-efi 71ubuntu2.2:
I've tried the various permutations of installing in BIOS mode, in UEFI
mode, or with UEFI with CSM enabled. All work as appropriate: when
installing in UEFI with or without CSM and no ESP is created, the user
is prompted; in
This change has been landed in bionic-proposed. As far as I can tell
it's "verification-done" -- I can succesfully install on UEFI systems no
problem, and /sys/firmware/efi/efivars is indeed mounted.
Unfortunately, I have no way to make sure it's indeed fixed since I have
never been able to
yes, you install using a recent daily. That should be enough, but
otherwise you can upgrade to the new ubiquity from -proposed.
The user needs to figure it out. We do have guided partitioning for that
reason; and the warning clearly says it's "missing an EFI System
Partition", which is one of the
** Description changed:
+ [SRU Justification]
+ There is a behavior regression on some EFI systems with specific firmwares
(right now, Lenovo, X230 and newer are known to be affected), where mokutil
--export --db returns "db is empty" and can lead to no .der certificates being
exported at all.
were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
** Affects: grub2 (Ubuntu)
Importance: High
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: Confirmed
** Changed in: grub2 (Ubuntu)
Importance
:Verification-done for cosmic:
ubuntu@superb-ram:~$ qemu-img convert vda1b.qcow2 vda1b.raw
ubuntu@superb-ram:~$ e2fsck -f vda1b.raw
e2fsck 1.44.4 (18-Aug-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking
Verification-done for bionic using e2fsprogs 1.44.1-1ubuntu1.1:
ubuntu@humble-cod:~$ qemu-img convert vda1b.qcow2 vda1b.raw
ubuntu@humble-cod:~$ e2fsck -f vda1b.raw
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking
** Description changed:
[Impact]
Any user installing Ubuntu on UEFI systems and picking manual partitioning.
This leads to an installation config that cannot be completed due to the
missing partition not being detected until grub-installer runs at the end of
the install process
[Test
** Description changed:
[Impact]
Any user installing Ubuntu on UEFI systems and picking manual partitioning.
This leads to an installation config that cannot be completed due to the
missing partition not being detected until grub-installer runs at the end of
the install process
[Test
** Description changed:
+ [Impact]
+ Any user installing Ubuntu on UEFI systems and picking manual partitioning.
This leads to an installation config that cannot be completed due to the
missing partition not being detected until grub-installer runs at the end of
the install process
+
+ [Test
ode review.
** Changed in: pipewire (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
** Changed in: pipewire (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ub
Please also make sure to set a bug subscriber...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
Indeed, but we should really be catching these errors earlier, when the
installer is running and the user is partitioning.
Adding a task for partman-efi.
** Also affects: partman-efi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Verification-done on cosmic with grub2 / grub2-signed.
Forcing an unsigned copy of the kernel, or one signed by an unknown key
leads to the system failing to upgrade, as expected:
ubuntu@ubuntu:~$ dpkg -l grub-efi\* | grep ii | awk '{ print $2" "$3 }'
grub-efi-amd64 2.02+dfsg1-5ubuntu8.1
Verification-done on cosmic with grub2 / grub2-signed:
ubuntu@ubuntu:~$ dpkg -l grub-efi\* | grep ii | awk '{ print $2" "$3 }'
grub-efi-amd64 2.02+dfsg1-5ubuntu8.1
grub-efi-amd64-bin 2.02+dfsg1-5ubuntu8.1
grub-efi-amd64-signed 1.110.1+2.02+dfsg1-5ubuntu8.1
ubuntu@ubuntu:~$ sudo update-grub
Verification-done on cosmic for grub2 / grub2-signed:
ubuntu@ubuntu:~$ dpkg -l grub-efi\* | grep ii | awk '{ print $2" "$3 }'
grub-efi-amd64 2.02+dfsg1-5ubuntu8.1
grub-efi-amd64-bin 2.02+dfsg1-5ubuntu8.1
grub-efi-amd64-signed 1.110.1+2.02+dfsg1-5ubuntu8.1
Menu shows as expected, since the
Verification-done for bionic with grub2 / grub2-signed:
ubuntu@ubuntu:~$ dpkg -l grub-efi\* | grep ii | awk '{print $2" "$3 }'
grub-efi-amd64 2.02-2ubuntu8.10
grub-efi-amd64-bin 2.02-2ubuntu8.10
grub-efi-amd64-signed 1.93.11+2.02-2ubuntu8.10
GRUB correctly shows the menu at every boot when the
Verification-done on bionic with grub2 / grub2-signed:
iF grub-efi-amd64 2.02-2ubuntu8.10 amd64 GRand Unified Bootloader, version 2
(EFI-AMD64 version)
ii grub-efi-amd64-bin 2.02-2ubuntu8.10 amd64 GRand Unified Bootloader, version
2 (EFI-AMD64 binaries)
ii grub-efi-amd64-signed
Verification-done on bionic with grub2 / grub2-signed:
iF grub-efi-amd642.02-2ubuntu8.10 amd64GRand Unified
Bootloader, version 2 (EFI-AMD64 version)
ii grub-efi-amd64-bin2.02-2ubuntu8.10 amd64GRand Unified
Bootloader, version 2 (EFI-AMD64 binaries)
Verification-done for trusty for grub2 and grub2-signed:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Verification-done on trusty with grub2 2.02~beta2-9ubuntu1.16 /
grub2-signed 1.34.18:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
** Also affects: e2fsprogs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: e2fsprogs (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+ - Users resizing filesystems using resize2fs.
+ - Resizing an existing Linux
*** This bug is a duplicate of bug 1798562 ***
https://bugs.launchpad.net/bugs/1798562
** This bug has been marked a duplicate of bug 1798562
After a side by side installation, resized filesystem is corrupted
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Yes, absolutely. In fact, I fixed this already:
$ ~/bin/netplan --root-dir=scratch/ --debug generate
DEBUG:command generate: running ['/lib/netplan/generate', '--root-dir',
'scratch/']
** (generate:18683): DEBUG: 16:41:58.422: Processing input file
scratch//etc/netplan/01-my_network.yaml..
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification be
As an update to this:
I think we agreed (in a short meeting between people involved in curtin,
cloud-init, grub2, etc.) that installers are indeed meant to be
authoritative on writing /etc/default/grub.
One work item that came out of this was to at the very least make it
clear what files are
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Fix Released
** Changed in: grub2 (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Package looks good to me (aside from the security review that still
needs to be done). MIR tentatively approved (we'll change the state to
denote this once the security review is done).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ Any user who wants to understand how /boot/grub/grub.cfg is being generated.
This is especially useful on dynamically-deployed systems (ie. using MAAS,
cloud-init) on clouds or datacenter deployments.
+
+ [Test case]
+ 1) Run 'update-grub'
+ 2) Verify that
** Description changed:
+ [Impact]
+ This affects UEFI users upgrading grub, especially when upgrading from an
earlier release or when using custom kernels (signed by PPA keys, or unsigned).
+
+ [Test case]
+ 1) Install a custom / PPA kernel, or copy an existing kernel into an unsigned
version
** Description changed:
+ [Impact]
+ This issue makes it impossible for UEFI users to access to boot menu and
choose their kernel if /boot is installed on LVM.
+
+ [Test case]
+ 1) Install Ubuntu on UEFI; put /boot on a LVM LV.
+ 2) Reboot after the install
+ 3) Verify that you will get a GRUB
I'm doing the MIR team review in parallel with the security review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812858
Title:
[MIR] libimagequant (dependency of pillow)
To manage notifications
Public bug reported:
It's really hard to debug what happens to generate grub.cfg -- no way to
know what files (from /etc/default/grub, /etc/default/grub.d/*) are
being used in which order.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Changed in: grub2
Fixed in 2.02+dfsg1-5ubuntu9 in disco.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812863
Title:
No way to debug grub.cfg generation
To manage notifications about this bug go to:
Testing looks good; removing block-proposed.
Kernels are checked as expected, a custom kernel signed with a custom
but known key is let through.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Confirmed => In Progress
** Changed in: gnome-remote-desktop (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: pipewire (Ubuntu)
Status: Confirmed => In Progress
** Changed in: pipewire (Ubuntu)
Importance: Undecided => Critical
** Changed in: pipewire (Ubuntu)
Importance: Critical => Low
** Changed in: pipewire (Ubuntu)
Assignee: (unassigned) => Mathieu Tru
Adding block-proposed for one last test run in -proposed.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789918
Title:
grub2 signed kernel enforcement doesn't check
It is indeed a typo, I copy-pasted the previous comment about
verification (since it was the exact same thing, but indeed verified
with 1.33.1~16.04.3+15+1533136590.3beb971-0ubuntu1 which includes the
added depends for grub2.
--
You received this bug notification because you are a member of
Doesn't look like a grub bug anymore. We can set back to New if
necessary.
** Changed in: grub2-signed (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/1811722
** Changed in: grub2 (Ubuntu)
Status: Triaged => In Progress
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been working on fixing this; code is here:
https://code.launchpad.net/~ubuntu-core-
dev/grub/+git/ubuntu/+merge/361589
I'll finish testing that it all works correctly, installing unstable
kernels, and then upload to disco and proceed with preparing the SRUs.
--
You received this bug
401 - 500 of 8586 matches
Mail list logo
