Comment 19 for bug 1515791

@Francesco Ongaro:

That appears to be another issue, unrelated to the bug in the description. Also supported by the amount of people that have reported success on this with the workaround. I suspect it is related to the hardware you're using. Please open a new bug report instead, I'd say.