From: Jason Kim <jason.w.kim@icloud.com>
To: me@rpatterson.net, Brian.Inglis@Shaw.ca, cygwin@cygwin.com
Subject: BUG: Log on Scheduled Task invisible/empty window blocks input
Date: Sat, 25 Nov 2023 09:16:08 -0600 [thread overview]
Message-ID: <6d77eda9-fee1-413a-8302-4657a639f9e3@icloud.com> (raw)
Hi,
This particular issue with the invisible windows that pop up seems to be
a relatively a new issue with cygwin with recent win11.
With a slightly older windows 10, these conhost tasks with their
invisible windows do not pop up at all (that I've noticed).
And no amount of using "run.exe" to launch seems to help.
Not using Administrator privileges on the shortcut does not seem to help
either.
All I know is that the same shortcut links and .bat files that worked
for 10+ years to start x11, start a mintty etc...
are now producing conhost.exe tasks with windows that are invisble. And
something triggers these windows to start blocking mouse input. Once
that happens, ctrl-alt-delete and then pressing escape seems to quiet
them down (so that mouse selection works again on the blocked areas of
the desktop, for a short while at least.
Killing the conhost tasks resolves the mouse i/o issue, but it seems to
interrupt copy/paste of text.
How can I fix this?
Please help!
Thank you
-Jason
next reply other threads:[~2023-11-25 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 15:16 Jason Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-27 2:43 Ross Patterson
2023-01-27 19:39 ` Brian Inglis
2023-01-29 22:55 ` Ross Patterson
2023-01-29 23:48 ` Brian Inglis
2023-01-30 11:02 ` Ross Patterson
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=6d77eda9-fee1-413a-8302-4657a639f9e3@icloud.com \
--to=jason.w.kim@icloud.com \
--cc=Brian.Inglis@Shaw.ca \
--cc=cygwin@cygwin.com \
--cc=me@rpatterson.net \
/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.
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).