XQueryBestCursor behaviour difference between XMir and X

[Tom Hindle]

Testing on Ubuntnu 14.04 with Mir enabled.

The following call to XQueryBestCursor returns a width and height of 0.

XQueryBestCursor(dis, d, 32, 32, &width_return, &height_return);

Whereas when not using Mir it returns a width and height of 32.

I've attached a simple X11 application that shows the difference. (or it can be seen here https://bitbucket.org/hindlemail/x11testapplication/src/adaba4419fcaec3e9031223b43f0e62f6593a578/main.c?at=default)

This difference prevents all mono winforms applications from running. (Including something as simple as showing a message box).

[Tom Hindle (3-launchpad-hindlemail-co-uk)]

XQueryBestCursor seems to just be returning what is set by xf86_cursors_init

I see that in 14.04 xorg-server is patched by xmir.patch. The xmir_screen_init function added by xmir.patch calls xf86_cursors_init(screen, 0,0,0)

I assume calling xf86_cursors_init(screen, 64,64,0) will fix the problem.

However I'm a bit confusted about which repo contains the latest xmir.patch file.
The xmir.patch in 14.04 shown by "apt-get source xorg-server" differs from the xmir.patch shown in lp:ubuntu/xorg-server. (And in the bzr history I can't see any place when xf86_cursors_init(screen, 0,0,0) is either added or removed).

[Robert Ancell (robert-ancell)]

Closing as this relates to the old XMir. Please re-open if this still occurs in newer versions.