After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 612943 - Show connected when apparently disconnected
Show connected when apparently disconnected
Status: RESOLVED DUPLICATE of bug 612949
Product: empathy
Classification: Core
Component: Contact List
2.29.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-03-15 14:38 UTC by Olivier Le Thanh Duong
Modified: 2010-03-24 11:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
logs (95.61 KB, text/x-log)
2010-03-20 01:01 UTC, Olivier Le Thanh Duong 		Details

Description Olivier Le Thanh Duong 2010-03-15 14:38:59 UTC 
using Empathy 2.29.92.20100312 and mission control 5.3.2-2~ppa9.10+1

Empathy show me as connected, several gabble and butterfly account are enabled (and are show as connected in the account dialog) but the Contact list is entirely empty (even when showing offline contact) and the previously open chat windows with contact don't show any status for them. Gabble log indicate it still connected but butterfly log don't.

After noticing the condition, when receiving a message from gabble the chat windows display correctly and show the contact as online however he is still not in the contact list.

After killing and relaunching empathy everything seems back  to normal
Comment 1 Jonny Lamb 2010-03-15 14:55:05 UTC 
MC might have crashed?
Comment 2 Guillaume Desmottes 2010-03-16 08:47:26 UTC 
logs please?
Comment 3 Olivier Le Thanh Duong 2010-03-20 01:01:33 UTC 
Created attachment 156600 [details]
logs

sorry I apparently forgot to attach them
Comment 4 Guillaume Desmottes 2010-03-22 10:23:36 UTC 
Humm this log doesn't contain contact list information so it's not really helpful :\
Comment 5 Guillaume Desmottes 2010-03-24 11:02:31 UTC 
Closing as a dup assuming that's the same issue as bug #612949 as I can't really tell more without full logs.

*** This bug has been marked as a duplicate of bug 612949 ***