home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x
- Path: sparky!uunet!gatech!bloom-beacon!INTERNET!dont-send-mail-to-path-lines
- From: dan@watson.ibm.COM (Walt Daniels)
- Subject: Debugging keyboard grab problems
- Message-ID: <072892.113852.dan@watson.ibm.com>
- Sender: daemon@athena.mit.edu (Mr Background)
- Organization: The Internet
- Date: Tue, 28 Jul 1992 15:38:52 GMT
- Lines: 12
-
- One of our users occationally gets hung in a state where it looks like
- the keyboard is grabbed by someone, i.e. the clock updates, you can
- popup a new day window from xcalendar, etc. but you can't type in any
- window. You can't perform any window manager functions (Motif).
-
- The first attempt at debugging was to kill windows individually and test
- if the grab was still in effect. Unfortunately it was until all the windows
- were killed. So my assumption is that the server somehow got the bit
- set and there is no mechanism to clear it.
-
- So the question is: How do you find the culprit that set the bit?
-
-