OK, I looked at this but got confused. The upower dbus interface we currently
have on the desktop & phone doesn't offer any interesting methods or setters
(all the properties are read-only).
The denied calls mentioned in the bug report are only using
EnumerateDevices/Get* methods and should disappear once you use the existing
upower-observe interface.
After a short IRC discussion it seems we need to better understand
what's needed from ubuntu-system-settings pov to control the aspects
related to power management.
<jgdx> you're right. Following the path to changing brightness is a dazzling
one, I end up in gnome-settings-daemon in a file called gsd-backlight-helper.c,
which uses udev
<jgdx> so I don't know what's ultimately needed, policy wise
<jgdx> but USS's use of powerd seems to be a mixtures of reads and gsettings.
<jgdx> I can't say for sure what indicator-brightness does, however, which USS
use.
** Changed in: snapd (Ubuntu)
Status: In Progress => Incomplete
** Changed in: snapd (Ubuntu)
Importance: High => Undecided
** Changed in: snapd (Ubuntu)
Assignee: Paweł Stołowski (stolowski) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616045
Title:
Create interface for the power daemon
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1616045/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
