GNU bug report logs - #42655
27.1; iconify-frame on a Lucid build may stuck the frame

Previous Next

Full log

Message #89 received at 42655 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Tino Calancha <tino.calancha <at> gmail.com>
Cc: 42655 <at> debbugs.gnu.org, eggert <at> cs.ucla.edu, uyennhi.qm <at> gmail.com,
 bhavin7392 <at> gmail.com, monnier <at> iro.umontreal.ca
Subject: Re: bug#42655: 27.1; iconify-frame on a Lucid build may stuck the
 frame
Date: Fri, 07 Aug 2020 08:53:27 +0300

> From: Tino Calancha <tino.calancha <at> gmail.com>
> Date: Thu, 6 Aug 2020 16:37:18 +0200 (CEST)
> cc: Tino Calancha <tino.calancha <at> gmail.com>, bhavin7392 <at> gmail.com, 
>     42655 <at> debbugs.gnu.org, eggert <at> cs.ucla.edu, uyennhi.qm <at> gmail.com, 
>     monnier <at> iro.umontreal.ca
> 
> > Thanks.  Looks like we never get the MapNotify event from X windows?
> > Can you verify that, either by running the xev utility or by setting a
> > breakpoint in xterm.c:handle_one_xevent when MapNotify is handled, and
> > repeating the recipe?
> 
> Set breakpoint at
> xterm::8348
> C-z ; frame is hidden
> ;; I select again the hidden frame
> ;; gdb doesn't jump to the breakpoint and the frame is 'cursed'
> M-x
> ;; The frame wakes up and gdb reaches the breakpoint.

And if you apply your patch, do we get MapNotify immediately after
"selecting again the hidden frame"?

Btw, what does "selecting again the hidden frame" mean, exactly?  What
gestures do you use to do that?  And what is your window manager?
(Bhavin, can you answer these questions for your case as well?)

Previous Next

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