On 20 Jul 2003, Mike Hearn wrote:
I'm also having unrelated issues since I ran a cvs update *grr*, I can no longer click on anything, nor use the keyboard. The mouse cursor doesn't change when I move the mouse over it, and an x11drv trace shows it processing no events *at all* given input.
I hope this isn't actually CVS that's borked for everybody, but I can't really see what might have broken it :(
hi, Mike
i was "lucky" enough to get into such situation, once: http://www.winehq.org/hypermail/wine-devel/2003/07/0229.html
as no-one have responded to this, i decided to do: su -c "make uninstall"; make clean; tools/wineinstall
this helped :) hence, the question arises: why is it bad to just do "make uninstall", cvs update and "tools/wineinstall" after, sometimes?
BTW: sometimes i am forgetting to kill all wine processes, so wine (with any combination of cmd-line) just outputs 0 bytes and quits. maybe that is a indication of a problem. should wineinstaller kill running wines before overwriting old executable file(s) or even before doing some checks?