QSocketNotifier for write triggers without connection.

Using MSys Mingw32, I have a non-blocking TCP socket created using the Berkeley sockets API. It is trying to connect to 127.0.0.1:50050. There is no service listening on that port at all. I am using QSocketNotifier instances for read, write, and error on the socket, instantiating and connecting them to the socket after calling connect().

Almost exactly 2 seconds after the call to connect(), the QSocketNotifier for write activates. There is definitely no connection, so this should not happen.

I have a different application that uses the same library, but uses select() to poll the sockets. It reports a socket error after 2 seconds.

It looks like Qt is reporting a WRITE state when it should be reporting an ERROR state on failing to connect to a port on the localhost.