Comment 7 for bug 2009863

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for updating the bug to let us know.

Unfortunately, there's nothing much we can do on our end to prevent this from happening again next time we are required to do a version upgrade. Thankfully, it looks like this is fixed upstream in 4.16, so hopefully this will be the last version to expose this unfortunate behaviour.

I am closing this bug report.