GNOME Bugzilla – Bug 612949
contact list is empty for a jabber account with a lot of contacts
Last modified: 2011-08-29 10:12:28 UTC
My Version is 2.29.92-0ubuntu2. I use two different jabber accounts with empathy: The first one is my private jabber account with not so many contacts. The second is our companys jabber account with something like 70~100 contacts in 2 groups. The first works ok, but for the second one, i dont see any of my contacts in my contact list. If both accounts are connected and i disable the first one, the contact list is left empty while my status is available and the connection manager says im still connected. Also restarting empathy does not fix this issue. But sometimes, by randomly disabling and enabling accounts, i am able to get me contacts in the list - a least until the next time i open empathy. This Bug is also reported in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/539023
I just saw i do have a lot of defunct prozesses name empahty-account like these: 2078 ? 00:00:01 empathy-account <defunct> 2082 ? 00:00:00 empathy-account <defunct>
Thanks for your bug report. I'd be interested in seeing Empathy and telepathy-gabble logs when only the buggy account is enabled. If you don't want to attach them for privacy reason feel free to send them to me by mail.
Thanks for taking care. This is a not so smart question, but how do i get those logs?
You can get them from the Debug window available in the Help section. See http://live.gnome.org/Empathy/Debugging
same problem here on ubuntu karmic empathy/ImportMc4Accounts-DEBUG: 03/16/2010 07:36:16.536422: connectivity_nm_state_change_cb: New NetworkManager network state 0 (connected: true) empathy/Dispatcher-DEBUG: 03/16/2010 07:36:16.549839: handler_constructor: Registering at org.freedesktop.Telepathy.Client.Empathy, /org/freedesktop/Telepathy/Client/Empathy empathy/Other-DEBUG: 03/16/2010 07:36:16.558089: empathy_signal_connect_weak: connecting to 0x9bdc160:account-validity-changed with context 0x9f5d2c0 empathy/Dispatcher-DEBUG: 03/16/2010 07:36:16.559662: handler_constructor: Registering at org.freedesktop.Telepathy.Client.EmpathyMoreThanMeetsTheEye, /org/freedesktop/Telepathy/Client/EmpathyMoreThanMeetsTheEye empathy/Other-DEBUG: 03/16/2010 07:36:16.568409: builder_get_file_valist: Loading file /usr/share/empathy/empathy-main-window.ui empathy/Other-DEBUG: 03/16/2010 07:36:17.23660: empathy_signal_connect_weak: connecting to 0x9b16908:changed with context 0x9fd63b0 empathy/Other-DEBUG: 03/16/2010 07:36:17.100620: empathy_signal_connect_weak: connecting to 0x9bdc160:account-validity-changed with context 0x9fdb570 empathy/Other-DEBUG: 03/16/2010 07:36:17.100677: empathy_signal_connect_weak: connecting to 0x9bdc160:account-removed with context 0x9fd9f50 empathy/Other-DEBUG: 03/16/2010 07:36:17.100712: empathy_signal_connect_weak: connecting to 0x9bdc160:account-enabled with context 0x9fdc760 empathy/Other-DEBUG: 03/16/2010 07:36:17.100744: empathy_signal_connect_weak: connecting to 0x9bdc160:account-disabled with context 0x9fdb3d0 empathy/Other-DEBUG: 03/16/2010 07:36:17.100898: empathy_signal_connect_weak: connecting to 0x9c473a0:state-change with context 0x9fdb3c0 empathy/Other-DEBUG: 03/16/2010 07:36:17.125451: builder_get_file_valist: Loading file /usr/share/empathy/empathy-status-icon.ui empathy/Other-DEBUG: 03/16/2010 07:36:17.137516: empathy_notify_manager_init: add capability: actions empathy/Other-DEBUG: 03/16/2010 07:36:17.137550: empathy_notify_manager_init: add capability: body empathy/Other-DEBUG: 03/16/2010 07:36:17.137567: empathy_notify_manager_init: add capability: body-hyperlinks empathy/Other-DEBUG: 03/16/2010 07:36:17.137587: empathy_notify_manager_init: add capability: body-markup empathy/Other-DEBUG: 03/16/2010 07:36:17.137607: empathy_notify_manager_init: add capability: icon-static empathy/Location-DEBUG: 03/16/2010 07:36:17.206326: resource_cb: /apps/empathy/location/resource_network changed empathy/Location-DEBUG: 03/16/2010 07:36:17.207216: resource_cb: /apps/empathy/location/resource_cell changed empathy/Location-DEBUG: 03/16/2010 07:36:17.207983: resource_cb: /apps/empathy/location/resource_gps changed empathy/Location-DEBUG: 03/16/2010 07:36:17.208632: accuracy_cb: /apps/empathy/location/reduce_accuracy changed empathy/Location-DEBUG: 03/16/2010 07:36:17.209234: publish_cb: Publish Conf changed empathy/Location-DEBUG: 03/16/2010 07:36:17.209830: setup_geoclue: Setting up Geoclue empathy/Location-DEBUG: 03/16/2010 07:36:17.213799: update_resources: Updating resources 7 empathy/Location-DEBUG: 03/16/2010 07:36:17.323538: address_changed_cb: New address (accuracy level 0): empathy/Location-DEBUG: 03/16/2010 07:36:17.323597: address_changed_cb: - (Empty) empathy/Location-DEBUG: 03/16/2010 07:36:17.323822: initial_position_cb: Error: Geoclue master client has no usable Position providers empathy/Location-DEBUG: 03/16/2010 07:36:41.523793: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/Other-DEBUG: 03/16/2010 07:36:41.524693: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/Dispatcher-DEBUG: 03/16/2010 07:36:41.525348: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/Contact-DEBUG: 03/16/2010 07:36:41.525995: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/Other-DEBUG: 03/16/2010 07:36:41.526855: update_sensitivity_am_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/Other-DEBUG: 03/16/2010 07:36:41.527503: account_manager_ready_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/Other-DEBUG: 03/16/2010 07:36:41.528117: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/Dispatcher-DEBUG: 03/16/2010 07:36:41.528753: account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/Other-DEBUG: 03/16/2010 07:36:41.529386: account_manager_ready_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/Other-DEBUG: 03/16/2010 07:36:41.530054: account_manager_ready_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
account_manager_prepared_cb: Failed to prepare account manager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Looks like mission control crashed :( Which version of telepathy-mission-control are you using? If you can reproduce could you: - Quit empathy and killall mission-control-5 - export MC_DEBUG=all - gdb /usr/lib/telepathy/mission-control-5 - Once gdb is started type 'r' to start MC - Start Empathy - Paste the log and the trace (type 'bt' in gdb once MC crashed). Thanks a lot.
While Empathy has worked the last few times, today, i was affected by this bug again. From the Empathy logs: empathy/Dispatcher-DEBUG: 03/23/2010 14:49:16.755064: connection_ready_cb: Error: User requested disconnection empathy/Other-DEBUG: 03/23/2010 14:49:16.755636: idle_presence_changed_cb: Presence changed to '(null)' (1) "(null)" empathy/Other-DEBUG: 03/23/2010 14:49:16.904264: main_window_flash_stop: Stop flashing empathy/Contact-DEBUG: 03/23/2010 14:49:18.510869: contact_manager_status_changed_cb: Adding new connection: /org/freedesktop/Telepathy/Connection/gabble/jabber/bgeese_40info_2etarent_2ede_2fLaptop empathy/Other-DEBUG: 03/23/2010 14:49:18.523402: idle_presence_changed_cb: Presence changed to 'available' (2) "" empathy/(null)-DEBUG: 03/23/2010 14:49:18.547457: get_requestable_channel_classes_cb: ContactCapabilities is not implemented; use RCC empathy/(null)-DEBUG: 03/23/2010 14:49:18.547478: get_requestable_channel_classes_cb: Assume all contacts support FT as CM implements it empathy/(null)-DEBUG: 03/23/2010 14:49:18.547482: get_requestable_channel_classes_cb: Assume all contacts support stream tubes as CM implements them empathy/(null)-DEBUG: 03/23/2010 14:49:43.546188: list_ensure_channel_cb: failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/(null)-DEBUG: 03/23/2010 14:49:43.546300: list_ensure_channel_cb: failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/(null)-DEBUG: 03/23/2010 14:49:43.546401: list_ensure_channel_cb: failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. empathy/(null)-DEBUG: 03/23/2010 14:50:02.376780: tp_contact_list_group_ready_cb: Group Systemaccounts added empathy/(null)-DEBUG: 03/23/2010 14:50:02.380947: tp_contact_list_group_ready_cb: Group Mitarbeiter Bonn added empathy/(null)-DEBUG: 03/23/2010 14:50:02.382453: tp_contact_list_group_ready_cb: Group Buddys added empathy/(null)-DEBUG: 03/23/2010 14:50:02.383080: tp_contact_list_group_ready_cb: Group Mitarbeiter Berlin added
Thanks for the log. I think I got the problem. The call fetching contact timeouts out, probably because the server is slow to send the roster to Gabble.
Created attachment 156960 [details] [review] http://git.collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/watch-list-channels-612949 libempathy/empathy-tp-contact-list.c | 117 ++++++++++++++++++++++++++++------ 1 files changed, 97 insertions(+), 20 deletions(-)
*** Bug 612943 has been marked as a duplicate of this bug. ***
Do you think it would be possible for me (with not so much knowledge) to apply this patch to some ubuntu source package to try if it helps? Or is that too much hassle because this will be fixed soon anyway?
You can try to build empathy from git and apply this patch. You can easily run empathy from source by defining EMPATHY_SRCDIR to the path of the source.
I think the handling of incoming contact lists and groups should be handled via the same codepath. Though that might be too invasive a change for 2.30.1.
(In reply to comment #13) > I think the handling of incoming contact lists and groups should be handled via > the same codepath. Though that might be too invasive a change for 2.30.1. That will be for 2.31: bug #614236
Merged; will be in 2.30.1 This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.