New issue
Advanced search Search tips

Issue 895545 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 728275
Owner: ----
Closed: Oct 15
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

hterm: when connection dies, it gets stuck blinking "Retrying..." and there is no way to get it to actually retry

Project Member Reported by chrismacgregor@google.com, Oct 15

Issue description

Secure Shell App Version: 0.8.45
Chrome Version: 69.0.3497.100 (Official Build) (64-bit)
OS: Linux (Debian-based, gLinux)

What steps will reproduce the problem?
(1) Connect (via Google relay)
(2) Use until connection is ended without warning (even while I'm in the middle of typing something)
(3) Observe that a blinking "Retrying..." appears

What is the expected result?

Ideally, it would ask me what to do, or would try to reconnect, and if that fails, would then ask me what to do - perhaps something similar to when I disconnect manually, and then have the prompt to "(R)econnect, (C)hoose another connection, or E(x)it?"

The next best thing would be if there was some key sequence that would get it out of the infuriatingly useless and unresponsive "Retrying..." state and get it to prompt me (as above).

What happens instead?

It is stuck in the "Retrying..." state, never successfully reconnects or does anything else useful, and does not respond in any useful way to any key sequence I've tried except shift-ctrl-N to start a new window (which doesn't appear in the same place).

If it can respond to that, why can't there be a key sequence that gets it to reconnect?

If someone can point me to the right area in the code, I can probably write a patch to fix this.

But please, I need a fix for this somehow - I have to work from home a lot, and this problem is driving me crazy.
 
Mergedinto: 728275
Status: Duplicate (was: Untriaged)
the ~. escape sequence should work

our servers don't support retrying
I don't need it to retry, just give me a way to re-connect (which obviously does work, because that option is available - and works! - whenever I disconnect manually).

Sign in to add a comment