Re: FVWM: BadAccess Xerrors with XGrabButton()

From: Charles Hines <>
Date: Tue, 28 Nov 1995 16:38:44 -0500

>>>>> "Jeremy" == Jeremy Payne <jeremy_at_yosemite.npa.uiuc.edu> writes:

Jeremy> Has anyone else seen any problems in clients calling
Jeremy> XGrabButton or XGrabPointer under fvwm? Whenever any client
Jeremy> managed by fvwm calls eg. XGrabButton() it reliably fails with
Jeremy> a BadAccess XError (for me at least). Notably proctool
Jeremy> (solaris) and recent beta versions of netscape seem to do
Jeremy> this, as well as my own code making similar calls.

Under AIX I've used the latest beta netscape and not seen this problem
(nor with any other programs).

Jeremy> I'm running the 3.4 sun openwindows dps server with fvwm
Jeremy> 2.0.39, but I get this behavior regardless of which server I
Jeremy> run (behaves same with X11R6/fvwm) -- it seems to only happen
Jeremy> when I use recent fvwm 2.x versions, not with any other window
Jeremy> managers (olwm, twm, mwm). If nobody else has seen this I'll
Jeremy> try to track down what may be causing it in the code, but it'd
Jeremy> be nice to get any insights anyone may have first...

As I said, I don't see this, but I can take a guess at what's
happening here. Here is an excerpt from the XGrabButton man page:

     If some other client has already issued the XGrabButton function
     with the same button/key combination on the same window, a
     BadAccess error results.

So, my guess is that you have a 'Mouse' line in your .fvwm2rc that is
conflicting with what these programs would like to do, perhaps like
so:

Mouse 1 W N Raise

I'm not 100% certain if this is really your problem, but you could use
it as a starting point for you investigation.

Chuck
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Nov 28 1995 - 15:39:06 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:57 BST