Comment 4 for bug 1748260

Revision history for this message
Kathy Lussier (klussier) wrote :

Has anyone been able to confirm that this problem is indeed fixed after 3.0.3?