Comment 2 for bug 1751403

Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

Turns out this has already been fixed upstream. Here's the correct bug report.