[Bug 59668] "Force closing of the connection" for no apparent reason

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=59668

--- Comment #2 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
Do you have more than one XMPP account? If you do, it would be helpful to
disable all of them except the one with the problem while capturing the log.

> (telepathy-gabble:32573): gabble-DEBUG: connector_error_disconnect (connection.c:1772): connection failed: WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): TLS handshake error: -9: GNUTLS_E_UNEXPECTED_PACKET_LENGTH

That might be something to do with it? If the server is getting TLS wrong
somehow, I would expect strange error behaviour.

> (telepathy-gabble:32573): gabble-DEBUG: remote_error_cb (connection.c:1718): Force closing of the connection 0x8309228
> (telepathy-gabble:32573): tp-glib/connection-DEBUG: tp_base_connection_change_status: was 0, now 2, for reason 0

Reason 0 is None_Specified, which is ... unhelpful. remote_error_cb ought to
log a debug message with the error it received, before it translates it into
Telepathy terminology. The next step for anyone who wants to pick this up
(probably not me, I'm afraid) would be to add that debug message.

"Force closing" just means the connection has basically already died, and now
we're cleaning up the mess.

> In Telepathy/KDE the symptom is the message "The connection was cancelled on your request", without the user making any request.

I would expect this to mean TP_CONNECTION_STATUS_REASON_REQUESTED, which is 1,
but I don't see any changes to status 2 (DISCONNECTED) for reason 1 (REQUESTED)
in your log: the only changes to status 2 that I can see are for reasons 0
(NONE_SPECIFIED) or 2 (NETWORK_ERROR).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.