GNU bug report logs - #9310
BadWindow error with quail guidance frame

Previous Next

Full log

Message #34 received at 9310-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: "Jan D." <jan.h.d <at> swipnet.se>
Cc: 9310-done <at> debbugs.gnu.org
Subject: Re: bug#9310: BadWindow error with quail guidance frame
Date: Fri, 14 Oct 2011 13:46:57 -0400

>>> Basically set synchronized and break in the error function.
>> OK, that part was already done.
>>> Then go up the call stack to find the frame the window belongs to,
>> That as well: it's the minibuffer-only frame.
>>> or see if it is some uninitialized value.
>> Doesn't look like it, the frames involved seem to have sensible
>> field values.  This problem started around the time the new window.c code
>> was installed, FWIW (which doesn't mean it's actually related).
> You can try xwininfo -id <the window> to see if there is something special
> about that window.  Compare with another window you have in Emacs.

Nothing stands out, no.  I just installed a patch that ignores errors in
that XSetWindowBorder function and it seems to be sufficient.


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.