On Fri, 2004-08-20 at 05:51, Mike Hommey wrote: > > I'm impressed with the amount of energy you've put into tracking this > bug, but you should have read history of the bugs merged with yours... > Especially > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216933&msg=63
I read this one. In a matter of fact, I started to really hunt the bug after reading this one, mainly because it was way too imprecise to do something with it (for example we don't know what cache we are speaking about, we have no idea of where is located the problem in the Xserver, and so on). I feel much more knowledgeable with my explanation than with this one. Moreover, I have some "evidences" that the CMS is involved (like the fact that running a copy of the Xserver is free of bug). The problem is now: What to do ? We cannot really access to the CMS and this bug seems to appears only from time to time in very special conditions. Regards -- Emmanuel Fleury Computer Science Department, | Office: B1-201 Aalborg University, | Phone: +45 96 35 72 23 Fredriks Bajersvej 7E, | Fax: +45 98 15 98 89 9220 Aalborg East, Denmark | Email: [EMAIL PROTECTED]
