Comment 4 for bug 511601

Revision history for this message
Gary van der Merwe (garyvdm) wrote :

There is now a new upstream release (0.5.1) that should fix this.