Skip to content

Incorrect behaviour on Windows 10 higher than 1809 #8360

@akunitsyn

Description

@akunitsyn

For bug reports, the following information can help speed up the process. Please
describe the bug that you have found and what you would expect to happen
instead.

System

OS: Windows 10 22H2 (19045.5247)
Version: alacritty 0.14.0 (22a4475)

I tried to use alacritty with Windows ssh client and far2l on remote server (Ubuntu 24.04).
Bash console works fine. After far2l started all keys excluding arrows and some functional keys and mouse clicks are disabled in console session. I think it is the problem with kitty keyboard protocol because far2l use it by default.
There are no issues on Linux in the same case.

I installed wezterm to the same computer after this test, tried to reproduce the bug in alacritty and this issue disappeared because Wezterm installer has added conpty.dll to a system.

Part of alacritty log before wezterm installation:
[alacritty_terminal] Using Windows API for pseudoconsole

After wezterm installation:
[alacritty_terminal] Using conpty.dll for pseudoconsole

Please add conpty.dll into alacritty installer or add info about this library installation ways into documentation.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions