You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to switch to wezterm. At first it all seemed fine but then I experienced the same and wezterm had the tendency to lockup (the wayland backend is being rewritten, that might be why). Then I found kovidgoyal/kitty#2191 (comment) and as I explained later on in the thread, kitty was receiving lots of IME-related events even without me using the keyboard. systemctl stop --user fcitx5-daemon fixed the issue. I have yet to investigate the situation. Looks like there is an execve failure in my fcitx5 journal.
Putting it out there since fix was not obvious.
Maintainer CC
No response
System information
nixos-unstable
The text was updated successfully, but these errors were encountered:
Are you following the right branch?
Is there an existing issue for this?
Issue description
Kitty had trouble processing my input:
I tried to switch to wezterm. At first it all seemed fine but then I experienced the same and wezterm had the tendency to lockup (the wayland backend is being rewritten, that might be why). Then I found kovidgoyal/kitty#2191 (comment) and as I explained later on in the thread, kitty was receiving lots of IME-related events even without me using the keyboard.
systemctl stop --user fcitx5-daemon
fixed the issue. I have yet to investigate the situation. Looks like there is anexecve
failure in my fcitx5 journal.Putting it out there since fix was not obvious.
Maintainer CC
No response
System information
The text was updated successfully, but these errors were encountered: