Hello Gabriel, or anyone else affected,

Accepted adsys into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~20.04 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: adsys (Ubuntu Focal)
       Status: New => Fix Committed

** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/1982349

Title:
  Manage energy profile settings

Status in adsys package in Ubuntu:
  Fix Released
Status in adsys source package in Focal:
  Fix Committed
Status in adsys source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Adsys cannot currently manage GSettings power management keys, such
  as:

  /org/gnome/settings-daemon/plugins/power/ambient-enabled
  /org/gnome/settings-daemon/plugins/power/idle-brightness
  /org/gnome/settings-daemon/plugins/power/idle-dim
  /org/gnome/settings-daemon/plugins/power/lid-close-ac-action
  /org/gnome/settings-daemon/plugins/power/lid-close-battery-action
  
/org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor
  /org/gnome/settings-daemon/plugins/power/power-button-action
  /org/gnome/settings-daemon/plugins/power/power-saver-profile-on-low-battery
  /org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout
  /org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type
  /org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
  /org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type

  [Test Plan]

  * Open the Group Policy Management Editor for a configured policy
  * Navigate to Computer Configuration > Administrative Templates > Ubuntu > 
Client management > Power Management
  * Double click on the last entry: Whether to hibernate ...
  * Enable it, set the value to "hibernate"
  * On a client with adsys, while connected on an AD account, run sudo adsysctl 
update -m -vv
  * Observe the logs that indicate the parsing of the dconf key:

  DEBUG Analyzing entry 
{Key:org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type 
Value:hibernate Disabled:false Meta:s Strategy: Err:<nil>} 
  * Observe the output of the following command (it should print 'hibernate'): 
gsettings get org.gnome.settings-daemon.plugins.power 
sleep-inactive-battery-type

  
  [Where problems could occur]

  This code is located in the dconf policy application manager and
  restricted to it. The negative impact in case of a new bug will be
  seen by gsettings key not being applied.

  [Other Info]

  This issue was initially reported on GitHub at
  https://github.com/ubuntu/adsys/issues/135

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982349/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to