all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: git@sphalerite.org
Cc: 60356@debbugs.gnu.org
Subject: bug#60356: 30.0.50; individual frame loses keyboard focus, focus cannot be restored
Date: Tue, 27 Dec 2022 18:50:46 +0200	[thread overview]
Message-ID: <83edsk23kp.fsf@gnu.org> (raw)
In-Reply-To: <ygav8lxujhb.fsf@localhost> (git@sphalerite.org)

> From: git@sphalerite.org
> Date: Tue, 27 Dec 2022 13:19:44 +0100
> 
> 
> The exact action leading to this bug is not clear to me. It seems to be
> related to lsp-mode though -- I've not observed it happening without
> lsp-mode.
> 
> The symptom is that a single frame will no longer accept keyboard input,
> and will visually indicate that it is not focused (outline rectangular
> cursor where I'd usually expect a solid rectangular cursor). Mouse input
> still works, and other frames still accept keyboard input as normal.
> 
> I'd be glad if anyone could point out ways to further debug this issue.
> I'm also in #emacs:matrix.org (@linus:schreibt.jetzt) in case
> fast-turnaround communication would be helpful :)

If you attach a debugger to Emacs in that state, and type

  (gdb) thread apply all bt

what do you get?  Please post here everything that GDB prints when you
do that.

Thanks.





  reply	other threads:[~2022-12-27 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 12:19 bug#60356: 30.0.50; individual frame loses keyboard focus, focus cannot be restored git
2022-12-27 16:50 ` Eli Zaretskii [this message]
2023-01-03 13:11   ` Linus Heckemann
2023-01-03 13:32     ` Eli Zaretskii
2023-01-04  1:08     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-28 23:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83edsk23kp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60356@debbugs.gnu.org \
    --cc=git@sphalerite.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.