Bagoro / connectbot

Automatically exported from code.google.com/p/connectbot
Apache License 2.0
0 stars 0 forks source link

Closing a "local" session immediately relaunches another local session #165

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open a "local" session
2. Type 'exit', or use the "Disconnect" menu option
3. Find yourself back at a local session prompt.

What is the expected output? What do you see instead?

When there are no other sessions open, and a "local" session is
disconnected, the screen briefly shows the "no sessions currently
connected" message, and then instead of returning to the hosts screen as
expected, just launches a new local session.  The only way to close a local
session without starting a new one appears to be to use the back button to
get to the hosts screen, and then disconnecting it from there.

Another side-effect is that it ends up adding a new "Local" entry to the
hosts screen's list every time this auto-restart occurs, so after trying
(and failing) to get out of a local session several times, I eventually
made it back to the hosts screen to find five "Local"s listed there.

What version of the product are you using (you can see this by using Menu
-> About in the Host List)?

ConnectBot 1.5.4 (r346 2009.06.30)

What type of system are you trying to connect to?

Local connection

If you are able to connect, what is the output of "echo $TERM", "uname -a",
and any other relevant information on the host?

N/A

Please provide any additional information below.

Original issue reported on code.google.com by foogod@gmail.com on 10 Jul 2009 at 1:05

GoogleCodeExporter commented 9 years ago
I can confirm this.

Original comment by thelinxswe on 15 Jul 2009 at 1:44

GoogleCodeExporter commented 9 years ago
i can confirm this also

Original comment by Vaelen...@gmail.com on 21 Jul 2009 at 4:53

GoogleCodeExporter commented 9 years ago
This happens when "local" is selected in the quick-connect spinner and is 
probably
triggered when the spinner is updated in a race condition with the on change 
listener.

Original comment by kenny@the-b.org on 14 Aug 2009 at 11:26

GoogleCodeExporter commented 9 years ago
This should be fixed in r396

Original comment by kenny@the-b.org on 14 Aug 2009 at 12:18