Comment 2 for bug 662630

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Maybe confirmed this too fast. It may in fact be a duplicate of bug 209900. The descriptions are different, but perhaps fixing that bug would fix this bug also?