group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #14670
[Bug 1680279] Re: attach secureboot state files to shim-signed apport reports
** Changed in: shim-signed (Ubuntu Xenial)
Status: Fix Released => Fix Committed
** Tags removed: verification-done-xenial
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1680279
Title:
attach secureboot state files to shim-signed apport reports
Status in shim-signed package in Ubuntu:
Fix Released
Status in shim-signed source package in Xenial:
Fix Committed
Status in shim-signed source package in Yakkety:
Fix Committed
Status in shim-signed source package in Zesty:
Fix Committed
Bug description:
[SRU Justification]
I'm asking the same questions repeatedly of bug submitters about the state of secureboot on their systems, so we should just include these files in the apport hook. Since shim-signed changes in stable releases for policy reasons, this should be SRUed back in as well.
[Test case]
1. Install the shim-signed package from -proposed
2. Run apport-bug shim-signed
3. Confirm that the apport collection succeeds
4. Verify that the report to be sent includes keys for two files under /sys/firmware/efi/efivars and for /proc/sys/kernel/moksbstate_disabled
[Regression potential]
If I done messed up, we could fail to get bug reports about shim that we really need.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1680279/+subscriptions