From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: 61719@debbugs.gnu.org
Subject: bug#61719: 29.0.60; pgtk focus problem with Sway 1.7
Date: Thu, 23 Feb 2023 17:35:34 +0800 [thread overview]
Message-ID: <87fsawohax.fsf@yahoo.com> (raw)
In-Reply-To: <87k0099wog.fsf@melete.silentflame.com> (Sean Whitton's message of "Wed, 22 Feb 2023 15:12:31 -0700")
Sean Whitton <spwhitton@spwhitton.name> writes:
> X-debbugs-cc: luangruo@yahoo.com
>
> I just upgraded a workstation Debian bullseye->bookworm, which involved
> an upgrade of the Sway Wayland compositor from 1.5 to 1.7. This appears
> to have uncovered a bug in the pgtk build.
>
> 1. emacs -Q --bg-daemon=foo
> 2. emacsclient -sfoo -nc; sleep 5; emacsclient -sfoo -nc
>
> After the second frame has opened, it seems that the first still has
> keyboard focus for typing unmodified self-insert chars, but if you type
> C-x, then neither of the frames receives the keypress.
>
> I tried 'firefox -new-window; sleep 5; firefox -new-window', which is
> also Wayland-native GTK, for comparison. The bug does not appear there.
Would you please run Emacs with ``WAYLAND_DEBUG=client'' and show the
print out around the time you create the new frame?
The output will be very verbose, but please send the entirety, and not
just what you think to be the problem. Thanks.
next prev parent reply other threads:[~2023-02-23 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 22:12 bug#61719: 29.0.60; pgtk focus problem with Sway 1.7 Sean Whitton
2023-02-23 9:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-24 4:52 ` Sean Whitton
2023-02-24 20:34 ` Sean Whitton
2023-05-03 19:18 ` Sean Whitton
2023-07-02 21:53 ` Sean Whitton
2023-08-23 20:37 ` bug#61719: 29.1; pgtk focus problem with fcitx5 5.0.21 preedit Sean Whitton
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=87fsawohax.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=61719@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=spwhitton@spwhitton.name \
/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).