With 21.4.1 from CVS I get: gromit:/builds/xemacs/xemacs:[0]$ src/xemacs -vanilla Warning: XtRemoveGrab asked to remove a widget not on the list Here's my system configuration. Any ideas what could be the problem? Btw. congretulations for 21.4.1! Andreas uname -a: Linux gromit 2.4.4-pre7 #77 Thu Apr 26 20:54:30 CEST 2001 i686 unknown /usr/src/cvs/xemacs-release-21-4/configure '--prefix=/opt/aj' '--extra-verbose=no' '--with-site-lisp' '--with-database=no' '--error-checking=none' '--debug=no' '--mail-locking=flock' '--with-gpm=no' '--with-sound=none' '--with-menubars=lucid' '--with-scrollbars=lucid' '--with-ncurses' '--with-mule' '--with-widgets=no' 'i686-linux-gnu' XEmacs 21.4.1 "Copyleft" configured for `i686-pc-linux'. Compilation / Installation: Source code location: /usr/src/cvs/xemacs-release-21-4 Installation prefix: /opt/aj Operating system description file: `s/linux.h' Machine description file: `m/intel386.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wshadow -Wsign-compare Relocating allocator for buffers: no GNU version of malloc: yes - Using Doug Lea's new malloc from the GNU C Library. Window System: Compiling in support for the X window system: - X Windows headers location: /usr/X11/include - X Windows libraries location: /usr/X11/lib - Handling WM_COMMAND properly. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. TTY: Compiling in support for ncurses. Images: Compiling in support for GIF images (builtin). Compiling in support for XPM images. Compiling in support for PNG images. Compiling in support for JPEG images. Compiling in support for TIFF images. Compiling in support for X-Face message headers. Sound: Databases: Compiling in support for LDAP. Internationalization: Compiling in support for Mule (multi-lingual Emacs). Compiling in support for XIM (X11R5+ I18N input method). - Using raw Xlib to provide XIM support. Mail: Compiling in support for "flock" mail spool file locking method. Other Features: Compiling in support for dynamic shared object modules. gromit:/builds/xemacs/xemacs:[0]$ xdpyinfo name of display: :0.0 version number: 11.0 vendor string: The XFree86 Project, Inc vendor release number: 3360 maximum request size: 4194300 bytes motion buffer size: 256 bitmap unit, bit order, padding: 32, LSBFirst, 32 image byte order: LSBFirst number of supported pixmap formats: 2 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 keycode range: minimum 8, maximum 255 focus: window 0x780000e, revert to Parent number of extensions: 19 BIG-REQUESTS DOUBLE-BUFFER DPMS LBX MIT-SCREEN-SAVER MIT-SHM MIT-SUNDRY-NONSTANDARD RECORD SECURITY SHAPE SYNC XC-APPGROUP XC-MISC XFree86-DGA XFree86-Misc XFree86-VidModeExtension XInputExtension XKEYBOARD XTEST default screen number: 0 number of screens: 1 screen #0: dimensions: 1280x1024 pixels (433x347 millimeters) resolution: 75x75 dots per inch depths (1): 16 root window id: 0x26 depth of root window: 16 planes number of colormaps: minimum 1, maximum 1 default colormap: 0x23 default number of colormap cells: 64 preallocated pixels: black 0, white 65535 options: backing-store YES, save-unders YES largest cursor: 32x32 current input event mask: 0x58007f KeyPressMask KeyReleaseMask ButtonPressMask ButtonReleaseMask EnterWindowMask LeaveWindowMask PointerMotionMask SubstructureNotifyMask SubstructureRedirectMask PropertyChangeMask number of visuals: 1 default visual id: 0x22 visual: visual id: 0x22 class: TrueColor depth: 16 planes available colormap entries: 64 per subfield red, green, blue masks: 0xf800, 0x7e0, 0x1f significant bits in color specification: 6 bits gromit:/builds/xemacs/xemacs:[0]$ -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.inka.de http://www.suse.de/~aj

Andy Piper <andyp(a)bea.com&gt; writes: > I've seen this at frame deletion and never been able to track it > down. I believe its widget related becuase it came and went while I > was hacking on them. Do you have any idea how to track it down? I can easily reproduce it but don't know anything about the widget stuff.

Andy Piper wrote: > > At 12:06 PM 5/1/01 +0200, Andreas Jaeger wrote: > >Andy Piper <andyp(a)bea.com&gt; writes: > > > > > I've seen this at frame deletion and never been able to track it > > > down. I believe its widget related becuase it came and went while I > > > was hacking on them. > > > >Do you have any idea how to track it down? I can easily reproduce it > >but don't know anything about the widget stuff. > > Absolutely no idea - it seems to be in the guts of the X code. I read all > the manuals and put breakpoints everywhere, but I just don't know what the > error is indicating. what you need to do is recompile the Xt sources with debug info, and find the place in the sources where this error is being issued, and set a breakpoint there. this shouldn't be hard, although perhaps a bit time-consuming if the Xt sources don't recompile easily. the message indicates that XtRemoveGrab was called on a widget without an associated earlier XtAddGrab call. those calls are used to create menus and modal dialog boxes -- anything that temporarily locks out input to all other widgets. andy, what state is the focus-handling in your code in?