By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 297

Summary:	[stdout/stderr] Numerous "X Error: BadWindow" and "X Error: BadAccess" Messages
Product:	TDE	Reporter:	Darrell <darrella>
Component:	system	Assignee:	Timothy Pearson <kb9vqf>
Status:	NEW ---
Severity:	normal	CC:	bugwatch, darrella
Priority:	P1
Version:	3.5.13.x [Trinity]
Hardware:	All
OS:	All
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Darrell 2010-10-01 16:57:39 CDT

For many years the following types of error messages have plagued KDE, and now Trinity:

X Error: BadWindow (invalid Window parameter)
X Error: BadAccess (attempt to access private resource denied)

Anybody using Trinity has seen these superfluous messages in their xsession log. The messages are annoying and evidence of sloppy coding.

The error messages do not appear in other desktops such as Xfce. The problem seems unique to legacy KDE/QT3 code.

Solving this problem would be great news for Trinity users everywhere.

Comment 1 Timothy Pearson 2010-10-01 17:08:54 CDT

(In reply to comment #0)
> The error messages do not appear in other desktops such as Xfce. The problem
> seems unique to legacy KDE/QT3 code.

A note to any developer who comes across this bug: from what I can tell, the BadWindow errors do not come from within Trinity, but rather from a malfunctioning segment of Qt3 code.  This problem would obviously be resolved if the TQT interface were enhanced to support Qt4, so I would suggest that any experienced Qt developers concentrate their efforts on the TQT interface.

Comment 2 Darrell 2012-03-10 20:06:39 CST

Now that some of the stderr messages have identification prefixes, occasionally I notice messages like this:

[kinit] TDE detected X Error: BadWindow (invalid Window parameter) 3

At one time somebody added an error trap in the kinit code. I don't know whether this new information helps. :)

Comment 3 Darrell 2012-03-10 20:51:17 CST

I might have run into another clue: the BadWindow errors seem to occur when closing certain windows. A repeatable example is starting ktip and then closing.

Other repeatable examples include kpdf and kfind. Closing either causes the error messages.

The common action seems to be closing a window triggers the error messages. Perhaps those apps causing the error messages use the same mechanism for closing and those that do not cause the errors use a different mechanism for closing.

I hope this helps!