Another point to note when you “update the bugs site with whatever information I do find”. @hexadecagram seems to be able to repro and mentioned they intent to try to handle this. It possibly doesn’t make sense to add anything at this point, unless that’s really something ground-breaking.
Anyway: when there’s some problematic bug where there is some problem easily observable by some users, but devs can’t repro on their systems, it usually gives little to add “I see it by doing these steps”: more important is to find out the details of system/program configuration that is likely the reason why it is easily repro on some systems, and not on others (it could be locale, or installed system update packages, or programs running in parallel such as clipboard managers, or … hundreds of possibilities, but that is often the crucial piece that is making some bugs hang unfixed for decades without any hope, until one day, some developer happens by chance to come across such a constellation).
