Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 462678

Summary: Applications does grab without doing ungrab, locking the display
Product: Red Hat Enterprise Linux 5 Reporter: Göran Uddeborg <goeran>
Component: openmotifAssignee: Thomas Woerner <twoerner>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: alanm, mnowak, pknirsch, syeghiay, tao
Target Milestone: beta   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 22:17:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Test program to trigger the bug none

Description Göran Uddeborg 2008-09-18 08:44:12 UTC 
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.
Comment 1 Thomas Woerner 2008-09-23 15:45:52 UTC 
There will be an OpenMotif rebase to 2.3.1 for EL-5.3. The 2.3.1 version already contains the fix.
Comment 2 Phil Knirsch 2008-09-24 11:58:04 UTC 
See comment #1, proposing for RHEL-5.3 with exception and granting Devel ACK.

Thanks,

Read ya, Phil
Comment 12 errata-xmlrpc 2009-01-20 22:17:05 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0247.html