On Fri, 2006-01-27 at 05:52 -0800, jerry bookter wrote:

X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2a00002 (or another number) ...As well as a few others but one thing at a time. As far as I can tell the error doesn't cause any harm, but it just bothers me. Is there anything I can do to fix it?

It's an error from the X server, telling you that an application has done something wrong. It's very likely a bug in the application or in a display library that the application uses. A quick google suggests it might possibly be a library problem to do with dialog box management. Trying to do anything about it is liable to be complicated, time-consuming and unproductive. Things to try might be: (1) Upgrade to the latest version of everything in the hope the problem has already been fixed. And/or try to identify which application is causing the error: (2) Search in other error logs - including application logs, increasing log levels if necessary (3) Keep a continuous watch on X.err (tail -f) so you can see which application you're using when the problem occurs. (4) Identify the application from the X error log. It's been a very long time since I last debugged X, but IIRC the log identifies the responsible process (via the resource id and a chain of requests?). Again, you may need to increase the log level. When you've identified the application, you'll be in a better position to google for reports of the problem. BTW, you may do better asking this question on an X-specific list. Cheers, Dave