Comment 15 for bug 1387949

@Selene

Sorry for updating the status without a comment. I think my intention was to get this re-tested on a current image and see if it was still reproducible.

Looks like Simon has commented about kernel changes that may address the original issue, so re-assigned to him.