I'm sorry for not commenting about the executed test plan. Let's fix
this!
The test plan was executed and I confirm that it was successful. The package
version used for the tests is the one proposed, as can be seen by the output of
apt-cache policy:
adsys:
Installed: 0.14.2~22.04
Candidate: 0.14.2~22.04
Version table:
*** 0.14.2~22.04 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
The following steps were executed:
1) Create a fresh VM with Ubuntu 22.04;
2) Join an active directory domain (created for test purposes);
3) Ensure no DCONF policy is configured on the AD controller;
4) Install adsys;
5) Authenticate with an AD user;
6) Change any DCONF related setting, such as desktop background picture;
After step 6, the setting is applied correctly and the error "unable to
open named profile (user@domain): using the null configuration" is not
shown in the journal.
--
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/2078245
Title:
DCONF policy manager removes userdb on empty policy
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Jammy:
Fix Committed
Status in adsys source package in Noble:
Fix Committed
Bug description:
Upstream issue https://github.com/ubuntu/adsys/issues/1002
tracking bug https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245
[ Impact ]
This is a regression introduced by the implementation of the purge command in
0.14.1.
When the user doesn't have at least one dconf setting set in a policy, the
following error is thrown:
unable to open named profile (user@domain): using the null
configuration
[ Test Plan ]
1. Create a policy with no dconf rule and make sure it applies to the user or
the machiune under test
2. Login on the machine
Without the patched version the following error is displayed:
"unable to open named profile (user@domain): using the null configuration"
With the patched version no error happens
[ Where problems could occur ]
The code that purges the dconf DB has been removed. Worst case, a dconf
setting still applies while all the dconf rules have been removed from the
policy. But then next time the policies applies you'll just end up with an
empty dconf db and no dconf settings enforced.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245/+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
