Comment 10 for bug 1954762

A few days ago an Xorg update came in. After this update, the problem hasn't presented itself again. Therefore, I think we can consider this bug now resolved. Many thanks to Daniel and Brian for taking a look at it.