#581 mod_groups: roster broken after deleting group in pidgin
Reporter
Frank Herren
Owner
MattJ
Created
Updated
Stars
★ (1)
Tags
Type-Defect
Priority-Medium
Status-New
Frank Herren
on
After deleting the group (tag, roster etc) in pidgin the roster seems to be out of sync when I log back in (even in another client like converse).
These are the steps I took to reproduce the issue:
delete group in pidgin, logout, login, everyone offline (prosody debug log responds with load_roster from everyone that's online and everything looks normal), login to webclient (conversejs), also noone online. if someone logs in afterwards it adds them and i see that they are online.
The only thing that helps is to restart the prosody service. I'm guessing that's because everyone resends their presence status. I'm not sure this will present a problem in production, but it seems weird. I am using the mod_auth_ldap module, but authentication works without problems so that shouldn't matter
Frank Herren
on
I forgot to mention that I tried reloading the roster and groups module.
Zash
on
Thanks for the report, sorry that we haven't responded to it until now.
Roster items provided by mod_groups are read-only, it is not surprising that weird things happens if you change them.
Assigning to MattJ so he can look at it at some point.
After deleting the group (tag, roster etc) in pidgin the roster seems to be out of sync when I log back in (even in another client like converse). These are the steps I took to reproduce the issue: delete group in pidgin, logout, login, everyone offline (prosody debug log responds with load_roster from everyone that's online and everything looks normal), login to webclient (conversejs), also noone online. if someone logs in afterwards it adds them and i see that they are online. The only thing that helps is to restart the prosody service. I'm guessing that's because everyone resends their presence status. I'm not sure this will present a problem in production, but it seems weird. I am using the mod_auth_ldap module, but authentication works without problems so that shouldn't matter
I forgot to mention that I tried reloading the roster and groups module.
Thanks for the report, sorry that we haven't responded to it until now. Roster items provided by mod_groups are read-only, it is not surprising that weird things happens if you change them. Assigning to MattJ so he can look at it at some point.
Changes