Created attachment 317049 [details]
Test program to trigger the bug

Description of problem:
There is a bug in OpenMotif regarding handling of Grab/Ungrab events that have been queued while the application is busy doing something else.  The bug is that OpenMotif currently will make the Grab event succeed (by resetting the time to current time if first call fails), while it will allow the Ungrab event to fail; the result is that the application wrongly ends up in a Grab state.

Version-Release number of selected component (if applicable):
openmotif-2.3.0-0.5.el5

How reproducible:
Every time

Steps to Reproduce:
1. Compile the attached test program: cc motifhang.c -o motifhang -lXm
2. Run it: ./motifhang
3. Press the File->Delay menu entry
4. Within 5 seconds, press the File menu button twice (or any EVEN number of times)
5. After the 5 seconds have passed, press the Click button

Actual results:
The display is now effectively locked.  The cursor is in the menu mode.

(Kids, if you try this at home, make sure you have the AllowClosedownGrabs and/or AllowDeactivateGrabs options activated in your X server first. :-)

Expected results:
Nothing special should happen.

Additional info:
This is recently fixed in upstreams: http://bugs.motifzone.net/show_bug.cgi?id=1328  (The motifzone bugzilla does not seem to be in the menu for external bug references.)  What we need is that fix applied to the RHEL package.