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
Do you use network manager? Can you give me the output of "mc-tool dump | grep Presences -A 4"
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
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.
Created attachment 89240 [details] ktp-debugger, name redacted Thanks for looking into this!
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?!
(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?
Highlighting interesting parts of the logs. I'm not sure what's up at the moment; make sure you have latest telepathy-gabble.
telepathy-gabble is at 0.18.3-1.2.
Mission Control upstream handles reconnecting. This open Telepathy bug seems to describe this issue: https://bugs.freedesktop.org/show_bug.cgi?id=45531.