Comment 3 for bug 45927

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

This issue has been fixed in the upcoming 1.0.6 release.