Opened 12 years ago

Closed 12 years ago

#2114 closed bug (WontFix)

Connection manager shows wrong info when connected to localhost

Reported by: bro Owned by:
Priority: minor Milestone: 1.3.6
Component: GTK UI Version: 1.3.5
Keywords: Cc:


The problem is that the code distinguishes between localhost and when comparing the hosts.

There are two issues:

1) The gtk-client can connect to localclient@localhost:58846 on startup but an entry in the connection manager with localclient@ will show as not connected.

2) When adding a new host, it's possible to add localclient@ if localclient@localhost:58846 is already in the list, and the other way around.


This fix has not been extensively tested, but worked as expected when tested on Ubuntu. The only thing I expect could matter is that in the method update_list, the variable host is changed, and later passed to Client.connect().

Change History (3)

comment:1 Changed 12 years ago by gazpachoking

Is this really an issue? If you are adding multiple entries for localhost you should know the difference. Even if patch is implemented you could still use the local hostname and exhibit the same problem. Also, you could have an ssh tunnel from to a remote host (although this will cause problems with the path picker.)

comment:2 Changed 12 years ago by bro

Yeah, I agree. There are other things to focus on ;-) Pleas close this if you like.

comment:3 Changed 12 years ago by gazpachoking

  • Resolution set to wontfix
  • Status changed from new to closed

Yeah, to get it perfect we'd have to be looking at hostname/ip, port, and username. Plus with the port forwarding issue I think it's just best to show connected to the daemon the user clicked connect on.

Note: See TracTickets for help on using tickets.