** Description changed:
- upstream issue https://github.com/ubuntu/adsys/pull/1070
+ Upstream issue https://github.com/ubuntu/adsys/issues/1002
+
[ Impact ]
- * An explanation of the effects of the bug on users and justification
- for backporting the fix to the stable release.
+ 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:
- * In addition, it is helpful, but not required, to include an
- explanation of how the upload fixes this bug.
+ unable to open named profile (user@domain): using the null configuration
+
[ Test Plan ]
- * detailed instructions how to reproduce the bug
+ 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
- * these should allow someone who is not familiar with the affected
- package to reproduce the bug and verify that the updated package
- fixes the problem.
+ Without the patched version the following error is displayed:
+ "unable to open named profile (user@domain): using the null configuration"
- * if other testing is appropriate to perform before landing this
- update, this should also be described here.
+ With the patched version no error happens
+
[ Where problems could occur ]
-
- * Think about what the upload changes in the software. Imagine the
- change is wrong or breaks something else: how would this show up?
-
- * It is assumed that any SRU candidate patch is well-tested before
- upload and has a low overall risk of regression, but it's important
- to make the effort to think about what ''could'' happen in the event
- of a regression.
-
- * This must never be "None" or "Low", or entirely an argument as to why
- your upload is low risk.
-
- * This both shows the SRU team that the risks have been considered,
- and provides guidance to testers in regression-testing the SRU.
-
- [ Other Info ]
-
- * Anything else you think is useful to include
-
- * Anticipate questions from users, SRU, +1 maintenance, security teams
- and the Technical Board and address these questions in advance
+ 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.
** Also affects: adsys (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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:
New
Status in adsys source package in Noble:
New
Bug description:
Upstream issue https://github.com/ubuntu/adsys/issues/1002
[ 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
