Comment 40 for bug 1856608

@mruffell: Is there any specific info you'd like people to continue to capture if they see this symptom? If so, maybe we put those steps in the Description.

I also wonder if this bug has become too unwieldly due to the number of reports w/ likely different underlying causes, that we can never really call it "closed" - esp. since the original report was truly a hardware issue.