Comment 21 for bug 410475

Revision history for this message
C de-Avillez (hggdh2) wrote :

@Wayne: The bug was still marked as private due to the stacktraces. I looked at them, and did not see anything warranting a Private status, so I reset it. You can now access it.

Sorry for that, but sometimes stacktraces do contain private data, and we try to be careful on them.