Comment 10 for bug 1391975

Actually I can't see any reason for this now, other than a bug in Mesa/radeon driver.

Your new screenshot appears to show a block that is correctly 64px wide. It could be the driver is scanning out with 2x the correct stride, because the driver appears to know the correct width and height.

Can you please:
1. test X for a valid cursor (and attach the Xorg)
2. test mir_demo_server_shell
3. Run es2_info and attach the output
4. Verify you were testing the correct binary (freshly built mesa/libmirplatform{3,4}driver.so and not accidentally loading the old one).