Comment 17 for bug 1823608

Seth Hillbrand (sethh) wrote :

This has already been fixed in 5.1.2