unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jay Berkenbilt" <ejb@ql.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 55726@debbugs.gnu.org
Subject: bug#55726: 28.1; emacs becomes unresponsive to input
Date: Mon, 30 May 2022 11:00:27 -0400	[thread overview]
Message-ID: <93bfe4a8-b57e-47fa-be43-af22e54c72c8@www.fastmail.com> (raw)
In-Reply-To: <87ee0bw0i4.fsf@tcd.ie>



On Mon, May 30, 2022, at 10:36 AM, Basil L. Contovounesios wrote:
> Jay Berkenbilt [2022-05-30 08:58 -0400] wrote:
> 
> > Problem description: I'm typing along, and all of a sudden, emacs
> > becomes completely unresponsive to mouse and keyboard events. It still
> > refreshes properly. I haven't been able to find any way out of this
> > other than to kill the process.
> 
> Have you tried attaching to the frozen Emacs instance from a terminal?
> 
> I ask about attaching from the terminal because your description and
> stacktrace remind me of my experience in https://bugs.gnu.org/48629,
> which I have run into once or twice in the last few months of infrequent
> Emacs usage.
> 
> HTH,
> 
> -- 
> Basil
> 

I haven't tried that. That's a great idea for a potential workaround
while we're tracking this down. I'll try it next time.





  reply	other threads:[~2022-05-30 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 12:58 bug#55726: 28.1; emacs becomes unresponsive to input Jay Berkenbilt
2022-05-30 13:57 ` Eli Zaretskii
     [not found]   ` <aa78fc87-b4e8-4629-be45-466967885a55@www.fastmail.com>
2022-05-30 15:18     ` Jay Berkenbilt
2022-06-18 19:38       ` Jay Berkenbilt
2022-06-19  5:38         ` Eli Zaretskii
2022-06-19 12:56           ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-28 19:12             ` Jay Berkenbilt
2022-05-30 14:36 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-30 15:00   ` Jay Berkenbilt [this message]
2022-06-17  1:53 ` dick

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=93bfe4a8-b57e-47fa-be43-af22e54c72c8@www.fastmail.com \
    --to=ejb@ql.org \
    --cc=55726@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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).