At this point, this is not a problem I can fix. It's very much tied to
their hardware, and to the kernel on that hardware. This is the only
instance of this I have ever seen, anywhere, over literally thousands of
test runs, and it is very easily reproduced manually by simply catting
the efi variable for SecureBoot, so it exists outside the test suite.
I've added a kernel task, if there's any fix to be had here, it would
have to occur there.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: plainbox-provider-checkbox
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/1896119
Title:
Catting the SecureBoot efivar in /sys hangs
To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1896119/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
