Comment 21 for bug 1302080

Revision history for this message
Tore Anderson (toreanderson) wrote :

As I've mentioned in my previous three comments, this bug is *not* fixed. It has been erroneously marked as fixed. Can someone with the appropriate access please re-open it? Otherwise I suppose I'll just have to submit a new duplicate issue.