after some more commentary from the customer, I'm still not convinced
that this isn't related to the hardware itself, HOWEVER, while doing a
bit more deubgging I noticed that the boot_mode_test.py script opens
files but does not properly close them (expecting python to close them
on exit?)
So while this may or may not resolve the hang that was reported when the
secureboot test runs, I can at least fix this a bit so that we properly
close the files after reading them.
** Changed in: plainbox-provider-checkbox
Status: Invalid => Incomplete
** Changed in: plainbox-provider-checkbox
Status: Incomplete => Fix Committed
** Changed in: plainbox-provider-checkbox
Status: Fix Committed => In Progress
** Changed in: plainbox-provider-checkbox
Importance: Undecided => Medium
** Changed in: plainbox-provider-checkbox
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: plainbox-provider-checkbox
Milestone: None => 0.57.0
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
