| Summary: | stored/local-pending/RemoveMembers doesn't trigger publish/MembersChanged | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Danielle Madeley <danielle> |
| Component: | gabble | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 0.8 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Subscription Request Decline Problem | ||
Created attachment 37178 [details]
Subscription Request Decline Problem
Visual indicator for failed decline subscription request.
(In reply to comment #1) > Created an attachment (id=37178) [details] > Subscription Request Decline Problem > > Visual indicator for failed decline subscription request. This is a bug filed against Gabble, but I think your screenshot shows a similar issue for Yahoo accounts, which are implemented using Haze. Could you file a separate bug for Haze? Superseded by contact lists. |
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.
When you decline a subscription request in Empathy, it calls RemoveMembers on stored. method call sender=:1.144 -> dest=:1.467 serial=6089 path=/org/freedesktop/Telepathy/Connection/gabble/jabber/danielle_2emadeley_40collabora_2eco_2euk_2fadelie/RosterChannel/List/stored; interface=org.freedesktop.Telepathy.Channel.Interface.Group; member=RemoveMembers array [ uint32 83 ] string "" Which triggers MembersChanged and MembersChangedDetailed on stored signal sender=:1.467 -> dest=(null destination) serial=700 path=/org/freedesktop/Telepathy/Connection/gabble/jabber/danielle_2emadeley_40collabora_2eco_2euk_2fadelie/RosterChannel/List/stored; interface=org.freedesktop.Telepathy.Channel.Interface.Group; member=MembersChanged string "" array [ ] array [ uint32 83 ] array [ ] array [ ] uint32 0 uint32 0 But the request stays pending in publish/local-pending until you restart Gabble. This means that if you attempt to rerequest authorisation, Empathy doesn't notice, because the contact doesn't appear again in publish. Is Empathy wrong, by not removing the handle from publish, or is Gabble wrong by not propagating to the other lists?