From: Bob Rogers <rogers@rgrjr.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57468@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#57468: 29.0.50; Text cursor continues to blink when frame loses focus
Date: Wed, 31 Aug 2022 12:02:04 -0700 [thread overview]
Message-ID: <25359.45100.999353.785164@orion.rgrjr.com> (raw)
In-Reply-To: <87k06o91c5.fsf@gnus.org>
From: Lars Ingebrigtsen <larsi@gnus.org>
Date: Wed, 31 Aug 2022 12:03:38 +0200
Bob Rogers <rogers@rgrjr.com> writes:
> Then I brought up a pre-existing emacs instance running as root
> (which I had forgotten about) and found that its blinking cursor stays
> on persistently, and the focus in/out code above shows that it's getting
> neither event.
How was the root Emacs started? Could it be in a way that stops the
window manager from delivering events to it?
Just "emacs &" after "su" in a shell. I should emphasize that I've seen
nothing special about the root emacs; all instances save one switched
between working and nonworking at long but unpredictable intervals. And
the other problematic instances were also spawned from shells, though
some were from a Konsole shell, some were via ssh with tunneled X11, and
some from an emacs shell window.
I've also tried a slightly newer version of master (commit
136495f178ccd36b23ffc347fe2b6680fd689e34) on the previous openSUSE
release, and the cursor behaves normally WRT focus-in/out. Here's what
report-emacs-bug says about the installation:
Windowing system distributor 'The X.Org Foundation', version 11.0.12003000
System Description: openSUSE Leap 15.3
This is under KDE/Plasma, apparently version 5.18.5.
-- Bob
next prev parent reply other threads:[~2022-08-31 19:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 23:38 bug#57468: 29.0.50; Text cursor continues to blink when frame loses focus Bob Rogers
2022-08-29 15:21 ` Lars Ingebrigtsen
2022-08-29 18:04 ` Bob Rogers
2022-08-30 10:27 ` Lars Ingebrigtsen
2022-08-30 12:02 ` Eli Zaretskii
2022-08-30 23:33 ` Bob Rogers
2022-08-31 10:03 ` Lars Ingebrigtsen
2022-08-31 19:02 ` Bob Rogers [this message]
2022-08-31 19:24 ` Eli Zaretskii
2022-08-31 19:31 ` Bob Rogers
2022-09-03 9:44 ` Lars Ingebrigtsen
2022-09-03 11:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 11:52 ` Lars Ingebrigtsen
2022-09-03 11:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 12:08 ` Lars Ingebrigtsen
2022-09-03 12:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 12:37 ` Lars Ingebrigtsen
2022-09-03 13:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 13:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 13:47 ` Lars Ingebrigtsen
2022-09-03 13:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 17:53 ` Bob Rogers
2022-09-04 0:36 ` 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
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=25359.45100.999353.785164@orion.rgrjr.com \
--to=rogers@rgrjr.com \
--cc=57468@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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 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).