Comment 2 for bug 1842502

Chris Johnston (cjohnston) wrote :

Setting back to new since this is a known upstream issue.