Upstream the leaning is this is a firmware implementation issue not a
fwupd bug, so there is nothing fwupd can do about it today. If from
some evidence or discussion that changes later we can re-open the issue.
** Changed in: fwupd (Ubuntu)
Status: Triaged => Invalid
--
You received
Thanks for the details and also reporting upstream!
** Changed in: fwupd (Ubuntu)
Importance: Undecided => High
** Changed in: fwupd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Forwarded upstream to https://github.com/fwupd/fwupd/issues/3186
** Bug watch added: github.com/fwupd/fwupd/issues #3186
https://github.com/fwupd/fwupd/issues/3186
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
