Reverting to 2.1.3 results in the same issue (which was definitely NOT the case before)...
I'll restart now and report back.
Restarting appears to have fixed the problem. I've never seen this before; does the OS service that handles this authentication dialog sometimes get messed up? I wonder if simply logging out and logging back in would fix the problem as well...
Anyway, thanks for the quick (and very useful!) reply!
