Project

General

Profile

Bug #1131

Quasselcore believes a socket is not connected when it is

Added by TerrorBite almost 13 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Quassel Core
Target version:
-
Start date:
01/01/2012
Due date:
% Done:

0%

Estimated time:
Version:
0.7.2
OS:
Linux

Description

Rarely (apparently after a failed connection attempt), the QAbstractSocket will get stuck in a "connecting/connected" state while the Quassel network state will be "Disconnected". This results in the core printing errors like the following, and no connection to that network can be made (there is no way to cancel the failed connection attempt, short of deleting the network or restarting the core):

2012-01-01 03:53:10 Warning: QAbstractSocket::connectToHost() called when already connecting/connected to "irc.example.com"

Quassel only has "Connected" and "Disconnected" states. It needs a third "Connecting" network state that allows an in-progress connection attempt to be cancelled.

Possibly related to #1005

Quasselcore version: 0.7.3 git-7db97a6
Quasselclient version: 0.7.1 dist-aa28596 (Ubuntu)

Also available in: Atom PDF