[Bug]: Atuin "freezes" in some cases and completely ignores all key press events and only responds for SIGTERM

[Dentrax]

What did you expect to happen?

Nothing, work as-is.

What happened?

When I press CTRL+R, Atuin completely ignores any key press events and doesn't respond at all. It only respects for CTRL+C.

Force quit and reopen the iTerm2 doesn't resolve the issue. But it works native Terminal.app.

The problem started occurring in the last few weeks. (I've no idea what's changed, Atuin has been working seamlessly)

I think it just freezes. But I can see that ago times are still counting from seconds, which means the UI is refreshing itself. So not sure if "freeze" is the right wording here.

How can I debug further? So that I can able to provide more context for you.

Atuin doctor output

{
  "atuin": {
    "version": "18.4.0",
    "sync": null,
    "sqlite_version": "3.46.0"
  },
  "shell": {
    "name": "zsh",
    "default": "zsh",
    "plugins": [
      "atuin"
    ],
    "preexec": "built-in"
  },
  "system": {
    "os": "Darwin",
    "arch": "arm64",
    "version": "15.2",
    "disks": [
      {
        "name": "Macintosh HD",
        "filesystem": "apfs"
      },
      {
        "name": "Macintosh HD",
        "filesystem": "apfs"
      }
    ]
  }
}

Code of Conduct

• I agree to follow this project's Code of Conduct

[Dentrax]

I found the issue, it was https://symless.com/synergy software. When I'm controlling Mac from Windows PC, Arrow keys no longer works in Atuin. How can I debug this? cc @ellie

[hydriniumh2]

I have the exact same issue, although I'm using InputLeap - which is a branch off the original repo Synergy is based on.
Keys are not registering in atuin when I use a shared keyboard + iterm2 + atuin. It works when I'm using the laptop keyboard or if I'm using the built in terminal.

{
  "atuin": {
    "version": "18.4.0",
    "sync": null,
    "sqlite_version": "3.46.0"
  },
  "shell": {
    "name": "zsh",
    "default": "zsh",
    "plugins": [
      "atuin"
    ],
    "preexec": "built-in"
  },
  "system": {
    "os": "Darwin",
    "arch": "arm64",
    "version": "15.3.1",
    "disks": [
      {
        "name": "Macintosh HD",
        "filesystem": "apfs"
      },
      {
        "name": "Macintosh HD",
        "filesystem": "apfs"
      }
    ]
  }

Actually, I just found I can get arrows to respond if I press Capslock, shift or alt at the same time and that I can't use those keys in Iterm2 after exiting Atuin

[hydriniumh2]

Messing around I found that changing two settings in iterm2 under Settings -> Profiles -> Keys seems to fix the issue.

"Apps can change how keys are reported"
Turn off - fixes arrow keys not working, however upon exiting Atuin the keybindings for shift, ctrl and capslock are still broken

"Report keys using CSI u"
Turn on - fixes keybindings being broken upon exiting Atuin
If only this is turned on while "Apps can change how keys are reported" is on the keybindings still break

I have no idea why either of these work, so if anyone can chime in on an explanation/ actual fix that would also be helpful.

[ellie]

How can I debug this?

I'm really sorry but I'm not at all familiar with any of these systems, do not remote-control machines, and do not have a windows PC. I'm unable to help and support here.

[hydriniumh2]

It does seem to be more of an issue with inputLeap + iterm2 as vanilla Ctrl+R doesn't work right either. Possibly related issue input-leap/input-leap#2077 although the fix hasn't made it into an official release yet

Update: I tried the newest unreleased git version of inputleap and it fixes the issue, you still need to have "Apps can change how keys are reported" turned off but "Report keys using CSI u" can be left off. I think that specific option had a side effect of causing odd input on some keys when ctrl was pressed at the same time.

[Dentrax]

Thanks so much @hydriniumh2, your instructions worked for me!