Comment 11 for bug 1401623

Christopher, it is unlikely that any automated tool is ever going to capture this bug any more than it already has. It is much more beneficial to find out why it might NOT happen, than why it DOES happen. What's more, is that it seems that this bug is in the proprietary driver upstream... So the most helpful thing we could do to get this fixed, is to show how many people are affected.

Because the current way of doing things does not in any way show how many people are affected, the current way of doing things will simply not help. It is utterly flawed, and those articles don't help to address this matter. For one thing, those articles are written with crashes and bad behavior within open source software in mind - neither of which is the case here.