Comment 5 for bug 790774

I don't know why this was closed for inactivity. I provided the information I was asked for, so this hould not have remnained in the Incomplete state in the first place.

I can still reproduce this, systematically, and I have observed it on several machines and with several servers (with different linux distributions and from different hosting providers). So I'm going to change this to "confirmed".

There is one thing worth noting, though: this seems to happen when the client is connected via WIFI (to a LAN connected to the Internet, of course), but not when connected via an ethernet cable.
So, I guess this may be triggered by a network connection issue, not by the server closing the connection?
In ANY case, the client should show a meaningful error message and quit, if the connection really is broken: not doing so is a bug for sure; and it doesn't seem there's a good reason for it breaking in the first place, either.

@zulcss please could you try if you can reproduce it when connected via wifi?