[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 #3 from Dennis Schridde <devurandom at gmx.net> ---
(In reply to comment #2)
> 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.
I already disabled all of them but the Facebook account.

> > (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.
I assume this is one of the network errors that Telepathy reported, before it
was able to connect the first time.

That is this part of my original report:
> First some network errors appeared, until Telepathy was finally able to
> establish a connection - maybe that is another bug, but at least it is 
> probably not related.

If you already kept that in mind while reading the log, of course this might be
the actual reason.

> > 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).
So there are two bugs? For one Telepathy disconnects for unknown reasons, and
then Telepathy/KDE also displays a wrong and misleading message about it?

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