[Bug: 21.4.12] xemacs: X Error of failed request: BadWindow(invalid Window parameter)

[Darryl Okahata]

tbennett at nvidia.com wrote:

> Ok, here it is.  Could not quickly get it to exit() when using
> (x-debug-mode t), but it did produce the error msg reliably.

This is weird (but I'm not familiar with the code):

* The stack trace is strangely recursive: execute_internal_event() gets
  recursively called five times, mostly via wait_delaying_user_input().

* Selections are involved.  I seem to recall that there are issues with
  selections, X, and/or Motif.  I have the following in my init.el, and
  you might want to see if these make a difference for you:

    ;; Setting this to nil dramatically improves responsiveness when
    ;; killing text.  If x-selection-strict-motif-ownership is non-nil,
    ;; the clipboard is "owned in the Motif Way", which generates a
    ;; sh*tload of X protocol traffic, but insures that cut and paste
    ;; works correctly.  If x-selection-strict-motif-ownership is nil, the
    ;; amount of protocol traffic is greatly lessened, but cut-and-paste
    ;; may not always work correctly with Motif widgets.
    ;(setq x-selection-strict-motif-ownership nil)

    ;;; Similar to above, but more correct?  from Glynn Clements
    (setq interprogram-cut-function nil)
    (setq interprogram-paste-function nil)

* The next time you reproduce this, could you dump out the contents of
  the "event" structure in the last call to
  x_decline_selection_request() (e.g., "print *event" in frame 6 of your
  stacktrace)?  Since we're getting a BadWindow error, I'd like to see
  the window value in the event.  Also, to make this useful, we'd need
  to see the window ID values in your X server (i.e., give us the output
  of "xwininfo -root -all").

-- 
	Darryl Okahata
	darrylo at soco.agilent.com

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.