https://bugs.winehq.org/show_bug.cgi?id=33479
--- Comment #38 from Forest winehq@tibit.com --- Created attachment 49192 --> https://bugs.winehq.org/attachment.cgi?id=49192 log from Sebastian Lackner's patch test
(In reply to Sebastian Lackner from comment #35)
I suspect that this problem occurs when a WM_X11DRV_CLIP_CURSOR message is interpreted incorrect. Does this patch help?
If not, could someone please attach a log with:
WINEDEBUG=+tid,+cursor,+event,+x11drv
That patch does not help in Guild Wars 2.