@seb128: I agree that AS is less good for us than gsettings in at least the following important ways: 1) it is harder for admins to change the default value of custom properties 2) there is not yet a friendly get/set command line tool 3) libaccountsservice hasn't yet added API for custom properties 4) correctly setting the permissions for properties to be only shared with the lightdm user is easy to forget to do
But on the other hand, for our "sharing info with greeter" use case, I think it's a necessary evil. As for making it more optimal: #1 can be managed with diverts, #2 can be fixed with a small amount of effort, #3 with a bit more effort, and #4 could be fixed by installing a common policykit policy that could be referenced by all custom properties that are for lightdm. Given that storing config in AS is a necessary evil and that synchronization adds all sorts of new problems, I would prefer to avoid synchronization where possible and just use AS as the canonical store for configuration that needs to be shared with the greeter. About bug 1237642, I did forget that I mentioned ring tone in that bug when I was filing this one. I was thinking that this bug was for ring tone and that one for volume/mute. But both ring tone and volume settings need the same treatment. If you'd like to dup one of the bugs that's fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1265528 Title: Share ring tone with greeter via AccountsService To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1265528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
