Comment 1 for bug 229360

Revision history for this message
Jonathan Davies (jpds) wrote :

I believe that this has been fixed in the new upstream release (1.2.3 onwards). This update is currently awaiting upload at bug #229360.