unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bhavin Gandhi <bhavin7392@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 42655@debbugs.gnu.org, eggert@cs.ucla.edu,
	tino.calancha@gmail.com, uyennhi.qm@gmail.com,
	monnier@iro.umontreal.ca
Subject: bug#42655: 27.1; iconify-frame on a Lucid build may stuck the frame
Date: Tue, 4 Aug 2020 20:44:35 +0530	[thread overview]
Message-ID: <CAOn=hbc-Z-koLqDQ-ZVV+rohGZuDtLHyXA0jwUMoszRWwDk5Kw@mail.gmail.com> (raw)
In-Reply-To: <83tuxia3x1.fsf@gnu.org>

I was able to reproduce this with Lucid. I will try to read about
attaching debugger and post the results here.

On Tue, 4 Aug 2020 at 19:59, Eli Zaretskii <eliz@gnu.org> wrote:
> 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?

The latter. The frame gets frozen, whatever we do is not displayed.  The
menu bar is functional though.

> And what _do_ you see displayed when you "select the window displaying
> the Emacs GUI" after C-z?

It's just shown as frozen in a state before we press C-z. I ran M-x zone
and then pressed C-z, the frame was frozen with 'Zoning...sorry' in the
minibuffer.

> If the problem is with display, then does it help to type (blindly)
> "M-x redraw-display RET"?

No it doesn't. The only thing worked was to create a new frame.





  reply	other threads:[~2020-08-04 15:14 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
2020-08-04 15:14             ` Bhavin Gandhi [this message]
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='CAOn=hbc-Z-koLqDQ-ZVV+rohGZuDtLHyXA0jwUMoszRWwDk5Kw@mail.gmail.com' \
    --to=bhavin7392@gmail.com \
    --cc=42655@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --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).