Comment # 23 on bug 954108 from Egbert Eich

I'd prefer if we can come up with a real solution.
In many cases this is someone calling ProcXFixesHideCursor() in the Xserver but
forgetting to call ProcXFixesShowCursor(). 
I could easily build a server which spits out the info needed to come closer to
the cause in the log, however if this isn't the culprit, debugging becomes a
bit messier. 
It involves attaching gdb to the Xserver from a remote machine, breakpointing
on some cursor functions in the driver and waiting for this to happen.