On Wed, Mar 26, 2014 at 03:48:11PM -0000, Michael Terry wrote: > So I gathered from an IRC conversation that the goal here is just to > have unity8 proxy that setting to powerd to avoid regressions. And not > worry about the multiple-unity8-process problem until a later merge that > moves that logic into USC.
It's mainly because the setting needs to be applied at login, when system-settings can't do it. > Is that right? AFAIK yes -- Iain Lane [ [email protected] ] Debian Developer [ [email protected] ] Ubuntu Developer [ [email protected] ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-ubuntu-touch-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1273174 Title: Manage auto brightness synchronisation Status in The Unity 8 shell: Triaged Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “unity-system-compositor” package in Ubuntu: New Bug description: powerd doesn't handle the saving or restoring of the automatic brightness boolean itself. Something else (likely unity8) should do this. I'm adding a GSettings boolean which should be monitored and synchronised to powerd using userAutoBrightnessEnable on its D-Bus API. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1273174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
