Re: XEmacs 21.4.13 hangs after X-error!?

Mats Lidell wrote: It's "known" in the sense that similar reports are made on a regular basis. However, it isn't "known" in the sense of knowing what causes it. Not unless you can get a backtrace at the point that the bogus request was sent; i.e. before the error reply has been received. IOW, probably not. AFAICT, XSendEvent() is only used in event-Xt.c and select-x.c, and XChangeProperty() is only used in frame-x.c and select-x.c. That points the finger of suspicion at select-x.c. Both of those functions are called in x_reply_selection_request(). Furthermore, in the simple case (the data can be sent in a single operation), the calls are consecutive, i.e. XChangeProperty() is immediately followed by XSendEvent(), so they should receive consecutive serial numbers. This matches the above messages (note that the serial numbers above are reversed). The window ID is taken from the SelectionRequest event, and doesn't look remotely valid; X window IDs tend to look like: 0x00?000??, where the ?s are non-zero. So, at a glance, it looks like the problem may result from a bogus SelectionRequest event. If you weren't actually trying to paste into another application, my first suspicion would be a malfunctioning clipboard manager utility or similar. Could you provide details of which other X programs are active, particularly the WM and any "tools". Even if there isn't anything obvious, if we were to get multiple reports, that might provide a lead. -- Glynn Clements <glynn.clements(a)virgin.net&gt;