keyboard problem under X and last snapshot (2022-03-01)

keyboard problem under X and last snapshot (2022-03-01)

[Denis Excoffier]

Hello,

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?

Regards,
Denis Excoffier.

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.21.1.3
OS: CYGWIN_NT-10.0-17763 PC17470 3.4.0-341.x86_64.snap 2022-03-01 00:05 UTC x86_64
OS: Windows 10  [Windows NT 10.0 build 17763] x64
Package: version 21.1.3-1 built 2022-01-14

XWin was started with the following command line:

/usr/bin/XWin -nodecoration -emulate3buttons -unixkill 
 -nowinkill -auth (…redacted...)/Xauthority :0 

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1920 h 1080
[ 27622.062] (II) xorg.conf is not supported
[ 27622.062] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
[ 27622.062] winUpdateDpi - primary monitor native DPI x 96 y 96
[ 27622.062] LoadPreferences: (…redacted...)/.XWinrc not found
[ 27622.109] LoadPreferences: Loading /etc/X11/system.XWinrc
[ 27622.109] LoadPreferences: Done parsing the configuration file...
[ 27622.125] winDetectSupportedEngines - RemoteSession: no
[ 27622.218] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
[ 27622.218] winDetectSupportedEngines - Returning, supported engines 00000005
[ 27622.218] winSetEngine - Using Shadow DirectDraw NonLocking
[ 27622.218] winScreenInit - Using Windows display depth of 32 bits per pixel
[ 27622.265] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
[ 27622.265] MIT-SHM extension disabled due to lack of kernel support
[ 27622.265] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
[ 27622.265] (EE) AIGLX: No native OpenGL in modes with a root window
[ 27622.687] (II) IGLX: Loaded and initialized swrast
[ 27622.687] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 27622.859] (EE) Error compiling keymap (server-0) executing '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "/tmp/xkb_w55Azw" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "/tmp/server-0.xkm" >/tmp/xkb_G5ywI7 2>&1'
[ 27622.859] (EE) xkbcomp exit status 0xffffffff
[ 27622.859] (EE) XKB: Couldn't compile keymap
[ 27622.859] (EE) XKB: Failed to load keymap. Loading default keymap instead.
[ 27622.875] (EE) Error compiling keymap (server-0) executing '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "/tmp/xkb_zJBPAR" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "/tmp/server-0.xkm" >/tmp/xkb_hBHkrn 2>&1'
[ 27622.875] (EE) xkbcomp exit status 0xffffffff
[ 27622.875] (EE) XKB: Couldn't compile keymap
[ 27622.875] XKB: Failed to compile keymap
[ 27622.875] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
[ 27622.875] (EE) Fatal server error:
[ 27622.875] (EE) Failed to activate virtual core keyboard: 2(EE) 
[ 27622.875] (EE) Server terminated with error (1). Closing log file.

Re: keyboard problem under X and last snapshot (2022-03-01)

[Takashi Yano]

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>

Re: keyboard problem under X and last snapshot (2022-03-01)

[Takashi Yano]

On Thu, 10 Mar 2022 18:10:31 +0900
Takashi Yano wrote:
> 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.

I found the cause. The problem was access violation in the code
retrieving the pgid of the ctty.

I will submit a patch shortly.

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