Comment 10 for bug 406650

Revision history for this message
Matthias Radestock (matthias-lshift) wrote :

As noted in comment #8, this bug has been fixed in the upstream 1.7.0 release. I am unsure how this should be reflected in the status.