From: Eli Zaretskii <eliz@gnu.org>
To: tino.calancha@gmail.com
Cc: 42655@debbugs.gnu.org, eggert@cs.ucla.edu,
monnier@iro.umontreal.ca, uyennhi.qm@gmail.com
Subject: bug#42655: 27.1; iconify-frame on a Lucid build may stuck the frame
Date: Tue, 04 Aug 2020 17:20:26 +0300 [thread overview]
Message-ID: <83tuxia3x1.fsf@gnu.org> (raw)
In-Reply-To: <CBF05EC2-30CC-4927-A059-8B6CDC69DDCD@gnu.org> (message from Eli Zaretskii on Tue, 04 Aug 2020 06:59:59 +0300)
> Date: Tue, 04 Aug 2020 06:59:59 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, uyennhi.qm@gmail.com
>
> In any case, I asked for a C-level backtrace when I responded to your original report. Can you please attach
> a debugger to Emacs after selecting the previously iconified frame, and show such a backtrace? Please do
> that with an unpatched Emacs and in "emacs -Q".
Also, I don't understand what you mean in your original report by
"unresponsive frame" and "cannot insert characters". Do you mean that
Emacs is "stuck" and doesn't respond, or do you mean that the results
of whatever you do are not displayed? And what _do_ you see displayed
when you "select the window displaying the Emacs GUI" after C-z?
If the problem is with display, then does it help to type (blindly)
"M-x redraw-display RET"?
next prev parent reply other threads:[~2020-08-04 14:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 18:46 bug#42655: 27.1; iconify-frame on a Lucid build may stuck the frame Tino Calancha
2020-08-01 18:53 ` Eli Zaretskii
2020-08-02 13:07 ` Tino Calancha
2020-08-02 14:34 ` Eli Zaretskii
2020-08-03 19:46 ` Tino Calancha
2020-08-03 21:29 ` Stefan Monnier
2020-08-04 2:21 ` Eli Zaretskii
2020-08-04 3:59 ` Eli Zaretskii
2020-08-04 14:20 ` Eli Zaretskii [this message]
2020-08-04 15:14 ` Bhavin Gandhi
2020-08-04 16:40 ` Eli Zaretskii
2020-08-04 18:53 ` Bhavin Gandhi
2020-08-04 19:07 ` Eli Zaretskii
2020-08-05 17:23 ` Bhavin Gandhi
2020-08-05 18:43 ` Eli Zaretskii
2020-08-05 18:57 ` Tino Calancha
2020-08-06 2:29 ` Eli Zaretskii
2020-08-06 5:41 ` Bhavin Gandhi
2020-08-06 7:43 ` Eli Zaretskii
2020-08-06 8:13 ` Tino Calancha
2020-08-06 13:47 ` Eli Zaretskii
2020-08-06 13:57 ` Eli Zaretskii
2020-08-06 14:18 ` Tino Calancha
2020-08-06 14:37 ` Tino Calancha
2020-08-07 5:53 ` Eli Zaretskii
2020-08-07 11:47 ` Tino Calancha
2020-08-07 12:05 ` Eli Zaretskii
2020-08-07 12:20 ` Bhavin Gandhi
2020-08-07 14:01 ` Tino Calancha
2020-08-07 15:06 ` Eli Zaretskii
2020-08-08 11:52 ` Tino Calancha
2020-08-09 14:26 ` Eli Zaretskii
2020-08-10 17:52 ` Tino Calancha
2020-08-12 16:50 ` Eli Zaretskii
2020-08-15 14:23 ` Tino Calancha
2020-08-05 18:24 ` Tino Calancha
2020-08-05 18:31 ` Bhavin Gandhi
2020-08-05 18:34 ` Tino Calancha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tuxia3x1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42655@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=monnier@iro.umontreal.ca \
--cc=tino.calancha@gmail.com \
--cc=uyennhi.qm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).