Keyboard entry after ssh broken pipe after suspend emits key codes instead of characters #11808
-
Issue DescriptionI suspend my arch linux machine at the end of the day so that I can (somewhat) resume my work the next day. If i'm ssh'ed into a vm / server when I wake my desktop the ghostty window goes into this mode where any keypress shows (unicode?) codes If I click onto another application then the ghostty window draws focus back to the window. I need to go to a new ghostty window (Creating new tabs and splits still works) I'm running: Cosmic DE is in tiling mode. Expected BehaviorI expect that it would drop the ssh session, and the keys pressed would appear as the actual character. Actual Behaviorall key presses that are not ghostty hotkeys or OS hotkeys print codes on the screen enter still works as enter though. the bottom command I typed It's highly likely I've done something wrong here, apologies if that's the case. Reproduction Steps
Ghostty LogsNo response Ghostty VersionOS Version InformationArch linux (Linux only) Display ServerOther (Linux only) Desktop Environment/Window ManagerCosmic 1.0.0 Minimal Ghostty Configurationfont-family="JetBrainsMono Nerd Font"
font-size=12
clipboard-paste-protection = false
app-notifications = no-clipboard-copy
shell-integration-features = ssh-terminfo,no-cursor,sudo,no-title
background-opacity = 0.85
window-decoration = false
window-padding-x = 0
window-padding-y = 0
macos-window-shadow = false
window-padding-balance = true
window-save-state = always
keybind = "ctrl+c=copy_to_clipboard"
keybind = ctrl+v=paste_from_clipboard
keybind = ctrl+shift+c=text:\x03
keybind = "ctrl+shift+v=unbind"
keybind = ctrl+1=goto_tab:1
keybind = ctrl+2=goto_tab:2
keybind = ctrl+3=goto_tab:3
keybind = ctrl+4=goto_tab:4
keybind = ctrl+5=goto_tab:5
keybind = ctrl+6=goto_tab:6
keybind = ctrl+7=goto_tab:7
keybind = ctrl+8=goto_tab:8
keybind = ctrl+9=goto_tab:9
# Splits
keybind = ctrl+shift+enter=new_split:right
keybind = ctrl+shift+_=new_split:down
keybind = ctrl+tab=goto_split:next
# Disable link-url
link-url = falseAdditional Relevant ConfigurationNo response I acknowledge that:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
This is a fundamental issue with SSH that Ghostty can't fix. When you disconnect from an SSH session abnormally, the shell does not have time to reset the terminal back into a known safe state, which is why the output's all garbled (I presume you were using some TUI tool that turned on keyboard and mouse reporting, too). You need to reset the terminal via the "Reset" action in the context menu, or run the |
Beta Was this translation helpful? Give feedback.
This is a fundamental issue with SSH that Ghostty can't fix. When you disconnect from an SSH session abnormally, the shell does not have time to reset the terminal back into a known safe state, which is why the output's all garbled (I presume you were using some TUI tool that turned on keyboard and mouse reporting, too). You need to reset the terminal via the "Reset" action in the context menu, or run the
resetcommand which does the same thing.