[GH-ISSUE #2657] Connection loss within the application after display is off #1729

New issue

Open

opened 2026-02-27 00:04:37 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 00:04:37 +03:00

Owner

Originally created by @markvandennieuwenhuizen on GitHub (Oct 6, 2022).
Original GitHub issue: https://github.com/electerm/electerm/issues/2657

Electerm Version and download file extension(Electerm版本和下载文件后缀)

1.23.8 electerm-1.23.8-mac-arm64.dmg

Platform detail (平台详情)

macbook air m2 Monterey

What steps will reproduce the bug?(重新问题的详细步骤)

open new local terminal (or any ssh connection)
wait for display off
activate display
need to reload the tab to get connected

What should have happened?(期望的结果)

open new local terminal (or any ssh connection)
wait for display off
activate display
connection intact

Would this happen in other terminal app(是否能够在其他同类软件重现这个问题)

Have tested same in native terminal, iTerm2 and Termius. No disconnect was observed

Additional information(其他任何相关信息)

No response

Originally created by @markvandennieuwenhuizen on GitHub (Oct 6, 2022). Original GitHub issue: https://github.com/electerm/electerm/issues/2657 ### Electerm Version and download file extension(Electerm版本和下载文件后缀) 1.23.8 electerm-1.23.8-mac-arm64.dmg ### Platform detail (平台详情) macbook air m2 Monterey ### What steps will reproduce the bug?(重新问题的详细步骤) open new local terminal (or any ssh connection) wait for display off activate display need to reload the tab to get connected ### What should have happened?(期望的结果) open new local terminal (or any ssh connection) wait for display off activate display connection intact ### Would this happen in other terminal app(是否能够在其他同类软件重现这个问题) Have tested same in native terminal, iTerm2 and Termius. No disconnect was observed ### Additional information(其他任何相关信息) _No response_

kerem added the

need investigate

label

2026-02-27 00:04:37 +03:00

kerem commented

2026-02-27 00:04:38 +03:00

Author

Owner

@markvandennieuwenhuizen commented on GitHub (Oct 7, 2022):

Same behaviour observed from v1.22.20 onwards

@markvandennieuwenhuizen commented on GitHub (Oct 7, 2022): Same behaviour observed from v1.22.20 onwards

kerem commented

2026-02-27 00:04:38 +03:00

Author

Owner

@markvandennieuwenhuizen commented on GitHub (Oct 11, 2022):

Please let me know if I can help with e.g. debugging. Electerm is by the far the best application and I would really like to use it.

@markvandennieuwenhuizen commented on GitHub (Oct 11, 2022): Please let me know if I can help with e.g. debugging. Electerm is by the far the best application and I would really like to use it.

kerem commented

2026-02-27 00:04:38 +03:00

Author

Owner

@markvandennieuwenhuizen commented on GitHub (Oct 18, 2022):

I ran electerm from the terminal and this is where the connection is lost:

15:03:54 info › Inbound: Received REQUEST_FAILURE
15:03:55 info › Outbound: Sending ping (GLOBAL_REQUEST: keepalive@openssh.com)
15:03:56 info › Inbound: Received REQUEST_FAILURE
15:03:57 info › Outbound: Sending ping (GLOBAL_REQUEST: keepalive@openssh.com)
15:03:57 info › Inbound: Received REQUEST_FAILURE
15:03:58 info › Outbound: Sending ping (GLOBAL_REQUEST: keepalive@openssh.com)
15:03:58 info › Inbound: Received REQUEST_FAILURE
15:03:58 info › Outbound: Sending CHANNEL_EOF (r:0)
15:03:58 info › Outbound: Sending DISCONNECT (11)
15:03:58 debug › Closed terminal gWKxkML
15:03:58 debug › Closed terminal NHBZh7W
15:03:58 debug › Closed terminal NHBZh7W
15:03:58 info › Socket ended
15:03:58 info › Socket closed
15:03:58 debug › Closed terminal gWKxkML
15:03:58 info › Outbound: Sending CHANNEL_CLOSE (r:0)
15:03:58 debug › Closed terminal gWKxkML

So this is not an issue but i guess a feature request: make the host to ping configurable or disable keepalive interval

I now used the default value for the keep alive interval 20000 ms but now it will only take longer to disconnect :-(

@markvandennieuwenhuizen commented on GitHub (Oct 18, 2022): I ran electerm from the terminal and this is where the connection is lost: 15:03:54 info › Inbound: Received REQUEST_FAILURE 15:03:55 info › Outbound: Sending ping (GLOBAL_REQUEST: keepalive@openssh.com) 15:03:56 info › Inbound: Received REQUEST_FAILURE 15:03:57 info › Outbound: Sending ping (GLOBAL_REQUEST: keepalive@openssh.com) 15:03:57 info › Inbound: Received REQUEST_FAILURE 15:03:58 info › Outbound: Sending ping (GLOBAL_REQUEST: keepalive@openssh.com) 15:03:58 info › Inbound: Received REQUEST_FAILURE 15:03:58 info › Outbound: Sending CHANNEL_EOF (r:0) 15:03:58 info › Outbound: Sending DISCONNECT (11) 15:03:58 debug › Closed terminal gWKxkML 15:03:58 debug › Closed terminal NHBZh7W 15:03:58 debug › Closed terminal NHBZh7W 15:03:58 info › Socket ended 15:03:58 info › Socket closed 15:03:58 debug › Closed terminal gWKxkML 15:03:58 info › Outbound: Sending CHANNEL_CLOSE (r:0) 15:03:58 debug › Closed terminal gWKxkML So this is not an issue but i guess a feature request: make the host to ping configurable or disable keepalive interval I now used the default value for the keep alive interval 20000 ms but now it will only take longer to disconnect :-(