Andreas Mohr - 2014-09-06

I would want to strongly second this. During a couple months of use, I also had to go through about 5 times of accidental closing. A confirmation is especially desirable since closing in some cases may also have unwanted consequences:

Win7 appears to possibly have issues upon an RDP session close as done via Close Box here (c.f. several Internet reports about generic error message "The number of connections to this computer is limited and all connections are in use right now." as encountered during Win7 session logon).
This happened to me at my last Close Box catastrophy recently, and I was NOT able to cure this problem in a benign way - reboot (i.e., session loss!) was the only way to regain login capability of the affected user (and BTW, even login at the local console!! E.g. local Win 7 logon will eventually just display another message that rdesktop services are experiencing trouble, and "logging in with another user should be unaffected" - hah!).

So (phew!), a way to avoid accidental Close Box close would be very desirable, to say the least.

Now the question would be how to implement that:
- add a command line option to configure Close Box behaviour (possibly -Q would be an appropriate option char to use, since several other desirable candidates such as cCxX are taken)
- modes: a) user prompt dialog (see dialog description above), b) don't ask for confirmation, c) disallow Close Box functionality (not sure whether that's even useful/allowable)
- decision on which Close Box mode ought to be the default (one could argue that the future default should match current behaviour, i.e. a no-prompt closing, but given the issues I'd strongly favour a config change into having a safe setting as the default, i.e. the user prompt dialog)


Andreas Mohr