Hello Jean-Baptiste, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.2~22.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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. -- 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
