Comment 17 for bug 314263

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This has been fixed properly upstream now.