This bug is one that not everyone is seeing, in fact as of last weekend we had 8 confirmed reports so the bug as reported is NOT that widespread. That does not mean this is not important especially to those who see the problem and who have reported it in order to get it fixed. Given that reported occurences are sparse ANY occurence in the wild outside of test is interesting not because we don't have a good belief that its fixed, but RATHER because the more data we have that proves it is fixed the better off we all are! If that means soliciting test data from users are you saying thats a bad thing to do so? Involving users where practical I think is important to ensuring difficult to reproduce problems are solved. Getting involved in tortured discussions about the intent of asking for assistance where practical seems unhelpful.