Bug 44055 - Doesn't receive last published PEP items when connecting
Summary: Doesn't receive last published PEP items when connecting
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-22 06:38 UTC by Guillaume Desmottes
Modified: 2019-12-03 19:54 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
test script (1.94 KB, text/x-python)
2011-12-22 06:49 UTC, Guillaume Desmottes
Details

Description Guillaume Desmottes 2011-12-22 06:38:11 UTC
It looks like servers don't send us the last published item when connecting any more. Gabble relying on this to populates its cache, that means we don't get the location from any contact.

I observed this with jabber.belnet.be (running ejabberd) and Collabora's XMPP server (running prosody) so that's probably not a server bug.

Did we change the way we announce our caps to the server? Servers don't send the last published items when we add the +notify feature to our caps afterward; see http://mail.jabber.org/pipermail/pubsub/2010-July/000692.html
Comment 1 Guillaume Desmottes 2011-12-22 06:49:18 UTC
Created attachment 54698 [details]
test script

Here is a small script I hacked to bump the location of all contacts (including our own).
Comment 2 GitLab Migration User 2019-12-03 19:54:52 UTC
-- 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/197.


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.