Skip to content

[Bug]: Alacritty + WSL does not accept typing #2598

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
azaslavsky opened this issue Feb 24, 2025 · 1 comment
Open
1 task done

[Bug]: Alacritty + WSL does not accept typing #2598

azaslavsky opened this issue Feb 24, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@azaslavsky
Copy link

What did you expect to happen?

I should be able to type when in the Altuin TUI.

What happened?

I am able to enter the Altuin TUI, and navigate it when using up/down arrows, but typing any actual keys or pressing enter is not possible. My setup: Using alacritty 0.13.2 on Windows 11, which is connected to WSL2 instance running Ubuntu 20.04.

Interestingly, altuin works fine from inside tmux - it's only at the top-level that there are problems.

Atuin doctor output

Atuin Doctor
Checking for diagnostics


Please include the output below with any bug reports or issues

{
  "atuin": {
    "version": "18.4.0",
    "sync": null,
    "sqlite_version": "3.46.0"
  },
  "shell": {
    "name": "bash",
    "default": "bash",
    "plugins": [
      "atuin",
      "bash-preexec"
    ],
    "preexec": "bash-preexec"
  },
  "system": {
    "os": "Ubuntu",
    "arch": "x86_64",
    "version": "20.04",
    "disks": [
      {
        "name": "none",
        "filesystem": "overlay"
      },
      {
        "name": "drivers",
        "filesystem": "9p"
      },
      {
        "name": "/dev/sdc",
        "filesystem": "ext4"
      },
      {
        "name": "/dev/sdc",
        "filesystem": "ext4"
      },
      {
        "name": "none",
        "filesystem": "overlay"
      },
      {
        "name": "none",
        "filesystem": "overlay"
      },
      {
        "name": "none",
        "filesystem": "overlay"
      },
      {
        "name": "C:\\134",
        "filesystem": "9p"
      },
      {
        "name": "/dev/sdc",
        "filesystem": "ext4"
      },
      {
        "name": "snapfuse",
        "filesystem": "fuse.snapfuse"
      },
      {
        "name": "snapfuse",
        "filesystem": "fuse.snapfuse"
      },
      {
        "name": "snapfuse",
        "filesystem": "fuse.snapfuse"
      },
      {
        "name": "snapfuse",
        "filesystem": "fuse.snapfuse"
      },
      {
        "name": "snapfuse",
        "filesystem": "fuse.snapfuse"
      },
      {
        "name": "snapfuse",
        "filesystem": "fuse.snapfuse"
      },
      {
        "name": "/dev/sdd",
        "filesystem": "ext4"
      },
      {
        "name": "/dev/sdc",
        "filesystem": "ext4"
      },
      {
        "name": "/dev/sdc",
        "filesystem": "ext4"
      },
      {
        "name": "C:\\134Program\\040Files\\134Docker\\134Docker\\134resources",
        "filesystem": "9p"
      }
    ]
  }
}

Code of Conduct

  • I agree to follow this project's Code of Conduct
@azaslavsky azaslavsky added the bug Something isn't working label Feb 24, 2025
@Liushitong
Copy link

Liushitong commented Apr 14, 2025

I got same issue.

  • Windows 10
  • WSL2 and Ubuntu22.04
  • zsh 5.8.1
  • Alacritty 0.15.1
  • atuin 18.4.0

Only the arrow keyboards can be used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants