Comment 4 for bug 543872

Revision history for this message
MarcRandolph (mrand) wrote :

The developer believes that this issue is likely fixed in a later version than what you are running. If you still have this problem after updating, we'd need a new stack trace, which would imply opening a new ticket. Therefore I'm going to close this one.