Comment 9 for bug 1630285

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Somehow this appears to have possibly landed in xenial without undergoing the verification expected (which might explain why it was still in New, rather than Fix Committed).

I have set this back to Fix Committed for xenial, and re-did the verification. As above, verification was limited to making sure the workaround was present, since there is no hardware available to me to run the test with.