"fails to request state" when trying to perform actions in mokutil
Bug #1560764 reported by
Mario Limonciello
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
mokutil (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Recently it's been observed that mokutil is unable to make changes to the various Mok* variables. It complains that "fails to request state" when trying most actions or similar errors.
The root of these problems is because the variables have been set as immutable after this kernel commit:
https:/
In many instances mokutil 0.2 will delete the variable and recreate it, so changing it with chattr isn't a workable solution as the kernel will just recreate it with the immutable attribute and it will fail over again.
summary: |
- "fails to request state" when trying to perform actions + "fails to request state" when trying to perform actions in mokutil |
Changed in mokutil (Ubuntu): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
Alternatively it seems that this might be fixed by moving to mokutil 0.3. Mokutil 0.3 has switched over to use libefivar (https:/ /github. com/lcp/ mokutil/ commit/ 7b49e8342846595 27c9f7cf554f223 748c00564b). libefivar has handling for immutable variables since version 0.22 (https:/ /github. com/rhinstaller /efivar/ commit/ df78c364a1d3626 55f5495e781b647 553b5ae144).