Bug #281993 has a fix now, apparently, it may be worth checking if the same logic would help fix this one.
Bug #281993 has a fix now, apparently, it may be worth checking if the same logic would help fix this one.