This is a high priority bug. Scenario: - User A leaves themselves connected to Remote Machine then goes away from their local machine - User B has a high priority reason to connect to Remote Machine, so User B connects, disconnecting User A - Since User A is not around to click cancel, their TSC automatically reconnects, kicking off User B in the middle of something critical - repeat ad infinitum
In a production environment this is a very big deal. Also, what's the point in this feature anyway? If you're at your machine when you get disconnected you can click reconnect manually, and you can do so straight away so you're never going to use the timed auto- reconnect anyway, and if you're not at your machine you can't click cancel (even though if you're not there to click cancel there's no point connecting, and if you were there to click cancel then it wouldn't need to be automated). It seems as though this feature is there solely to create problems. -- Logging off causes error on client https://bugs.launchpad.net/bugs/124348 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
