attach secureboot state files to shim-signed apport reports
Bug #1680279 reported by
Steve Langasek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
shim-signed (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Committed
|
Undecided
|
Unassigned | ||
Zesty |
Fix Released
|
Undecided
|
Unassigned |
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/
[Regression potential]
If I done messed up, we could fail to get bug reports about shim that we really need.
Changed in shim-signed (Ubuntu): | |
status: | New → Fix Released |
Changed in shim-signed (Ubuntu Xenial): | |
status: | Fix Released → Fix Committed |
tags: |
added: verification-needed-xenial removed: verification-done-xenial |
To post a comment you must log in.
Hello Steve, or anyone else affected,
Accepted shim-signed into yakkety-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ shim-signed/ 1.28~16. 10.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!