No, it seems the specific hardware causing the issue was mentioned in the bug report.