Manage energy profile settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
adsys (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Adsys cannot currently manage GSettings power management keys, such as:
/org/gnome/
/org/gnome/
/org/gnome/
/org/gnome/
/org/gnome/
/org/gnome/
/org/gnome/
/org/gnome/
/org/gnome/
/org/gnome/
/org/gnome/
/org/gnome/
[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/
* Observe the output of the following command (it should print 'hibernate'): gsettings get org.gnome.
[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:/
description: | updated |
This bug was fixed in the package adsys - 0.9.2
---------------
adsys (0.9.2) kinetic; urgency=medium
* Update generators to fix FTBFS com/golangci/ golangci- lint golang. org/protobuf
- shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's
filesystem hijacking and cause unexpected behavior
* Update dependencies to latest:
- github.
- google.
-- Gabriel Nagy <email address hidden> Wed, 03 Aug 2022 11:00:39 +0300