[Bug 2059756] Re: [SRU] adsys 0.14.1
Yes, the package is ready to upload to Mantic, and it is strictly the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
We plan to SRU the stack to Mantic and align all the supported releases on the same version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Also affects: adsys (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: golang-1.22 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: adsys (Ubuntu Mantic) Status: New => Confirmed ** Changed in: golang-1.22 (Ubuntu Mantic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049061] Re: adsysctl update with a domain user fails if KRB5CCNAME is not set
Hi Timo, We plan to do a release of ADSys from 24.04 to 22.04 which contains much more than this bug and we'll cover the testing of the entirety of the package. Master SRU bug https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756 We'll send the exception request in the coming days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049061 Title: adsysctl update with a domain user fails if KRB5CCNAME is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) * Note: Both are currently in the new queue of 22.04 : https://launchpad.net/ubuntu/jammy/+queue?queue_state=0_text= [test plan] # Process Adsys follows a robust continuous integration and testing process. It is covered by a comprehensive automated tests suite (https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated end to end test suite that runs in a real active directory environment (https://github.com/ubuntu/adsys/actions/workflows/e2e-tests.yaml). The team applied the following quality
[Bug 2062557] Re: [FFe] add trace-cmd to standand seed
** Also affects: ubuntu-meta (Ubuntu) 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/2062557 Title: [FFe] add trace-cmd to standand seed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/2062557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062564] Re: [FFe] Seed pemmican
** Also affects: ubuntu-meta (Ubuntu) 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/2062564 Title: [FFe] Seed pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: + * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) - * Note: Both are currently in the new queue of 22.04 : https://launchpad.net/ubuntu/jammy/+queue?queue_state=0_text= + * Note: Both are currently in the new queue of 22.04 : https://launchpad.net/ubuntu/jammy/+queue?queue_state=0_text= + [test plan] # Process Adsys follows a robust continuous integration and testing process. It is covered by a comprehensive automated tests suite (https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated end to end test suite that runs in a real active directory
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Changed in: adsys (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] [NEW] [SRU] adsys 0.14.1
Public bug reported: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version ** Affects: adsys (Ubuntu) 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/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. + Version 0.14.1 is available for 22.04 in a PPA and already used in + production by customers. + [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues - Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ + Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] - Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog - * New features -* New policies: - - Add mount / network shares policy manager - - Add AppArmor policy manager - - Support multiple AD backends and implement Winbind support - - Add system proxy policy manager - - Add certificate policy manager for machines - - Add adsysctl policy purge command to purge applied policies - - Full documentation - - Full end to end automated test suite. + Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog + * New features + * New policies: + - Add mount / network shares policy manager + - Add AppArmor policy manager + - Support multiple AD backends and implement Winbind support + - Add system proxy policy manager + - Add certificate policy manager for machines + - Add adsysctl policy purge command to purge applied policies + - Full documentation + - Full end to end automated test suite. - * Enhancements - * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine - * Expose Ubuntu Pro status in the "status" command - * Update scripts manager creation - * List Pro policy types in service status output - * Warn when Pro-only rules are configured - * Use systemd via D-Bus instead of systemctl commands - * Add placeholder notes for entry types - * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos - * Rework policy application sync strategy - * Print logs when policies are up to date - * Update policy definitions to include dconf key for dark mode background - * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) - * Allow sssd backend to work without ad_domain being set (LP: #2054445) - * Update apport hook to include journal errors and package logs + * Enhancements + * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine + * Expose Ubuntu Pro status in the "status" command + * Update scripts manager creation + * List Pro policy types in service status output + * Warn when Pro-only rules are configured + * Use systemd via D-Bus instead of systemctl commands + * Add placeholder notes for entry types + * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos + * Rework policy application sync strategy + * Print logs when policies are up to date + * Update policy definitions to include dconf key for dark mode background + * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) + * Allow sssd backend to work without ad_domain being set (LP: #2054445) + * Update apport hook to include journal errors and package logs - * Bug fixes - * Fix policy update failing when GPT.INI contains no version key - * Fix object lookup for users having a FQDN as their hostname - * Support special characters in domains when parsing sssd configuration - * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf - * Ensure empty state for dconf policy - * Handle case mismatches in GPT.INI file name - * Ensure GPO URLs contain the FQDN of the domain
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) [test plan] # Process - Adsys follows a robust continuous integration and testing process. It is covered by a comprehensive automated tests suite (https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated end to end test suite that runs in a real active directory environment. + Adsys follows a robust continuous integration and testing process. It is covered by a comprehensive automated tests suite (https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated end to end test suite that runs in a real active
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) + * Note: Both are currently in the new queue of 22.04 : https://launchpad.net/ubuntu/jammy/+queue?queue_state=0_text= [test plan] # Process Adsys follows a robust continuous integration and testing process. It is covered by a comprehensive automated tests suite (https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated end to end test suite that runs in a real active directory environment (https://github.com/ubuntu/adsys/actions/workflows/e2e-tests.yaml). The team applied the following quality criteria: * All changes
[Bug 2043376] Re: adsys cant fetch gpos ubuntu 22.04.3
** Changed in: adsys (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043376 Title: adsys cant fetch gpos ubuntu 22.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2043376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055300] Re: DEP8 failures in noble/armhf with samba 4.19.5
There is a passing run with samba/2:4.19.5+dfsg-1ubuntu1 This could be a flaky test on armhf. I'm closing this report for now and will look further if it becomes a blocker on this arch in the futur. ** Changed in: adsys (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055300 Title: DEP8 failures in noble/armhf with samba 4.19.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2055300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055300] Re: DEP8 failures in noble/armhf with samba 4.19.5
** Changed in: adsys (Ubuntu) Assignee: (unassigned) => Gabriel Nagy (gabuscus) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055300 Title: DEP8 failures in noble/armhf with samba 4.19.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2055300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929038] Re: [SRU] Backport to 20.04 LTS
It's a desktop package that we do not need on riscv64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958668] Re: Do not propose to reboot on WSL
** Changed in: update-manager (Ubuntu) Status: New => Triaged ** Changed in: update-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958668 Title: Do not propose to reboot on WSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1958668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929038] Re: [SRU] Backport to 20.04 LTS
This has been verified a while ago and already deployed in production for customers. Marking as verification-done. ** Tags removed: removal-candidate verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968150] [NEW] [FFe] Remove zsys from installer
Public bug reported: Zsys is in very low maintenance mode (critical bug fixes only) and must be removed from the LTS. However ZFS and encrypted ZFS are still available as an installation option but the package ZSys is not installed. The ZFS layout remains unchanged. https://git.launchpad.net/ubiquity/commit/?id=76e7718dbdd9dde7a7609f754cf8719469bbf0e5 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Description changed: Zsys is in very low maintenance mode (critical bug fixes only) and must be removed from the LTS. However ZFS and encrypted ZFS are still available as an installation option but the package ZSys is not installed. The ZFS layout remains unchanged. + + https://git.launchpad.net/ubiquity/commit/?id=76e7718dbdd9dde7a7609f754cf8719469bbf0e5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968150 Title: [FFe] Remove zsys from installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1968150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)
** Changed in: zsys (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967585 Title: Failed to start ZSYS daemon service (panic: runtime error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1967585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)
A pool compatibility property has been added to ZFS 2.1 but not to the go binding. ** Changed in: zsys (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967585 Title: Failed to start ZSYS daemon service (panic: runtime error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1967585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session in virt-manager with QXL
** Summary changed: - Jammy fails to boot to live session + Jammy fails to boot to live session in virt-manager with QXL ** Description changed: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. There are crashes of gnome-shell and xorg in /var/crash. - From the journal + From the journal avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 ip 7fa1ca256f44 sp 7fff16f7c2a0 error 4 in libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000] avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00 avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission + + + If I switch from QXL to Virtio then it works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session in virt-manager with QXL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "_usr_lib_xorg_Xorg.0.crash" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577348/+files/_usr_lib_xorg_Xorg.0.crash ** Description changed: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. There are crashes of gnome-shell and xorg in /var/crash. + + I'm on Jammy with libvirt 8.0.0-1ubuntu6 and qemu 6.2+dfsg-2ubuntu5 ** Description changed: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. There are crashes of gnome-shell and xorg in /var/crash. - I'm on Jammy with libvirt 8.0.0-1ubuntu6 and qemu 6.2+dfsg-2ubuntu5 + From the journal + avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 ip 7fa1ca256f44 sp 7fff16f7c2a0 error 4 in libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000] + avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00 + avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "_usr_bin_gnome-shell.999.crash" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577347/+files/_usr_bin_gnome-shell.999.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577346/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "debug" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577344/+files/debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "dm" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577345/+files/dm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] [NEW] Jammy fails to boot to live session
Public bug reported: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. There are crashes of gnome-shell and xorg in /var/crash. From the journal avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 ip 7fa1ca256f44 sp 7fff16f7c2a0 error 4 in libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000] avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00 avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966818] Re: zsys crashing on snap mounts
*** This bug is a duplicate of bug 1967585 *** https://bugs.launchpad.net/bugs/1967585 ** This bug has been marked a duplicate of bug 1967585 Failed to start ZSYS daemon service (panic: runtime error) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966818 Title: zsys crashing on snap mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1966818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)
Thanks for your report. Confirmed with 0.5.8build2. Downgrading and pinning to 0.5.8 is the workaround for now. https://launchpad.net/ubuntu/+source/zsys/0.5.8/+build/21362897/+files/zsys_0.5.8_amd64.deb ** Changed in: zsys (Ubuntu) Status: New => Confirmed ** Changed in: zsys (Ubuntu) Importance: Undecided => Critical ** Changed in: zsys (Ubuntu) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) ** Changed in: zsys (Ubuntu) Milestone: None => ubuntu-22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967585 Title: Failed to start ZSYS daemon service (panic: runtime error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1967585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929201] Re: Packages in PPA are not installed if version higher than in a release pocket
I confirm that adding XB-Task addresses the issue and the package from the PPA is installed. However, when there is no task defined, the package from archive should be installed. ** Changed in: livecd-rootfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929201 Title: Packages in PPA are not installed if version higher than in a release pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1929201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964325] [NEW] Fails to print due to apparmor denied connect operation for cupsd - /run/systemd/userdb/io.systemd.Machine
Public bug reported: On an up to date Jammy machine, printing fails and there is the following apparmor denied message in the journal: apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd" name="/run/systemd/userdb/io.systemd.Machine" pid=892182 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 Printing works after running aa-complain cupsd. The printer is a driverless HP Envy 5020 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apparmor 3.0.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 10:25:10 2022 InstallationDate: Installed on 2020-05-31 (647 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) ProcKernelCmdline: BOOT_IMAGE=/BOOT/ubuntu_nt06gx@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_nt06gx ro snd-intel-dspcfg.dsp_driver=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy rls-jj-incoming ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964325 Title: Fails to print due to apparmor denied connect operation for cupsd - /run/systemd/userdb/io.systemd.Machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1964325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936907] Re: [MIR] ADSys
** Description changed: [Availability] Available on all archs, available starting hirsute. It will be backported to Focal once an FFe has been accepted. [Rationale] We are supporting GPO Active Directory support on ubuntu starting hirsute. This features allows for an administrator to configure their Active Directory server to deploy per-machine and per-user configurations, enforce rules and other domain policies. - Right now, dconf keys are supported. + Right now, dconf keys, sudo administration rights and computer and user + scripts are supported. This feature is built and use the krb5 tickets which are provided by SSSD. Basically: - SSSD is dealing with user and machine registration/authentification and enforce password policies - ADSys is handling GPO enforcement and support. The Ubuntu specific policies needs to be installed on the Active Directory server (they are contained in the daemon). [Security] The daemon is started is running as a root user to be able to enforce machine policies, like rebuilding dconf databases, setting profiles. User only interacts with the client side (both sides communicates over GRPC), which can be ran as any user. Polkit is used to restrain access to some part of the API. There is a PAM module to build on demand per-user policy once authenticated with SSSD. They are rejected if the authentication or not all affected policies could be downloaded. [Quality assurance] Joining a domain in the ubiquity desktop installer makes the machine joining the AD domain and install adsys functionality. The package will be seeded directly on the desktop ISO. - An extensive testsuite (more than 700) is included and available as + An extensive testsuite (more than 1k) is included and available as autopkgtests for rdepends. The whole stack is tested (even the client/daemon interaction) and coverage is measured (including in the small python script). However, tests with a real Active Directory server can only be done manually as there is no setup available in the autopkgtests infrastructure. [Dependencies] Main dependencies are libsmbclient, python3 (an embeeded script allows, via samba, connecting to AD LDAP) and SSSD/KRB5. This is a Go package, and all dependencies are vendored, and versions are controlled via go.mod. We are using dependabot (from Github) to automatically get notified of any dependencies updates (and security issues), which opens a PR, rebuild and run all tests to report it there. We are thus able to quickly merge them. [Standards compliance] Standard debhelper packaging, including a systemd service. [Maintenance] The desktop team will maintain it. * we commit to test no-change-rebuilds triggered by a dependent library/compiler and to fix any issues found for the lifetime of the release (including ESM when included) * we will provide timely testing of no-change-rebuilds from the security team, fixing the rebuilt package as necessary * we commit to provide updates to the security team for any affected vendored code for the lifetime of the release (including ESM when included) * we will provide timely, high quality updates for the security team to sponsor to fix issues in the affected vendored code - [Background information] ADSys is composed of: - a daemon, named adsysd, running as root. This one will shutdown after a period of inactivity without any active request. It is socket activated. - a client, named adsysctl (which is a symlink to adsysd and only differ behavior from its executable name), which is running as the user (or root on boot for machine update). This ones optionally wakes up adsysd, connect through an Unix socket with SO_PEERCRED to communicate current user running the process. We are using grpc to communicate between the client and service. Each client request is validated through polkit, matching user name and permissions. The daemon will reject any unauthorized client connections. Note that all actions are always performed from executing the client, even the scheduled one by a cron. - The daemon contains a python embeeded script to reuse samba utilities to - connect with GSSAPI to the AD LDAP server and list available GPOs. GPOs - are then downloaded in a cache directory which isn’t accessible to + The daemon contains a python embedded script that uses samba utilities + to connect with GSSAPI to the AD LDAP server and list available GPOs. + GPOs are then downloaded in a cache directory which isn’t accessible to users. The daemon also contains all GPOs policies to install on the Active Directory side to reflect them in the UI. This could be accessed online or dumped directly via the command line tool. Finally, those are automatically refreshed for any supported LTSes and intermediate versions. The availability of features can be different
[Bug 1959667] [NEW] non informative error message when enabling a non available UA service
Public bug reported: Jammy / software-properties-gtk: Installed: 0.99.17 When trying to enable a service that is not available the error message provide no useful information about what went wrong (cf screenshot) and in the journal: ubuntu-advantag[1461382]: Failed to parse UA status: Operation was cancelled In both cases the error message should be similar to UA CLI: UA Infra: ESM is not available for Ubuntu 22.04 (Jammy Jellyfish). ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2022-02-01_12-06.png" https://bugs.launchpad.net/bugs/1959667/+attachment/5558588/+files/2022-02-01_12-06.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959667 Title: non informative error message when enabling a non available UA service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958668] [NEW] Do not propose to reboot on WSL
Public bug reported: On WSL, at the end of a do-release-upgrade, the upgrader proposes to reboot the machine. Although on WSL it is not possible to reboot due to the lack of systemd and it ends with an error. The message at the end should be different if it is running on a system where systemd is not available or specifically on WSL and do not propose a reboot but to manually shutdown and restart the instance. ** Affects: update-manager (Ubuntu) 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/1958668 Title: Do not propose to reboot on WSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1958668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952999] Re: Wayland blocks the microphone of the webcam
Yes, it works perfectly with Xorg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952999 Title: Wayland blocks the microphone of the webcam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1952999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952999] [NEW] Wayland blocks the microphone of the webcam
Public bug reported: Jammy daily In the wayland session the microphone of the webcam is no available. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.19.0-2build1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 2 07:45:44 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2081] InstallationDate: Installed on 2020-05-31 (549 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_nt06gx@/vmlinuz-5.13.0-20-generic root=ZFS=rpool/ROOT/ubuntu_nt06gx ro snd-intel-dspcfg.dsp_driver=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:br5.16:efr3.4:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:skuBXNUC10i7FNH:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy reproducible rls-jj-incoming single-occurrence ubuntu wayland-session ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952999 Title: Wayland blocks the microphone of the webcam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1952999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952457] Re: choosing Ubuntu on xorg fails to launch X, launches Wayland
There is no crash and this is on hardware. ** Tags added: rls-jj-incoming ** Attachment added: "journal.txt.gz" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1952457/+attachment/5544826/+files/journal.txt.gz ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952457 Title: choosing Ubuntu on xorg fails to launch X, launches Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1952457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952930] Re: Xorg session doesn't stick
** Attachment added: "journal.txt.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1952930/+attachment/5544680/+files/journal.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952930 Title: Xorg session doesn't stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1952930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952930] [NEW] Xorg session doesn't stick
Public bug reported: Jammy daily. *Test Case* 1. Boot to GDM 2. Select an Xorg Session 3. Login 4. Verify that Xorg is running 5. Reboot the machine 6. Check that Xorg session is still selected 7. Login 8. Verify that Xorg is running *Actual result* Wayland is running despite Xorg was preselected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-session 40.1.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 16:28:37 2021 InstallationDate: Installed on 2020-05-31 (549 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy rls-jj-incoming wayland-session ** Tags added: rls-jj-incomping ** Tags removed: rls-jj-incomping ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952930 Title: Xorg session doesn't stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1952930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
Verification
Mesa 21.0.3-0ubuntu0.3~20.04.4 has been tested on 2 systems and it fixes
the issue. Marking as verification-done.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174
Title:
[SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Changed in: mesa (Ubuntu Focal)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174
Title:
[SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium applications
(Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
is being freed and reallocated with exactly the same heap pointers
during a resize, which is causing Mesa to think the new drawable is
already fully initialized when binded to the context, but it is not true
and only because the new drawable is matching the old stale pointer for
the previously freed drawable… and as a result the context remain
invalid and the app is unable to present.
With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
users hitting this issue is increasing.
[Test Case]
On Windows 11 with WSLg and Ubuntu 20.04
1. Verify that hardware acceleration is enable either with glxinfo -B or in
edge with edge://gpu
2. Install and launch chrome, edge or vscode
3. Resize the windows repeatedly
Verification:
The app must not crash or hang.
+
+ [What could go wrong]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174
Title:
[SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium applications
(Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
is being freed and reallocated with exactly the same heap pointers
during a resize, which is causing Mesa to think the new drawable is
already fully initialized when binded to the context, but it is not true
and only because the new drawable is matching the old stale pointer for
the previously freed drawable… and as a result the context remain
invalid and the app is unable to present.
With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
users hitting this issue is increasing.
[Test Case]
+ On Windows 11 with WSLg and Ubuntu 20.04
+
1. Verify that hardware acceleration is enable either with glxinfo -B or in
edge with edge://gpu
2. Install and launch chrome, edge or vscode
3. Resize the windows repeatedly
Verification:
The app must not crash or hang.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174
Title:
[SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium applications
(Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
is being freed and reallocated with exactly the same heap pointers
during a resize, which is causing Mesa to think the new drawable is
already fully initialized when binded to the context, but it is not true
and only because the new drawable is matching the old stale pointer for
the previously freed drawable… and as a result the context remain
invalid and the app is unable to present.
With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
users hitting this issue is increasing.
[Test Case]
+ 1. Verify that hardware acceleration is enable either with glxinfo -B or in
edge with edge://gpu
+ 2. Install and launch chrome, edge or vscode
+ 3. Resize the windows repeatedly
+
+ Verification:
+ The app must not crash or hang.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174
Title:
[SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium applications
(Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
is being freed and reallocated with exactly the same heap pointers
during a resize, which is causing Mesa to think the new drawable is
already fully initialized when binded to the context, but it is not true
and only because the new drawable is matching the old stale pointer for
the previously freed drawable… and as a result the context remain
invalid and the app is unable to present.
With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
users hitting this issue is increasing.
+
+ [Test Case]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174
Title:
[SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] [NEW] [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
Public bug reported:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which is
affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium applications
(Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
is being freed and reallocated with exactly the same heap pointers
during a resize, which is causing Mesa to think the new drawable is
already fully initialized when binded to the context, but it is not true
and only because the new drawable is matching the old stale pointer for
the previously freed drawable… and as a result the context remain
invalid and the app is unable to present.
With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
users hitting this issue is increasing.
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: mesa (Ubuntu Focal)
Importance: High
Status: Triaged
** Also affects: mesa (Ubuntu Focal)
Importance: Undecided
Status: New
** Description changed:
[Description]
- This is a request to backport this fix to focal-updates which is affecting
users of WSL:
+ This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium applications
(Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
is being freed and reallocated with exactly the same heap pointers
during a resize, which is causing Mesa to think the new drawable is
already fully initialized when binded to the context, but it is not true
and only because the new drawable is matching the old stale pointer for
the previously freed drawable… and as a result the context remain
invalid and the app is unable to present.
With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
users hitting this issue is increasing.
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
** Changed in: mesa (Ubuntu Focal)
Status: New => Triaged
** Changed in: mesa (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174
Title:
[SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926267] Re: do-release-upgrade failed silently after failed to connect to snap service
** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute) Status: Confirmed => Won't Fix ** Changed in: ubuntu-release-upgrader (Ubuntu Impish) Status: Confirmed => Triaged ** Changed in: ubuntu-release-upgrader (Ubuntu Impish) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926267 Title: do-release-upgrade failed silently after failed to connect to snap service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
I've this issue too. What else do you need than @Mario's journal? ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Also affects: gdm3 (Ubuntu Impish) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
There is also an additional requirement. The package must install successfully and replace an existing file that would have been created manually (we had to ship the file on the image for the customer since we don't have this fix in a package yet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
IMHO having the fix in network-dispatcher makes more sense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
@Seb this fix has to go to focal for a customer project and must land in the dev release first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
The server is set via a configuration file. The default config file is /etc/systemd/timesyncd.conf and it can be overridden by dropping files in /etc/systemd/timesyncd.conf.d/. There is a pool of free ntp servers available on https://www.ntppool.org/en/. To test this fix you also need a DHCP server that returns NTP records. With VMs, you can use dnsmasq to provide NTP records by changing the values in dnsmasq.conf # Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5 #dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5 Or if you're using libvirt, edit the configuration with "virsh net-edit default" (or the name of the network your VMs are attached to) then pass the option directly to dnsmasq (cf https://libvirt.org/formatnetwork.html for reference) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940925] [NEW] Do not activate spread view on first boot
Public bug reported: On first boot the spread view shows the first boot wizard and it looks really weird. Moreover if you click on the right workspace the wizard is not displayed. The spread view should be disabled and the wizard should be displayed full screen immediately. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 24 12:41:16 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-31 (450 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "Screenshot from 2021-08-24 12-39-28.png" https://bugs.launchpad.net/bugs/1940925/+attachment/5520159/+files/Screenshot%20from%202021-08-24%2012-39-28.png ** Description changed: On first boot the spread view shows the first boot wizard and it looks - really weird. The spread view should be disable and the wizard should be - displayed full screen immediately. + really weird. Moreover if you click on the right workspace the wizard is + not displayed. + + The spread view should be disabled and the wizard should be displayed + full screen immediately. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 24 12:41:16 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-31 (450 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940925 Title: Do not activate spread view on first boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
** Also affects: network-manager (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Focal) Importance: Undecided => High ** Changed in: network-manager (Ubuntu Focal) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940826] Re: customisation steps do not work for 20.04
** Package changed: ubiquity (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940826 Title: customisation steps do not work for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1940826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940822] [NEW] This is a test
Public bug reported: This is a test ** Affects: ubuntu Importance: Undecided Status: Invalid ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940822 Title: This is a test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1940822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940657] Re: Cannot type in address bar nor page content in live session
Thanks for your report. Could you please describe your testing environment (VM vs HW, HW configuration, ...) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940657 Title: Cannot type in address bar nor page content in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921091] Re: [SRU] New feature: Encryption recovery key
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921091 Title: [SRU] New feature: Encryption recovery key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921091] Re: [SRU] New feature: Encryption recovery key
I verified ubiquity 20.04.15.17 in both automated and manual partitioning and it works as expected. Marking as verification done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921091 Title: [SRU] New feature: Encryption recovery key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928860] Re: Recovery key is low-entropy
ubiquity (21.10.4) impish; urgency=medium [ Didier Roche ] [ Jean-Baptiste Lallement ] * Make the recovery key a 48 digits password by default (LP: 1928860) * Recovery key is editable and optional. * Show the recovery key during manual partitioning. * Display a warning if recovery key is stored on a non removable media. ** Changed in: ubiquity (Ubuntu Impish) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928860 Title: Recovery key is low-entropy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1928860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921091] Re: [SRU] New feature: Encryption recovery key
This patch is missing in scripts/plugininstall.py from focal and the
install crashes in manual mode partitioning mode:
disk = debconf_disk.split('/')[-1].replace('=', '/')
if not disk: # disk is not set in manual partitioning mode
syslog.syslog(
syslog.LOG_ERR,
'Determining installation disk failed. '
'Setting a recovery key is supported only with partman-auto.')
self.clean_crypto_keys()
self.db.input('critical', 'ubiquity/install/broken_luks_add_key')
self.db.go()
return
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-failed verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921091
Title:
[SRU] New feature: Encryption recovery key
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921091/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921091] Re: [SRU] New feature: Encryption recovery key
pushed to focal branch https://git.launchpad.net/ubiquity/commit/?h=focal=b88f5121758599b5f412c56aabe67b22e5e2f586 ** Changed in: ubiquity (Ubuntu Focal) Status: New => In Progress ** Changed in: ubiquity (Ubuntu Focal) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) ** Changed in: ubiquity (Ubuntu Focal) Milestone: None => ubuntu-20.04.3 ** Changed in: ubiquity (Ubuntu Focal) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921091 Title: [SRU] New feature: Encryption recovery key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936488] [NEW] Ubiquity fails to build with GTK4
Public bug reported:
With latest updates applied on impish Ubiquity fails to build with:
make: Leaving directory '/home/j-lallement/shared/Ubuntu/Dev/ubiquity/src'
/home/j-lallement/shared/Ubuntu/Dev/ubiquity/tests/test_gtkwidgets.py:9:
PyGIWarning: Gtk was imported without specifying a version first. Use
gi.require_version('Gtk', '4.0') before import to ensure that the right version
gets loaded.
from gi.repository import Gtk, TimezoneMap
/home/j-lallement/shared/Ubuntu/Dev/ubiquity/tests/test_usersetup.py:6:
PyGIWarning: UbiquityMockResolver was imported without specifying a version
first. Use gi.require_version('UbiquityMockResolver', '1.0') before import to
ensure that the right version gets loaded.
from gi.repository import UbiquityMockResolver
Traceback (most recent call last):
File "/home/j-lallement/shared/Ubuntu/Dev/ubiquity/./tests/run", line 121, in
suite = unittest.TestLoader().loadTestsFromNames(tests)
File "/usr/lib/python3.9/unittest/loader.py", line 220, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib/python3.9/unittest/loader.py", line 220, in
suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib/python3.9/unittest/loader.py", line 154, in loadTestsFromName
module = __import__(module_name)
File "/home/j-lallement/shared/Ubuntu/Dev/ubiquity/tests/test_usersetup.py",
line 9, in
from ubiquity import gtkwidgets, plugin_manager
File "/home/j-lallement/shared/Ubuntu/Dev/ubiquity/./ubiquity/gtkwidgets.py",
line 38, in
class StylizedFrame(Gtk.Alignment):
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 32, in
__getattr__
return getattr(self._introspection_module, name)
File "/usr/lib/python3/dist-packages/gi/module.py", line 123, in __getattr__
raise AttributeError("%r object has no attribute %r" % (
AttributeError: 'gi.repository.Gtk' object has no attribute 'Alignment'
It should be fixed by setting the version of GTK to 3
** Affects: ubiquity (Ubuntu)
Importance: Critical
Status: New
** Tags: rls-ii-incoming
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu)
Importance: High => Critical
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936488
Title:
Ubiquity fails to build with GTK4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1936488/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935818] Re: Black screen if PAM session fails to initialize completely
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: gdm3 (Ubuntu Focal) Assignee: Jean-Baptiste Lallement (jibel) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935818 Title: Black screen if PAM session fails to initialize completely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1935818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935818] [NEW] Black screen if PAM session fails to initialize completely
Public bug reported: [Description] If PAM session fails to initialize completely, the session aborts as expected but GDM stays on VT1 and switches to a black screen. This is the case for example, when requirement to start a session are not met and the session start up has to be aborted. [Test Plan] 1. In /etc/pam.d/gdm-password insert the line: session requisite pam_deny.so After the line @include common-account 2. Login from GDM 3. Verify that: - The session fails to start - A black TTY is displayed - Active TTY is 1 4. Apply the patched version 5. Login from GDM 6. Verify the login fails but GDM is still displayed and an error message in printed under the password box. [Where problem could occur] * Cannot login at all with any user. [Other info] * Upstream bug report and patch: https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/143 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 3.38.2.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:36:11 2021 InstallationDate: Installed on 2020-05-31 (407 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: High Status: Triaged ** Affects: gdm3 (Ubuntu Focal) Importance: Undecided Assignee: Jean-Baptiste Lallement (jibel) Status: New ** Tags: amd64 apport-bug impish ** Description changed: [Description] If PAM session fails to initialize completely, the session aborts as expected but GDM stays on VT1 and switches to a black screen. [Test Plan] 1. In /etc/pam.d/gdm-password insert the line: - session requisite pam_deny.so - After the line - @include common-account - 2. Login from GDM + session requisite pam_deny.so + After the line + @include common-account + 2. Login from GDM 3. Verify that: - - The session fails to start - - A black TTY is displayed - - Active TTY is 1 + - The session fails to start + - A black TTY is displayed + - Active TTY is 1 4. Apply the patched version - 5. Login from GDM + 5. Login from GDM 6. Verify the login fails but GDM is still displayed and an error message in printed under the password box. [Where problem could occur] * Cannot login at all with any user. [Other info] + * Upstream bug report and patch: + https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/143 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 3.38.2.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:36:11 2021 InstallationDate: Installed on 2020-05-31 (407 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: gdm3 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu) Status: New => Triaged ** Description changed: [Description] - If PAM session fails to initialize completely, the session aborts as expected but GDM stays on VT1 and switches to a black screen. + If PAM session fails to initialize completely, the session aborts as expected but GDM stays on VT1 and switches to a black screen. This is the case for example, when requirement to start a session are not met and the session start up has to be aborted. [Test Plan] 1. In /etc/pam.d/gdm-password insert the line: session requisite pam_deny.so After the line @include common-account 2. Login from GDM 3. Verify that: - The session fails to start - A black TTY is displayed - Active TTY is 1 4. Apply the patched version 5. Login from GDM 6. Verify the login fails but GDM is still displayed and an error message in printed under the password box. [Where problem could occur] * Cannot login at all with any user. [Other info] * Upstream bug report and patch: - https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/143 + https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/143 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 3.38.2.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubun
[Bug 1934997] Re: Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6
Thank you for your report and sorry for the issue caused by this SRU. In focal GPO are enforced by default. But the original version of SSSD was not fully implementing the MS spec and GPO where actually not enforced. This was the case for the default domain policy which defines in particular the security and password policy which where not followed. This is what this SRU addressed by backporting most the GPO fixes from recent version of SSSD and created this unfortunate side effect. This problem will occur when users will upgrade from 20.04 to 22.04 anyway. Adding 'ad_gpo_access_control = permissive' to sssd.conf is one way to fix it. Another way is to make sure the default domain policy is properly defined and that the client can access it. However we will have a look at a Samba4 setup to try to understand if there is a general problem with this setup and how it can be addressed before 22.04 is released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934997 Title: Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1934997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934997] Re: Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6
** Changed in: sssd (Ubuntu) Status: New => Triaged ** Changed in: sssd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934997 Title: Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1934997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931074] Re: SRU: fix tests to also succeed with Python 3.8.10
The package builds. Marking as verification done. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931074 Title: SRU: fix tests to also succeed with Python 3.8.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1931074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DCHP are not propagated to timesyncd
Updates version of the script. ** Attachment added: "10-update-timesyncd" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+attachment/5507668/+files/10-update-timesyncd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DCHP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] [NEW] NTP servers from DCHP are not propagated to timesyncd
Public bug reported: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug impish ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DCHP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933095] Re: [SRU] AD option not available for network-only connection
I verified ubiquity 20.04.15.14 and confirm I can enable AD in the user info page on a local network without public access. It also works with internet access and it is disabled without networking at all. Marking as verification-done ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933095 Title: [SRU] AD option not available for network-only connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1933095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933098] Re: [SRU] krb5-config is not needed for Active Directory support
I verified ubiquity 20.04.15.14 and confirm that the packages are not installed after the installation of the release and the GPOs are still downloaded. Marking as verification-done ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933098 Title: [SRU] krb5-config is not needed for Active Directory support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1933098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933116] Re: [SRU] Fix GPO support in Focal
I verified that sssd 2.2.3-3ubuntu0.6 behaves as expected (default domain policy is downloaded and applied) and didn't find any regression either. Marking as verification-done ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933116 Title: [SRU] Fix GPO support in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1933116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926771] Re: [SRU] Hard dependency on desktop-file-utils not declared
** No longer affects: wslu (Ubuntu Hirsute) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926771 Title: [SRU] Hard dependency on desktop-file-utils not declared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1926771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929536] Re: [SRU] GDM background configurable with gsettings
verification gnome-shell 3.36.9-0ubuntu0.20.04.2 has been tested successfully and can be configured via AD and GPOs. Without AD the behaviour is still the same. marking as verification done ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929536 Title: [SRU] GDM background configurable with gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933098] Re: [SRU] krb5-config is not needed for Active Directory support
** Changed in: ubiquity (Ubuntu) Importance: Undecided => High ** Changed in: ubiquity (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: ubiquity (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933098 Title: [SRU] krb5-config is not needed for Active Directory support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1933098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933116] [NEW] [SRU] Fix GPO support in Focal
Public bug reported: [Description] GPO support in focal doesn't focal MS ADTS spec and is not functional. It means that the default domain policy containing the security policy for example is not applied. This SRU backports GPO patches from current stable version of SSSD. [Test Case] 1. Install a machine with SSSD and join and AD domain where the controller is a Windows machine. 2. Add the machine to an OU of the domain 3. Boot the machine and login ad a user of the domain. 4. Verify the content of /var/lib/sss/gpo_cache/ When it fails, this directory is empty On success it is filled with the GPO downloaded from the domain controller. It is also possible to check the journal for errors, there should be non related to GPO. [Where problems could occur] This code is limited to GPO on AD which is not working in focal. Worst case, it is still not functional. ** Affects: sssd (Ubuntu) Importance: High Status: Fix Released ** Affects: sssd (Ubuntu Focal) Importance: High Status: Triaged ** Also affects: sssd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: sssd (Ubuntu) Status: New => Fix Released ** Changed in: sssd (Ubuntu) Importance: Undecided => High ** Changed in: sssd (Ubuntu Focal) Importance: Undecided => High ** Changed in: sssd (Ubuntu Focal) Status: New => Triaged ** Summary changed: - [SRU] Fix GPO support on Focal + [SRU] Fix GPO support in Focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933116 Title: [SRU] Fix GPO support in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1933116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921374] Re: [SRU] New feature: Active Directory support
Verification of Ubiquity In ubiquity I enabled Active Directory and filled the corresponding fields. After installation: - The machine joined the domain - On first boot, I can login as a user of the domain and its home directory is created. Marking as verification done. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921374 Title: [SRU] New feature: Active Directory support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921374] Re: [SRU] New feature: Active Directory support
Verification of livecd-rootfs I checked the daily build of focal https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/focal/ubuntu/+build/279154 the packages realmd and adcli in universe in focal and main in focal- updates are correctly seeded in the image. Marking as verification done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921374 Title: [SRU] New feature: Active Directory support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929038] Re: [SRU] Backport to 20.04 LTS
I've installed golang-1.16 from proposed and successfully performed a build of adsys and of a simple sample source code. The "go version" command returned 1.16.2 on both. Marking as verification done. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: adsys (Ubuntu Focal) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929038] Re: [SRU] Backport to 20.04 LTS
** Changed in: adsys (Ubuntu Focal) Importance: Undecided => High ** Changed in: adsys (Ubuntu Focal) Status: New => Triaged ** Changed in: adsys (Ubuntu) Status: New => Fix Released ** Changed in: adsys (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913261] Re: [needs-packaging] New package: ubuntu-wsl-integration
it's now in Impish. ubuntu-wsl-integration | 0.31.2 | impish/universe | source, amd64, arm64 Closing ** Changed in: ubuntu Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913261 Title: [needs-packaging] New package: ubuntu-wsl-integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1913261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913262] Re: [needs-packaging] new package: ubuntu-wsl-oobe
Thanks everyone 0.1.17 is in the archive ubuntu-wsl-oobe | 0.1.17 | impish/universe | source, amd64, arm64 ** Changed in: ubuntu Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913262 Title: [needs-packaging] new package: ubuntu-wsl-oobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1913262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928860] Re: Recovery key is low-entropy
This is being worked on. In summary the following changes will be done in 21.10: - The length of the generated numerical key will be increased to 48 digits (like bitlocker) - It will be optional - It will be editable and accept letters, digits and special characters. ** Changed in: ubiquity (Ubuntu Impish) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928860 Title: Recovery key is low-entropy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1928860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928860] Re: Recovery key is low-entropy
** Changed in: ubiquity (Ubuntu Impish) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928860 Title: Recovery key is low-entropy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1928860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921374] Re: [SRU] New feature: Active Directory support
Yes, adding the packages in a hook of livecd-rootfs does the job. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921374 Title: [SRU] New feature: Active Directory support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929536] Re: [SRU] GDM background configurable with gsettings
** Description changed: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. - [Rationale] - Corporate customers use LTS releases and ultimately this will be released for 20.04. - This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. + [Test Case] + 1. Boot a desktop session + 2. Verify that the default aubergine background is displayed in the greeter. + 3. Login as the administrator of the machine + 4. Install systemd-container + 5. Switch to the GDM user: + $ sudo machinectl shell gdm@ /bin/bash + 6. Apply a different background with the command: + $ gsettings set com.ubuntu.login-screen background-picture-uri 'file:///usr/share/backgrounds/warty-final-ubuntu.png' + 7. Logout + 8. Verify that the image 'warty-final-ubuntu.png' is displayed as the background of the greeter. + [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 ** Description changed: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Test Case] - 1. Boot a desktop session + 1. Boot a desktop session 2. Verify that the default aubergine background is displayed in the greeter. 3. Login as the administrator of the machine 4. Install systemd-container 5. Switch to the GDM user: - $ sudo machinectl shell gdm@ /bin/bash + $ sudo machinectl shell gdm@ /bin/bash 6. Apply a different background with the command: - $ gsettings set com.ubuntu.login-screen background-picture-uri 'file:///usr/share/backgrounds/warty-final-ubuntu.png' + $ gsettings set com.ubuntu.login-screen background-picture-uri 'file:///usr/share/backgrounds/warty-final-ubuntu.png' 7. Logout 8. Verify that the image 'warty-final-ubuntu.png' is displayed as the background of the greeter. - - [Risks] - The changeset is minimal, isolated and can be easily reverted. + [Risks / Impact] + The changeset is minimal, isolated (Only the code of the greeter is impacted by the change.) and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929536 Title: [SRU] GDM background configurable with gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929536] [NEW] [SRU] GDM background configurable with gsettings
Public bug reported: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases and ultimately this will be released for 20.04. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 ** Affects: gnome-shell (Ubuntu) Importance: Medium Status: Fix Released ** Affects: gnome-shell (Ubuntu Focal) Importance: Medium Status: New ** Also affects: gnome-shell (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Focal) Milestone: None => ubuntu-20.04.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929536 Title: [SRU] GDM background configurable with gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929038] Re: [SRU] Backport to 20.04 LTS
** Changed in: golang-1.16 (Ubuntu Focal) Milestone: None => ubuntu-20.04.3 ** Changed in: adsys (Ubuntu Focal) Milestone: None => ubuntu-20.04.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921374] Re: [SRU] New feature: Active Directory support
** Changed in: ubiquity (Ubuntu Focal) Status: In Progress => New ** Changed in: livecd-rootfs (Ubuntu Focal) Status: In Progress => New ** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: Jean-Baptiste Lallement (jibel) => (unassigned) ** Changed in: ubiquity (Ubuntu Focal) Assignee: Jean-Baptiste Lallement (jibel) => (unassigned) ** Changed in: livecd-rootfs (Ubuntu Focal) Milestone: None => ubuntu-20.04.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921374 Title: [SRU] New feature: Active Directory support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921374] Re: [SRU] New feature: Active Directory support
must succeed. - The home directory of the user must be created dynamically. [Where problems could occur] If the python code and debconf templates, Ubiquity won't start at all or the user info page will not be displayed. So it will highly visible and easy to diagnose. Otherwise, SSSD and Kerberos may not be configured correctly and will prevent login as an AD user. In this case, we still keep the local user and it is possible to log in and diagnose and fix the issue. [Other Info] Built and tested on latest focal daily image. ** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) ** Description changed: [Impact] This feature allows to join a machine to an Active Directory domain at installation time. It adds a check box in the user info stage, which once selected displays a page to enter the credentials to join the domain. It installs the required packages on the target filesystem and configures SSSD and Kerberos so it works on first boot. This feature also required: 1. A change to the seed to include additional packages for AD connectivity. https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=a83c543f5fb98d4a539815b89b43cf9076c00283 2. A change to livecd-rootfs to add the required dependencies via a chroot hook for the project ubuntu to workaround bug 1921862 in Focal. - [Test Plan] + [Test Plan Ubiquity] Prerequisites: A network with an up and running AD controller, DHCP and DNS. 1. Start the installer either from a live session or ubiquity-dm 2. Proceed to the step "Who are you?" 3. Enter the user and computer information. For the computer name, you must use the FQDN. 4. Check box "Use Active Directory" and press continue. 5. Enter the address of the Active Directory controller and credentials of the user allowed to add machines to the domain. 6. Verify that the server is reachable by pressing "Test Connection". 7. Once all the information has been entered and is valid, press "Continue" to proceed with the remaining usual steps of the installation. 8. At the end of the installation you can reboot the machine and you are ready to log in as a user of the domain on first boot More information about initial installation on the ADSys' Wiki: https://github.com/ubuntu/adsys/wiki/2.-Prerequisites *Verification* - Log in as a user of the domain must succeed. - The home directory of the user must be created dynamically. + [Test Plan livecd-rootfs] + 1. Build an image with the patched version of livecd-rootfs + 2. Compare the manifest to an image without the patch + + *Verification* + - No package should be removed with the patched version + - The following packages and their dependencies should be added: sssd, realmd, adcli, krb5-config + + [Where problems could occur] If the python code and debconf templates, Ubiquity won't start at all or the user info page will not be displayed. So it will highly visible and easy to diagnose. Otherwise, SSSD and Kerberos may not be configured correctly and will prevent login as an AD user. In this case, we still keep the local user and it is possible to log in and diagnose and fix the issue. [Other Info] Built and tested on latest focal daily image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921374 Title: [SRU] New feature: Active Directory support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929201] Re: Packages in PPA are not installed if version higher than in a release pocket
** Attachment added: "buildlog_ubuntu_focal_amd64_ubuntu-archive_BUILDING_with_ppa.txt.gz" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1929201/+attachment/5499210/+files/buildlog_ubuntu_focal_amd64_ubuntu-archive_BUILDING_with_ppa.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929201 Title: Packages in PPA are not installed if version higher than in a release pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1929201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929201] Re: Packages in PPA are not installed if version higher than in a release pocket
** Attachment added: "buildlog_ubuntu_focal_amd64_ubuntu-archive_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1929201/+attachment/5499209/+files/buildlog_ubuntu_focal_amd64_ubuntu-archive_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929201 Title: Packages in PPA are not installed if version higher than in a release pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1929201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929201] [NEW] Packages in PPA are not installed if version higher than in a release pocket
Public bug reported:
While trying to find a workaround for bug 1921862, we tried building a
rootfs of Ubuntu Desktop from a PPA that contains a new version of
ubiquity and zsys in focal.
Current version in the archive:
ubiquity | 20.04.15| focal
ubiquity | 20.04.15.11 | focal-updates
zsys | 0.4.5 | focal
zsys | 0.4.8 | focal-updates
Versions in the PPA (https://launchpad.net/~jibel/+archive/ubuntu/ppa/+packages)
ubiquity | 20.04.15.12~ppa3
zsys | 0.4.8ubuntu1ppa1
The results of the builds are:
Without the PPA (same than an Ubuntu Desktop build without proposed)
https://launchpad.net/~jibel/+livefs/ubuntu/focal/ubuntu-archive/+build/276788
With the PPA
https://launchpad.net/~jibel/+livefs/ubuntu/focal/ubuntu-archive/+build/276827
The builds have been triggered with the API, the only difference is the
metadata_override which contains the PPA:
In [67]: livefs2.requestBuild(archive = archive, distro_arch_series = das,
metadata_override= {'project': 'ubuntu'}, pocket='Updates')
Out[67]: https://api.launchpad.net/devel/~jibel/+livefs/ubuntu/focal/ubuntu-archive/+build/276788>
In [68]: livefs2.requestBuild(archive = archive, distro_arch_series = das,
metadata_override= {'project': 'ubuntu', 'extra_ppas' : ['jibel/ppa']},
pocket='Updates')
Out[68]: https://api.launchpad.net/devel/~jibel/+livefs/ubuntu/focal/ubuntu-archive/+build/276827>
(archive is the primary archive)
If you compare the 2 builds
ubiquity and zsys and in the first build but not the second.
** Affects: livecd-rootfs (Ubuntu)
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/1929201
Title:
Packages in PPA are not installed if version higher than in a release
pocket
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1929201/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921862] Re: Call germinate with -updates
We tried the workaround to add the packages as dependencies of Ubiquity and rebuilding an ISO with the new Ubiquity and the dependencies pulled automatically. Unfortunately, the result is not what is expected. The packages are installed in the live session and the target file system. AD is configured by Ubiquity as expected during installation. The packages are marked to be kept after installation. But at the end of the installation, the packages are removed then reinstalled by the installer. As a consequence the configuration done during installation is reset. We tried to modify script/plugininstall.py and scripts/install.py to force keep the packages by they are still considered garbage by apt and removed. Finally we added a list of packages to keep so they are not considered to "autopurge" by Ubiquity, the packages are kept as expected by not their dependencies even if they are strong one. The resulting installation is completely inconsistent. Using this approach would mean to manually calculate the list of dependencies of the packages to keep and mark them as keep. This is clearly not something maintainable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921862 Title: Call germinate with -updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921374] Re: [SRU] New feature: Active Directory support
** Description changed: TODO [Impact] This feature allows to join a machine to an Active Directory domain at installation time. It adds a check box in the user info stage, which once selected displays a page to enter the credentials to join the domain. It installs the required packages on the target filesystem and configures SSSD and Kerberos so it works on first boot. This feature also required a change to the seed to include additional packages for AD connectivity. https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=a83c543f5fb98d4a539815b89b43cf9076c00283 + and to the dependencies of Ubiquity to workaround bug 1921862 in Focal. + [Test Plan] + Prerequisites: + A network with an up and running AD controller, DHCP and DNS. + + 1. Start the installer either from a live session or ubiquity-dm + 2. Proceed to the step "Who are you?" + 3. Enter the user and computer information. For the computer name, you must use the FQDN. + 4. Check box "Use Active Directory" and press continue. + 5. Enter the address of the Active Directory controller and credentials of the user allowed to add machines to the domain. + 6. Verify that the server is reachable by pressing "Test Connection". + 7. Once all the information has been entered and is valid, press "Continue" to proceed with the remaining usual steps of the installation. + 8. At the end of the installation you can reboot the machine and you are ready to log in as a user of the domain on first boot + + More information about initial installation on the ADSys' Wiki: + https://github.com/ubuntu/adsys/wiki/2.-Prerequisites + + *Verification* + - Log in as a user of the domain must succeed. + - The home directory of the user must be created dynamically. + [Where problems could occur] If the python code and debconf templates, Ubiquity won't start at all or the user info page will not be displayed. So it will highly visible and easy to diagnose. Otherwise, SSSD and Kerberos may not be configured correctly and will prevent login as an AD user. In this case, we still keep the local user and it is possible to log in and diagnose and fix the issue. [Other Info] Built and tested on latest focal daily image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921374 Title: [SRU] New feature: Active Directory support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921862] Re: Call germinate with -updates
Thanks for your advice. As a workaround we'll try to make the packages a dependency of Ubiquity (or ubiquity-gtk since the UI only exist for this UI) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921862 Title: Call germinate with -updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
