http://bugs.winehq.org/show_bug.cgi?id=27779
--- Comment #95 from Alexey Loukianov mooroon2@mail.ru 2011-11-06 12:34:19 CST --- Actually the condition there is correct at what it had been targeted for: it either propagates changes immediately to X11 in case cursor had changed between calls to SetCursor or rate-limits propagation in case SetCursor are being frequently called with the same cursor handle. Using && in that construction would be wrong. I'm thinking about try to debug today or tomorrow why does the problems with fullscreen cursor only arise in case XI2 is used.
Thankfully I've been able to get Steam starting up and more-or-less working under debugger (I use OllyDbg as my prefered debugger for Win32) and it generally works with non-HW (int 3) breakpoints set in some of Steam modules and inside Wine DLLs. Thus it is possible to do advanced trace tasks without hacking-in anything in Wine sources.