Bug 340201

Summary:	KTP doesn't reconnect after resume from suspend
Product:	[Unmaintained] telepathy	Reporter:	S <sb56637>
Component:	general	Assignee:	Telepathy Bugs <kde-telepathy-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	kde, simonandric5, smithjd15
Priority:	NOR
Version First Reported In:	git-latest
Target Milestone:	Future
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	ktp-debugger, name redacted

Description S 2014-10-21 16:31:26 UTC

Hi,

After connecting to my Google Talk account in KTP, I suspend my laptop. After resuming and re-connecting to the WiFI, KTP doesn't re-connect. Additionally, it still shows some of my contacts as though they were online, whereas others it shows as offline. In reality, it has still not reconnected.

This behavior happens every time.

Thanks for looking into it!

Reproducible: Always

Comment 1 David Edmundson 2014-10-21 16:32:46 UTC

Do you use network manager?

Can you give me the output of "mc-tool dump | grep Presences -A 4"

Comment 2 S 2014-10-21 16:35:43 UTC

I should have mentioned that this bug is for KTP 0.9.0 from openSUSE KDE:Extra.

Yes, I use NetworkManager.

Here is "mc-tool dump | grep Presences -A 4" in the state after resume, where it shows some contacts as connected and others offline when in reality KTP has not re-connected:
-----------------------------------------
Presences:
   Automatic: available (2) ""
     Current: offline (1) ""
   Requested: available (2) ""
    Changing: yes

Comment 3 David Edmundson 2014-10-21 16:39:52 UTC

Weird, it should be trying to reconnect. We've got our requested presence to available.

running ktp-debugger and looking in the tabs "mission control" and "gabble" might list  something useful, could you have a look?

You can attach them here for me to look, but note the gabble log will contain contact IDs + potentially messages. No passwords though.

Comment 4 S 2014-10-21 16:46:30 UTC

Created attachment 89240 [details]
ktp-debugger, name redacted

Thanks for looking into this!

Comment 5 David Edmundson 2014-10-21 16:47:34 UTC

10/21/2014 11:23:39.481801 - [mcd] emit_property_changed: called
10/21/2014 11:23:39.482063 - [mcd] connection_should_reconnect: TpError code org.freedesktop.Telepathy.Error.NotAvailable not handled
10/21/2014 11:23:39.482068 - [mcd] connection_should_reconnect: not reconnecting

What?!

Comment 6 S 2014-10-21 16:52:21 UTC

(In reply to David Edmundson from comment #5)
> 10/21/2014 11:23:39.481801 - [mcd] emit_property_changed: called
> 10/21/2014 11:23:39.482063 - [mcd] connection_should_reconnect: TpError code
> org.freedesktop.Telepathy.Error.NotAvailable not handled
> 10/21/2014 11:23:39.482068 - [mcd] connection_should_reconnect: not
> reconnecting
> 
> What?!

:/ Sorry, configuration issue on my end?

Comment 7 David Edmundson 2014-10-21 16:55:12 UTC

Highlighting interesting parts of the logs.
I'm not sure what's up at the moment; make sure you have latest telepathy-gabble.

Comment 8 S 2014-10-21 17:00:01 UTC

telepathy-gabble is at 0.18.3-1.2.

Comment 9 Jamie Smith 2018-02-10 00:31:51 UTC

Mission Control upstream handles reconnecting. This open Telepathy bug seems to describe this issue: https://bugs.freedesktop.org/show_bug.cgi?id=45531.