Hello Denison, or anyone else affected, Accepted adsys into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.3~24.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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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. ** Changed in: adsys (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-noble ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed-jammy -- 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/2081966 Title: [SRU] Timeout for listing GPOs is not enough in some cases 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: [Impact] Adsys has a fixed timeout for listing the GPOs. This can cause issues on slower machines or in cases with many policies to be listed. Adding a configurable timeout prevents the daemon from timing out the listing process during its execution. [Test Plan] 1. Configure A LOT (this can vary depending on the VM setup) of GPOs in the AD controller; 2. Install adsys on the client, without changing the default settings; 3. Run `adsysctl policy update --all`; 4. With the default timeout, the command should timeout due to not being able to fetch all policies in time; 5. Update adsys configuration file (/etc/adsys.yaml) and increase the gpo_list_timeout; 6. Repeat step 3; 7. With an increased timeout, the command should fetch all policies with no issues; [Where Problems Could Occur] If misconfigured by the user, the timeout could be insufficient and AD users would not be allowed to authenticate. Upstream PR: https://github.com/ubuntu/adsys/pull/1097 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2081966/+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
