Some sound settings need to be in AccountsService

[Michael Terry]

Sound settings like volume and ringtone need to be accessible to the greeter once we split it. Thus, they should be stored in AS instead of gsettings (or at least in addition to).

This is not a v1-phone bug, but for the future.

[Sebastien Bacher (seb128)]

Does it mean that we intend to have those being "by user settings"? What would happen if the screen is locked, would you get the ringtone of the user selected in the greeter? It seems like it would be easier for the sound settings to just let the system value be changed/stored (do we have per user settings on the desktop working?)

[Michael Terry (mterry)]

I don't know what it means for multi-user environments that have a SIM card. I think there are lots of open questions around that in general (like, which user's addressbook do you ask for a picture/name for the incoming call in the greeter?).

We could store it in a system location if you like that better. Could still be done in AS if we like (using a custom setting that everyone only sets sets/gets on the "lightdm" user or some such, though that is a very greeter-oriented suggestion). Or some other more appropriate system daemon. Either way, we'd want sane "admin" policykit settings for the setting.

[Michael Terry (mterry)]

I do remember an open bug a while back, where design wanted per-user sound settings to appear in the greeter though. So for volume, being per-user might still be desired.

[Lars Karlitski (larsu)]

We've decided that volume should be a device-wide setting and thus not be stored in AccountsService. Matthew agrees with that. Seee bug #840777 for the pulseaudio task.

This bug still applies for other settings, such as ring tones.

[Sebastien Bacher (seb128)]

The settings part has been implemented right?

[Sebastien Bacher (seb128)]

I think that is fixed, feel free to reopen if that's not the case though