Thank you for your opening of this bug, but this issue has already been resolved by 3.13.0-36 please see bug 1368245 for more information.
Thank you for your opening of this bug, but this issue has already been resolved by 3.13.0-36 please see bug 1368245 for more information.