Bug 430175

Description of problem:
Object within graphics applications do not display at
the proper location on the screen.

Graphics app#1 displays three windows when launched:  the main graphics window,
a command window (below the graphics window) and a third window (to the right of
the graphics window) that displays pressure gradients.  When a user manipulates
the object in the graphics window (rotate, zoom) the pressure gradient window to
the right refreshes but is supposed to stay at its current position.  What
happens is that as soon as the graphics object is manipulated, the pressure
gradient window shifts to the top,left corner of the screen.  If you drag the
window back to the right side of the main graphics window and go to manipulate
the object again, it immediately shifts back to top,left.

The second problem occurs with two different applications that have the same
capability in that you have a main graphics window with an object displayed. 
You can select two points on that object and request the programs to draw a line
between those points and calculate the distance between those two points and the
programs will display the distance value on the line drawn between those two
points.  While the line is drawn properly between those two points, the distance
value shows up in a different region of the screen totally unrelated to either
data point or the line drawn between them.

Version-Release number of selected component (if applicable):
2.8.6-2.13

How reproducible:
100% of the time

Steps to Reproduce:
1. Third-party and internal graphics apps needed to demonstrate problem.
2.
3.
  
Actual results:
As documented above, objects appear in unexpected
regions of the screen or graphics display window.

Expected results:
In case #1, graphics window should not change position
on screen when refreshed.  In case #2 and 3, the
calculated value should be displayed neighboring line
drawn and not in an unrelated portion of the graphics
display window.

Additional info:
We have downgraded metacity back to 2.8.6-2.11 (but
retained all other packages that are part of the
RHEL WS 4.6 release) and all graphics applications
are working properly again.  The 2.8.6-2.13 release
of metacity is the trigger that is causing the abnormal
display behavior.