When starting a process and watching its output, we shouldn't do this in a separate thread but instead integrate the code with twisted main-loop (gtk/glib's actually) using ProcessProtocol?, see ​here

Also, when waiting for a process by pid (one we may not have launched ourselves), we should use gobject.child_watch_add(pid) which will also integrate with the main loop.

Places of interest:

• 1 ssh_key_util.generate_new_key: simple call_when_done callback
• 2 config_server.do_tunnel_connect_test: simple call_when_done callback (needs output and returncode)
• 3 ssh_command_monitor: needs every line to be parsed as they are received...
• 4 server_link.do_connect_to_server: re-implements wait_for_socket!!!

The command used for toggling ARD on or off requires authentication, at the moment we don't keep the password (we should - but only for platforms that are known to require it: osx) and we need a way to request it if we do not have it (key login).

Then we can use the password to enable ARD if it is not enabled (and potentially other things - auto-start?)

See ​https://xpra.org/trac/ticket/43#comment:23

Probably need to duplicate the workarounds to get Ubuntu to stop doing crazy things.