I have configured an account on VKontakte.ru without adding any contacts, and then configured XMPP access in Empathy as described here: http://vk.com/help.php?page=jabber You have to be logged in with your VKontakte account to get a user ID on this page. Also, you need to use host name vkmessenger.com as the claimed SRV records are not there. After connecting, gabble fails an assertion after receiving the roster stanza: (telepathy-gabble:9523): wocky-DEBUG: _end_element_ns: Received stanza * iq xmlns='jabber:client' to='id160570475@vk.com/644940c2' type='result' id='6583075243' " " * query xmlns='jabber:iq:roster' (telepathy-gabble:9523): tp-glib/groups-DEBUG: change_members: not emitting signal, nothing changed (telepathy-gabble:9523): tp-glib/groups-DEBUG: change_members: not emitting signal, nothing changed (telepathy-gabble:9523): tp-glib/groups-DEBUG: change_members: not emitting signal, nothing changed (telepathy-gabble:9523): tp-glib/groups-DEBUG: change_members: not emitting signal, nothing changed (telepathy-gabble:9523): tp-glib/groups-DEBUG: change_members: not emitting signal, nothing changed (telepathy-gabble:9523): tp-glib/presence-DEBUG: tp_presence_mixin_emit_presence_update: called. (telepathy-gabble:9523): tp-glib/presence-DEBUG: construct_simple_presence_hash: called. tp-glib-CRITICAL **: tp_base_contact_list_set_list_received: assertion `self->priv->state != TP_CONTACT_LIST_STATE_SUCCESS' failed
Not critical as most users have contacts in their rosters by the time they want to chat :)
*** Bug 43860 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/200.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.