Comment 1 for bug 490162

Revision history for this message
Joe Daly (skinny.moey) wrote :

I updated to 2.1.0b3 and this problem went away. This should probably be marked as fixed or invalid. Ill leave it up in case someone recognizes the problem as being fixed.