[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package grub2 - 2.02+dfsg1-5ubuntu8.2 --- grub2 (2.02+dfsg1-5ubuntu8.2) cosmic; urgency=medium [ Mathieu Trudel-Lapierre ] * debian/grub-check-signatures: properly account for DB showing as empty on some broken firmwares: Guard against mokutil

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-08 Thread Mathieu Trudel-Lapierre
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",

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-08 Thread Launchpad Bug Tracker
This bug was fixed in the package grub2 - 2.02-2ubuntu8.12 --- grub2 (2.02-2ubuntu8.12) bionic; urgency=medium * debian/grub-check-signatures: make sure grub-check-signatures conserves its execute bit. grub2 (2.02-2ubuntu8.11) bionic; urgency=medium [ Mathieu

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-08 Thread Launchpad Bug Tracker
This bug was fixed in the package grub2-signed - 1.93.13 --- grub2-signed (1.93.13) bionic; urgency=medium * Rebuild against grub2 2.02-2ubuntu8.12. grub2-signed (1.93.12) bionic; urgency=medium * Rebuild against grub2 2.02-2ubuntu8.11. (LP: #1401532) (LP: #1814403) (LP:

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-08 Thread Mathieu Trudel-Lapierre
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

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-07 Thread Steve Langasek
Hello Mathieu, or anyone else affected, Accepted grub2-signed into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.93.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-07 Thread Steve Langasek
Hello Mathieu, or anyone else affected, Accepted grub2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-05 Thread Mathieu Trudel-Lapierre
** 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

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-05 Thread Brian Murray
Hello Mathieu, or anyone else affected, Accepted grub2 into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2/2.02+dfsg1-5ubuntu8.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-05 Thread Mathieu Trudel-Lapierre
** 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.

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-04 Thread Launchpad Bug Tracker
This bug was fixed in the package grub2 - 2.02+dfsg1-5ubuntu11 --- grub2 (2.02+dfsg1-5ubuntu11) disco; urgency=medium [ Mathieu Trudel-Lapierre ] * debian/grub-check-signatures: properly account for DB showing as empty on some broken firmwares: Guard against mokutil --export

[Bug 1814575] Re: Updates failing because "db is empty"

2019-02-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2 (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/1814575 Title: