Re: Attempt to copy to unlocked clipboard!

Hi, I've tried to compile a recent cvs xemacs on an Debian Alpha Linux system using the Compaq C compiler. When starting src/xemacs -vanilla, and kill something (in this case ";; This buffer is"), I get repeatedly the message: Warning: Attempt to copy to unlocked clipboard! on the console and xemacs hangs. This doesn't happen if I turn off Options->Keyboard and Mouse->Yank/kill interact with clipboard. If I kill it I get: Fatal error (3). Your files have been auto-saved. Use `M-x recover-session' to recover them. If you have access to the PROBLEMS file that came with your version of XEmacs, please check to see if your crash is described there, as there may be a workaround available. Otherwise, please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /usr/local/src/xemacs-21.2-05.07/src/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: own-selection-internal(CLIPBOARD ";; This buffer is") # bind (append data type) own-selection-1(CLIPBOARD ";; This buffer is" nil) # (unwind-protect ...) # bind (--letf-save--95234 --letf-bound--95235 zmacs-region-stays append type data) own-selection(";; This buffer is" CLIPBOARD) # bind (append string) own-clipboard(";; This buffer is" t) # bind (replace string) kill-new(";; This buffer is") # bind (undo-high-threshold tail verbose end beg) kill-region(1 18 1) # bind (command-debug-status) call-interactively(kill-region) # (condition-case ... . error) # (catch top-level ...) zsh: quit (core dumped) src/xemacs -vanilla The backtrace is not really helpful: (gdb) bt #0 0x200015b3ba8 in __kill () at __kill:2 #1 0x120047054 in fatal_error_signal () Strangely, I cannot find the error message anywhere in the source. Does anybody have an idea how to track this down? Falk