Just to let you know that this issue has now sorted as of Stable Channel updates release 3.9.2-53:
Apologies for it taking so very long to get around to this and thanks again for your original report that brought this issue to light. It only affected a very few devices but at least those few should be good to go now.