Comment 2 for bug 567434

Revision history for this message
Ner0lph (ner0lph) wrote :

Apparently it's fixed, cf. bug #565810.