public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: keyboard problem under X and last snapshot (2022-03-01)
Date: Thu, 10 Mar 2022 18:10:31 +0900	[thread overview]
Message-ID: <20220310181031.9b9c6d6b465fb97a34c99611@nifty.ne.jp> (raw)
In-Reply-To: <FEC414AD-0458-4056-A44B-B5E274493433@Denis-Excoffier.org>

On Wed, 9 Mar 2022 22:24:45 +0100
Denis Excoffier wrote:
> I tried the last snapshot (dated 2022-03-01), which seems to work well, until i failed to launch X/Windows, giving the
> following message in a Windows popup: Failed to activate virtual core keyboard: 2
> 
> Under the preceding snapshot (dated 2022-02-17) everything works perfectly.
> 
> Below the full content of the failing XWin.0.log. Any ideas?

I noticed this occurs after the commit:

commit 0ddf19d6ca6edf9edd7fc147124794fa9d5100e0
Author: Takashi Yano <takashi.yano@nifty.ne.jp>
Date:   Mon Feb 21 21:20:48 2022 +0900

    Cygwin: pty, console: Fix handle leak which occurs on exec() error.

    - This patch fixes the handle leak which occurs when exec() fails
      with an error. The duplicated handles will be closed when the
      exec'ed process is terminated. However, if exec() fails, the code
      path does not reach to the code closing the duplicated handles.
      To implement this fix more appropriately, the setup, cleanup and
      closing pty codes which was previously located in spawn.cc are
      encapsulated into the fhandler_pty_slave class functions.

Now, I am looking into this problem. Please wait a while.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2022-03-10  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 21:24 Denis Excoffier
2022-03-10  9:10 ` Takashi Yano [this message]
2022-03-10 11:33   ` Takashi Yano

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=20220310181031.9b9c6d6b465fb97a34c99611@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.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.
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).