Comment 8 for bug 1717667

Revision history for this message
Mario Limonciello (superm1) wrote :

@bigon had confirmed that 1.0.0 did fix it, which is now in master. According to github #259 the patch linked in comment #7 on top of 0.9.x didn't fix it however, so it could have been a combination of other items in master that had actually fixed the issue.