Comment 6 for bug 1952158

Thanks for the further investigation, amk. And thanks for following up with upstream. We will track the progress of their bug and act accordingly (likely backporting a patch to fix the issue).