Comment 5 for bug 1720223

Oh, hello!

The problem is Xwayland is single-buffered; it only ever allocates a single wl_buffer and repeatedly wl_surface.attach()es it.

The problem here is that we tie the frame callback to the MirBuffer, and only submit the frame callbacks when we first construct the MirBuffer. Since the compositor never releases the MirBuffer we never construct a new one, and so all subsequent frame callback requests are ignored.

Bah.