Re: [Bug: 21.4.17] FreeBSD 6, Gnome 2.12.1, Xemacs 21.4 spews BadWindow errors.

George> Whenever I type a bit of text into xemacs and "kill" it George> (e.g. move to the beginning of the line hit control-k), I George> get a pair of messages in the xterm window from which I George> started xemacs: George> It only happens when nautilus is running. As far as I know this is harmless, except that it messes up your terminal screen. It's possible that it's an XEmacs bug, but the last time I tried to debug this I put a trace on the window creation function and those are definitely not XEmacs's windows. We may have misimplemented the protocol (see below), but the folks who did that work were pretty wizardly. Caveat: I don't understand the following, I'm just repeating what somebody else diagnosed. Apparently some applications misuse the X selection, by setting the owner to a window that they later destroy without disowning the selection. The X selection (or maybe it's the clipboard) protocol requires some communication with the former owner when this is done, but that window no longer exists so you get the bad resource message. GNOME applications are apparently especially prone to this behavior. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.