Closing this as the issue will be tracked using BZ 1098025 in upstream and 1096729 in downstream. *** This bug has been marked as a duplicate of bug 1096729 ***