Public bug reported:
[Impact]
Changing any gsettings key in AD resulted in user databases under /etc/dconf,
owned by root, with 0600 as permissions. This change was done late in the cycle
after passing some permissions checkers to harden the binaries.
However, in that case, the user databases needs to be readable by the users so
that they can apply those values, so we need to align with ibus profile and
makes them 644.
[Test case]
* Change a gsettings key under AD, like picture-uri one.
* Login on the Ubuntu laptop connected with AD by adsys
* The background should now be changed to the set value.
[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 as it is already nowdays.
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
** Affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973748
Title:
Updating any gsettings key makes user dconf database unreadable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973748/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
