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 recently upgraded a linux server from Debian 11 to the recently released Debian 12. Upon the upgrade completing, I noticed that kitty will crash in windows when launching tmux from that Debian 12 machine. The app essentially crashes (the window says "Not Responding") and attempts to close the window manually from the top show the standard crash pop up:
I'm not sure what other documentation can I provide here, unfortunately. The setup worked perfectly fine in Debian 11 (running tmux version 3.1c, whereas Debian 12 appears to have upgraded tmux to version 3.3a). I've also tested the latest version of putty (0.78) and iTerm2 via MacOS and neither of those appears to have a problem running tmux in those terminals.
Please let me know if/how I can provide more information to assist in chasing down this bug. Thank you!
The text was updated successfully, but these errors were encountered:
Two more clients tested: Both Windows Terminal and MobaXterm seem to work just fine with Debian 12 and tmux 3.3a as well. The problem seems to be isolated only to kitty (I'm using the latest version - 0.76.1.12p).
I recently upgraded a linux server from Debian 11 to the recently released Debian 12. Upon the upgrade completing, I noticed that kitty will crash in windows when launching tmux from that Debian 12 machine. The app essentially crashes (the window says "Not Responding") and attempts to close the window manually from the top show the standard crash pop up:
I'm not sure what other documentation can I provide here, unfortunately. The setup worked perfectly fine in Debian 11 (running tmux version 3.1c, whereas Debian 12 appears to have upgraded tmux to version 3.3a). I've also tested the latest version of putty (0.78) and iTerm2 via MacOS and neither of those appears to have a problem running tmux in those terminals.
Please let me know if/how I can provide more information to assist in chasing down this bug. Thank you!
The text was updated successfully, but these errors were encountered: