Is this the same as bug 1154870, which describes an almost identical issue but hasn't been closed as a duplicate?
Is this the same as bug 1154870, which describes an almost identical issue but hasn't been closed as a duplicate?