SIGTERM sent when Windows Terminal exits due to error #14181

Closed
opened 2026-01-31 04:03:10 +00:00 by claunia · 0 comments
Owner

Originally created by @huili80 on GitHub (Jun 9, 2021).

Windows Terminal version (or Windows build number)

10.0.18363.1556

Other Software

No response

Steps to reproduce

Change the name of the session in settings while it's actively running and ssh-ed to a remove linux host

Expected Behavior

It appears to run into error due to the session name change, and subsequently shutdown, which is fine. But I'd expect SIGHUP being sent to the remote session.

Actual Behavior

SIGTERM appears to have been sent to the remote session.

Originally created by @huili80 on GitHub (Jun 9, 2021). ### Windows Terminal version (or Windows build number) 10.0.18363.1556 ### Other Software _No response_ ### Steps to reproduce Change the name of the session in settings while it's actively running and ssh-ed to a remove linux host ### Expected Behavior It appears to run into error due to the session name change, and subsequently shutdown, which is fine. But I'd expect SIGHUP being sent to the remote session. ### Actual Behavior SIGTERM appears to have been sent to the remote session.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 04:03:11 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14181