When a storage backend (such as libaccounts/sso) alters a non-parameter (such as Nickname), the new value may not get propagated to CMs until they restart.
I can't help thinking that the whole account-storage API needs a redesign... but this looks a reasonable approach to getting the desired side-effect of changing a property. One thing that's a bit wrong: > + if (prop->setprop != NULL) > + prop->setprop (self, prop->name, &value, NULL); > + > + /* now emit our own property changed signal directly */ > mcd_account_changed_property (account, prop->name, &value); The Set() implementation for every mutable property should be calling mcd_account_changed_property already (e.g. for Nickname this is via mcd_account_set_string_val).
... so you shouldn't need to call mcd_account_changed_property explicitly any more, is what I meant to say.
(In reply to comment #2) > ... so you shouldn't need to call mcd_account_changed_property explicitly any > more, is what I meant to say. Amended, rebased, pushed.
r+
Released in 5.7.10
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.