From: Eli Zaretskii <eliz@gnu.org>
To: Mike Kupfer <kupfer@rawbw.com>
Cc: 74535@debbugs.gnu.org
Subject: bug#74535: 30.0.92; partial hang, esp. keyboard events
Date: Mon, 25 Nov 2024 21:27:34 +0200 [thread overview]
Message-ID: <8634jfi061.fsf@gnu.org> (raw)
In-Reply-To: <22277.1732561980@alto.camomileplus.org> (message from Mike Kupfer on Mon, 25 Nov 2024 11:13:00 -0800)
> From: Mike Kupfer <kupfer@rawbw.com>
> Date: Mon, 25 Nov 2024 11:13:00 -0800
>
> I've been getting occasional Emacs hangs, under both Xfce and MATE. I
> haven't seen the problem (so far) with i3. Emacs seems to handle mouse
> events okay, e.g., it looks like point is moving in response to a mouse
> click. And I can create new frames using emacsclient. But keyboard
> events don't seem to be processed--there's no response to C-g, M-x,
> C-p, C-n, simple text, F10.
>
> I tried troubleshooting the problem using strace (simple "strace -p
> <emacs_pid>"), but there's so much output I've been unable to make sense
> of it.
>
> I don't have a reliable recipe for reproducing the problem. It *might*
> be related to closing a frame.
>
> I did not see this problem with 30.0.91.
>
> My current plan for troubleshooting (the next time it happens) is to
> attach gdb, dump the last 10 items in recent_keys (using the
> instructions in etc/DEBUG), resume the process, type a few keys, go back
> into gdb, and see if recent_keys and recent_keys_index have changed. Is
> there a better approach?
Bisecting is better. Since you didn't have this problem with the
previous pretest (but please verify that first: it could be that the
problem started happening because of an unrelated change to your
system), you need to bisect between that and the last pretest, which
shouldn't be a lot of revisions.
Thanks.
next prev parent reply other threads:[~2024-11-25 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 19:13 bug#74535: 30.0.92; partial hang, esp. keyboard events Mike Kupfer
2024-11-25 19:27 ` Eli Zaretskii [this message]
2024-11-25 21:59 ` Mike Kupfer
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=8634jfi061.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74535@debbugs.gnu.org \
--cc=kupfer@rawbw.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).