[Bug 2076381] Re: [MIR] retry
So, retry are in the release pocket for focal and noble, it seems we can’t do post-release promotion in those pockets (which are surely read only): I’m getting: Override component to main retry 1.0.5-3 in noble: universe/misc -> main retry 1.0.5-3 in noble amd64: universe/utils/optional/100% -> main retry 1.0.5-3 in noble arm64: universe/utils/optional/100% -> main retry 1.0.5-3 in noble armhf: universe/utils/optional/100% -> main retry 1.0.5-3 in noble ppc64el: universe/utils/optional/100% -> main retry 1.0.5-3 in noble riscv64: universe/utils/optional/100% -> main retry 1.0.5-3 in noble s390x: universe/utils/optional/100% -> main Override [y|N]? y Traceback (most recent call last): File "/home/didrocks/tools/bin/ubuntu-archive-tools/./change-override", line 231, in main() File "/home/didrocks/tools/bin/ubuntu-archive-tools/./change-override", line 227, in main change_overrides(options, args) File "/home/didrocks/tools/bin/ubuntu-archive-tools/./change-override", line 147, in change_overrides if publication.changeOverride(**kwargs): File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 642, in __call__ response, content = self.root._browser._request( File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 484, in _request raise error lazr.restfulclient.errors.BadRequest: HTTP Error 400: Bad Request Response headers: --- -content-encoding: gzip connection: close content-length: 40 content-security-policy: frame-ancestors 'self'; content-type: text/plain;charset=utf-8 date: Thu, 12 Sep 2024 15:20:05 GMT server: gunicorn status: 400 strict-transport-security: max-age=15552000 transfer-encoding: chunked vary: Accept,Accept-Encoding x-content-type-options: nosniff x-frame-options: SAMEORIGIN x-launchpad-revision: 1b1ed1ad2dbfc71ee62b5c5491c975135a771bf0 x-lazr-notifications: [] x-powered-by: Zope (www.zope.org), Python (www.python.org) x-request-id: 4a0db52c-7b76-4da2-a113-61b5fcaa2572 x-vcs-revision: 1b1ed1ad2dbfc71ee62b5c5491c975135a771bf0 x-xss-protection: 1; mode=block --- Response body: --- b"Cannot change overrides in suite 'noble'" --- It probably means we need to SRU them, as a no-change rebuild, and then, we can promote them in -updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076381 Title: [MIR] retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080372] Re: SRU golang 1.23.1 to older releases
** Also affects: golang-1.23 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: golang-1.23 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: golang-1.23 (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/2080372 Title: SRU golang 1.23.1 to older releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.23/+bug/2080372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080372] [NEW] SRU golang 1.23.1 to older releases
Public bug reported: [ Impact ] Our incoming WSL Pro Service is a go tool that will require for both security reasons and new features usage Go 1.23. We will have a single code base for 20.04, 22.04 and 24.04 LTSes. Note that this SRU is only about 22.04 and 24.04 as 20.04 will be treated separately. [ Test Plan ] 1. Install golang 1.23 2. Run `go version` ouside of any workspace -> ensure go 1.23 is printed 3. Build wsl-pro-service with it (adjusting the PATH) -> ensure it builds and that tests pass [ Where problems could occur ] The go package is a new, per version, package. It doesn’t change any of the default PATH and is opt-in for application. So, problems will occur inside the package itself or for application that are explicitely opting in, but not outside. [ Other info ] We are already building and testing special Pro for WSL images which are using this go version and properties from this PPA: https://launchpad.net/~ubuntu-wsl-dev/+archive/ubuntu/ppa ** Affects: golang-1.23 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: golang-1.23 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: golang-1.23 (Ubuntu Noble) 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/2080372 Title: SRU golang 1.23.1 to older releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.23/+bug/2080372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066269] Re: [MIR] sysprof
Override component to main libsysprof-6-6 47~beta-1 in oracular amd64: universe/libs/optional/100% -> main libsysprof-6-6 47~beta-1 in oracular arm64: universe/libs/optional/100% -> main libsysprof-6-6 47~beta-1 in oracular armhf: universe/libs/optional/100% -> main libsysprof-6-6 47~beta-1 in oracular i386: universe/libs/optional/100% -> main libsysprof-6-6 47~beta-1 in oracular ppc64el: universe/libs/optional/100% -> main libsysprof-6-6 47~beta-1 in oracular riscv64: universe/libs/optional/100% -> main libsysprof-6-6 47~beta-1 in oracular s390x: universe/libs/optional/100% -> main libsysprof-6-dev 47~beta-1 in oracular amd64: universe/libdevel/optional/100% -> main libsysprof-6-dev 47~beta-1 in oracular arm64: universe/libdevel/optional/100% -> main libsysprof-6-dev 47~beta-1 in oracular armhf: universe/libdevel/optional/100% -> main libsysprof-6-dev 47~beta-1 in oracular i386: universe/libdevel/optional/100% -> main libsysprof-6-dev 47~beta-1 in oracular ppc64el: universe/libdevel/optional/100% -> main libsysprof-6-dev 47~beta-1 in oracular riscv64: universe/libdevel/optional/100% -> main libsysprof-6-dev 47~beta-1 in oracular s390x: universe/libdevel/optional/100% -> main libsysprof-6-modules 47~beta-1 in oracular amd64: universe/libs/optional/100% -> main libsysprof-6-modules 47~beta-1 in oracular arm64: universe/libs/optional/100% -> main libsysprof-6-modules 47~beta-1 in oracular armhf: universe/libs/optional/100% -> main libsysprof-6-modules 47~beta-1 in oracular i386: universe/libs/optional/100% -> main libsysprof-6-modules 47~beta-1 in oracular ppc64el: universe/libs/optional/100% -> main libsysprof-6-modules 47~beta-1 in oracular riscv64: universe/libs/optional/100% -> main libsysprof-6-modules 47~beta-1 in oracular s390x: universe/libs/optional/100% -> main sysprof 47~beta-1 in oracular amd64: universe/devel/optional/100% -> main sysprof 47~beta-1 in oracular arm64: universe/devel/optional/100% -> main sysprof 47~beta-1 in oracular armhf: universe/devel/optional/100% -> main sysprof 47~beta-1 in oracular ppc64el: universe/devel/optional/100% -> main sysprof 47~beta-1 in oracular riscv64: universe/devel/optional/100% -> main sysprof 47~beta-1 in oracular s390x: universe/devel/optional/100% -> main Override [y|N]? y 27 publications overridden. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066269 Title: [MIR] sysprof To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysprof/+bug/2066269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076381] Re: [MIR] retry
In main now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076381 Title: [MIR] retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078827] Re: [MIR] luit
$ ./change-override -c main -S luit Override component to main luit 2.0.20221028-1 in oracular: universe/misc -> main luit 2.0.20221028-1 in oracular amd64: universe/utils/optional/100% -> main luit 2.0.20221028-1 in oracular arm64: universe/utils/optional/100% -> main luit 2.0.20221028-1 in oracular armhf: universe/utils/optional/100% -> main luit 2.0.20221028-1 in oracular ppc64el: universe/utils/optional/100% -> main luit 2.0.20221028-1 in oracular riscv64: universe/utils/optional/100% -> main luit 2.0.20221028-1 in oracular s390x: universe/utils/optional/100% -> main Override [y|N]? y 7 publications overridden. ** Changed in: luit (Ubuntu) Status: Fix Committed => 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/2078827 Title: [MIR] luit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/luit/+bug/2078827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066262] Re: [MIR] libdex
$ ./change-override -c main -S libdex Override component to main libdex 0.7.1-1 in oracular: universe/misc -> main gir1.2-dex-1 0.7.1-1 in oracular amd64: universe/introspection/optional/100% -> main gir1.2-dex-1 0.7.1-1 in oracular arm64: universe/introspection/optional/100% -> main gir1.2-dex-1 0.7.1-1 in oracular armhf: universe/introspection/optional/100% -> main gir1.2-dex-1 0.7.1-1 in oracular i386: universe/introspection/optional/100% -> main gir1.2-dex-1 0.7.1-1 in oracular ppc64el: universe/introspection/optional/100% -> main gir1.2-dex-1 0.7.1-1 in oracular riscv64: universe/introspection/optional/100% -> main gir1.2-dex-1 0.7.1-1 in oracular s390x: universe/introspection/optional/100% -> main libdex-1-1 0.7.1-1 in oracular amd64: universe/libs/optional/100% -> main libdex-1-1 0.7.1-1 in oracular arm64: universe/libs/optional/100% -> main libdex-1-1 0.7.1-1 in oracular armhf: universe/libs/optional/100% -> main libdex-1-1 0.7.1-1 in oracular i386: universe/libs/optional/100% -> main libdex-1-1 0.7.1-1 in oracular ppc64el: universe/libs/optional/100% -> main libdex-1-1 0.7.1-1 in oracular riscv64: universe/libs/optional/100% -> main libdex-1-1 0.7.1-1 in oracular s390x: universe/libs/optional/100% -> main libdex-dev 0.7.1-1 in oracular amd64: universe/libdevel/optional/100% -> main libdex-dev 0.7.1-1 in oracular arm64: universe/libdevel/optional/100% -> main libdex-dev 0.7.1-1 in oracular armhf: universe/libdevel/optional/100% -> main libdex-dev 0.7.1-1 in oracular i386: universe/libdevel/optional/100% -> main libdex-dev 0.7.1-1 in oracular ppc64el: universe/libdevel/optional/100% -> main libdex-dev 0.7.1-1 in oracular riscv64: universe/libdevel/optional/100% -> main libdex-dev 0.7.1-1 in oracular s390x: universe/libdevel/optional/100% -> main libdex-doc 0.7.1-1 in oracular amd64: universe/doc/optional/100% -> main libdex-doc 0.7.1-1 in oracular arm64: universe/doc/optional/100% -> main libdex-doc 0.7.1-1 in oracular armhf: universe/doc/optional/100% -> main libdex-doc 0.7.1-1 in oracular i386: universe/doc/optional/100% -> main libdex-doc 0.7.1-1 in oracular ppc64el: universe/doc/optional/100% -> main libdex-doc 0.7.1-1 in oracular riscv64: universe/doc/optional/100% -> main libdex-doc 0.7.1-1 in oracular s390x: universe/doc/optional/100% -> main Override [y|N]? y 29 publications overridden. ** Changed in: libdex (Ubuntu) Status: Fix Committed => 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/2066262 Title: [MIR] libdex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdex/+bug/2066262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066272] Re: [MIR] libpanel
$ ./change-override -c main -S libpanel Override component to main libpanel 1.7.1-3 in oracular: universe/misc -> main gir1.2-panel-1 1.7.1-3 in oracular amd64: universe/introspection/optional/100% -> main gir1.2-panel-1 1.7.1-3 in oracular arm64: universe/introspection/optional/100% -> main gir1.2-panel-1 1.7.1-3 in oracular armhf: universe/introspection/optional/100% -> main gir1.2-panel-1 1.7.1-3 in oracular ppc64el: universe/introspection/optional/100% -> main gir1.2-panel-1 1.7.1-3 in oracular riscv64: universe/introspection/optional/100% -> main gir1.2-panel-1 1.7.1-3 in oracular s390x: universe/introspection/optional/100% -> main libpanel-1-1 1.7.1-3 in oracular amd64: universe/libs/optional/100% -> main libpanel-1-1 1.7.1-3 in oracular arm64: universe/libs/optional/100% -> main libpanel-1-1 1.7.1-3 in oracular armhf: universe/libs/optional/100% -> main libpanel-1-1 1.7.1-3 in oracular ppc64el: universe/libs/optional/100% -> main libpanel-1-1 1.7.1-3 in oracular riscv64: universe/libs/optional/100% -> main libpanel-1-1 1.7.1-3 in oracular s390x: universe/libs/optional/100% -> main libpanel-common 1.7.1-3 in oracular amd64: universe/libs/optional/100% -> main libpanel-common 1.7.1-3 in oracular arm64: universe/libs/optional/100% -> main libpanel-common 1.7.1-3 in oracular armhf: universe/libs/optional/100% -> main libpanel-common 1.7.1-3 in oracular i386: universe/libs/optional/100% -> main libpanel-common 1.7.1-3 in oracular ppc64el: universe/libs/optional/100% -> main libpanel-common 1.7.1-3 in oracular riscv64: universe/libs/optional/100% -> main libpanel-common 1.7.1-3 in oracular s390x: universe/libs/optional/100% -> main libpanel-dev 1.7.1-3 in oracular amd64: universe/libdevel/optional/100% -> main libpanel-dev 1.7.1-3 in oracular arm64: universe/libdevel/optional/100% -> main libpanel-dev 1.7.1-3 in oracular armhf: universe/libdevel/optional/100% -> main libpanel-dev 1.7.1-3 in oracular ppc64el: universe/libdevel/optional/100% -> main libpanel-dev 1.7.1-3 in oracular riscv64: universe/libdevel/optional/100% -> main libpanel-dev 1.7.1-3 in oracular s390x: universe/libdevel/optional/100% -> main libpanel-doc 1.7.1-3 in oracular amd64: universe/doc/optional/100% -> main libpanel-doc 1.7.1-3 in oracular arm64: universe/doc/optional/100% -> main libpanel-doc 1.7.1-3 in oracular armhf: universe/doc/optional/100% -> main libpanel-doc 1.7.1-3 in oracular i386: universe/doc/optional/100% -> main libpanel-doc 1.7.1-3 in oracular ppc64el: universe/doc/optional/100% -> main libpanel-doc 1.7.1-3 in oracular riscv64: universe/doc/optional/100% -> main libpanel-doc 1.7.1-3 in oracular s390x: universe/doc/optional/100% -> main Override [y|N]? y 33 publications overridden. ** Changed in: libpanel (Ubuntu) Status: Fix Committed => 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/2066272 Title: [MIR] libpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpanel/+bug/2066272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080223] Re: Ensure WSL instances do not rely on the Windows launcher by using the new build pipeline
** Description changed: Note: all changes are related to each other and need to land together before next WSL image rebuild. Previously, WSL instances relied on a very lightweight build pipeline which was using the CPC image. In 22.04 we did a first step to have WSL has its own project in livecd-rootfs, with its own seed and image to produce a rootfs. However, a lot of ubuntu differentatior (enabling systemd by default, managing upgrade policy based on the distribution name, cloud-init enablement) were relying on an .exe file, ran on first launch, to ensure that those policies were modified. Microsoft is going to remove soon those launcher, and so, we won’t have an entrypoint to modify those policies. We thus needs to ship between one and three rootfs, varying on the upgrade policy (we produce multiple Windows applications on the store). This work has started on 24.04, and rely on cloud-init, (shipping pro client too for future wsl pro service offering). We thus needs to align our previous LTS on the latest state of art for WSL. Note that 20.04 will be more involved and will be treated separately. This is about aligning 22.04 and 24.04. What is needed in 22.04: - ensure livecd-rootfs can create between one and 3 tarballs, with different upgrade policy and enable systemd by default as a non conffiles. - - ensure we ship the same set of default application (aligning the seed), to include cloud-init and other tools that developers expect on a WSL system. Also, the pro client is shipped as it will be required with our new Pro on WSL offering. + - ensure we ship the same set of default application (aligning the seed), to include cloud-init and other tools that developers expect on a WSL system. Also, the pro client and lanscapes are shipped as it will be required with our new Pro on WSL offering. - ship wsl-setup: * it will drop some systemd experimation (that was never enabled by default), * it’s moving all the systemd units adjustements to take into account a WSL environment (Microsoft kernel, being a distro inside its own namespace running in parallel to other distros…) * enable cloud init WSL datasource * remove core 22.04 support and installer wrapper script as we don’t ship snaps by default anymore nor installer. * report the status of cloud-init in MoTD if it fails What is needed in 24.04: - ship wsl-setup: * it’s moving all the systemd units adjustements to take into account a WSL environment (Microsoft kernel, being a distro inside its own namespace running in parallel to other distros…) * enable cloud init WSL datasource * remove core 22.04 support and installer wrapper script as we don’t ship snaps by default anymore nor installer. * report the status of cloud-init in MoTD if it fails [ Impact ] The impacts are primarly on new rootfses produced by our build pipeline with CPC. It allows CPC also to not special case 24.04 for rootfs publication. So, only new images could see an impact on 24.04 and 22.04 setup, which is easily spottable. The other set of impacts is on systemd units, ensuring that we have the systemd units executed with success as expected and have a working system in the end. Finally, aligning the set of components update in 22.04 which are the defaults tool installed by default, will ensure we are aligning with 24.04. [ Test Plan ] 1. Build new rootfses (with CPC), publish them on cloud-images.ubuntu.com -> we should see one image ending up with "ubuntults" for 22.04 image -> we should have 2 images for 24.04: "ubuntu" and "ubuntults". 2. Build the Ubuntu (24.04), Ubuntu24.04 and Ubuntu22.04 windows package A. New installations: 1. Ship a cloud-init file to touch a file on disk on `%USERPROFILE%\.cloud-init\default.user-data` 2. For each ubuntu application, install them on the machine and create an user on disk -> Check that basic shell commands works -> Check that no MoTD messages complains about cloud-init failure -> Check that the file from the cloud-init profile was applied -> Run systemctl --failed and ensure nothing is listed related to WSL specific configuration itself -> Pro attach the machine and check that it’s attached B. Upgrade testing: Have a 22.04 and 24.04 WSL application installed. On each of them, do the following: 1. apt update && apt full-upgrade 2. wsl --shutdown 3. restart the instance 4. Check the A.2 items all pass. [ Where problems could occur ] Most of the issues could happen on initial boot. It will be really easy to spot any issues there with the previous test plan. On upgrade, the main difference will be in that we replace already shipped systemd unit overrides created by the launcher with some coming from a package. So, the override should still be applied, just in a cleaner way. This is also easily detectable thanks to the previous test pla
[Bug 2080223] Re: Ensure WSL instances do not rely on the Windows launcher by using the new build pipeline
** Description changed: + Note: all changes are related to each other and need to land together + before next WSL image rebuild. + Previously, WSL instances relied on a very lightweight build pipeline which was using the CPC image. In 22.04 we did a first step to have WSL has its own project in livecd-rootfs, with its own seed and image to produce a rootfs. However, a lot of ubuntu differentatior (enabling systemd by default, managing upgrade policy based on the distribution name, cloud-init enablement) were relying on an .exe file, ran on first launch, to ensure that those policies were modified. Microsoft is going to remove soon those launcher, and so, we won’t have an entrypoint to modify those policies. We thus needs to ship between one and three rootfs, varying on the upgrade policy (we produce multiple Windows applications on the store). This work has started on 24.04, and rely on cloud-init, (shipping pro client too for future wsl pro service offering). We thus needs to align our previous LTS on the latest state of art for WSL. Note that 20.04 will be more involved and will be treated separately. This is about aligning 22.04 and 24.04. What is needed in 22.04: - ensure livecd-rootfs can create between one and 3 tarballs, with different upgrade policy and enable systemd by default as a non conffiles. - ensure we ship the same set of default application (aligning the seed), to include cloud-init and other tools that developers expect on a WSL system. Also, the pro client is shipped as it will be required with our new Pro on WSL offering. - ship wsl-setup: * it will drop some systemd experimation (that was never enabled by default), * it’s moving all the systemd units adjustements to take into account a WSL environment (Microsoft kernel, being a distro inside its own namespace running in parallel to other distros…) * enable cloud init WSL datasource * remove core 22.04 support and installer wrapper script as we don’t ship snaps by default anymore nor installer. * report the status of cloud-init in MoTD if it fails What is needed in 24.04: - ship wsl-setup: * it’s moving all the systemd units adjustements to take into account a WSL environment (Microsoft kernel, being a distro inside its own namespace running in parallel to other distros…) * enable cloud init WSL datasource * remove core 22.04 support and installer wrapper script as we don’t ship snaps by default anymore nor installer. * report the status of cloud-init in MoTD if it fails [ Impact ] The impacts are primarly on new rootfses produced by our build pipeline with CPC. It allows CPC also to not special case 24.04 for rootfs publication. So, only new images could see an impact on 24.04 and 22.04 setup, which is easily spottable. The other set of impacts is on systemd units, ensuring that we have the systemd units executed with success as expected and have a working system in the end. Finally, aligning the set of components update in 22.04 which are the defaults tool installed by default, will ensure we are aligning with 24.04. [ Test Plan ] 1. Build new rootfses (with CPC), publish them on cloud-images.ubuntu.com -> we should see one image ending up with "ubuntults" for 22.04 image -> we should have 2 images for 24.04: "ubuntu" and "ubuntults". 2. Build the Ubuntu (24.04), Ubuntu24.04 and Ubuntu22.04 windows package A. New installations: 1. Ship a cloud-init file to touch a file on disk on `%USERPROFILE%\.cloud-init\default.user-data` 2. For each ubuntu application, install them on the machine and create an user on disk -> Check that basic shell commands works -> Check that no MoTD messages complains about cloud-init failure -> Check that the file from the cloud-init profile was applied -> Run systemctl --failed and ensure nothing is listed related to WSL specific configuration itself -> Pro attach the machine and check that it’s attached B. Upgrade testing: Have a 22.04 and 24.04 WSL application installed. On each of them, do the following: 1. apt update && apt full-upgrade 2. wsl --shutdown 3. restart the instance 4. Check the A.2 items all pass. [ Where problems could occur ] Most of the issues could happen on initial boot. It will be really easy to spot any issues there with the previous test plan. On upgrade, the main difference will be in that we replace already shipped systemd unit overrides created by the launcher with some coming from a package. So, the override should still be applied, just in a cleaner way. This is also easily detectable thanks to the previous test plan. The set of updated default tools in 22.04 will show a bigger update than usual, but as we expect most of people to use the "ubuntu" image and also ubuntu24.04 Windows store application, the alignements is risk-less and will give coherence from an
[Bug 2080223] [NEW] Ensure WSL instances do not rely on the Windows launcher by using the new build pipeline
Public bug reported: Previously, WSL instances relied on a very lightweight build pipeline which was using the CPC image. In 22.04 we did a first step to have WSL has its own project in livecd-rootfs, with its own seed and image to produce a rootfs. However, a lot of ubuntu differentatior (enabling systemd by default, managing upgrade policy based on the distribution name, cloud-init enablement) were relying on an .exe file, ran on first launch, to ensure that those policies were modified. Microsoft is going to remove soon those launcher, and so, we won’t have an entrypoint to modify those policies. We thus needs to ship between one and three rootfs, varying on the upgrade policy (we produce multiple Windows applications on the store). This work has started on 24.04, and rely on cloud-init, (shipping pro client too for future wsl pro service offering). We thus needs to align our previous LTS on the latest state of art for WSL. Note that 20.04 will be more involved and will be treated separately. This is about aligning 22.04 and 24.04. What is needed in 22.04: - ensure livecd-rootfs can create between one and 3 tarballs, with different upgrade policy and enable systemd by default as a non conffiles. - ensure we ship the same set of default application (aligning the seed), to include cloud-init and other tools that developers expect on a WSL system. Also, the pro client is shipped as it will be required with our new Pro on WSL offering. - ship wsl-setup: * it will drop some systemd experimation (that was never enabled by default), * it’s moving all the systemd units adjustements to take into account a WSL environment (Microsoft kernel, being a distro inside its own namespace running in parallel to other distros…) * enable cloud init WSL datasource * remove core 22.04 support and installer wrapper script as we don’t ship snaps by default anymore nor installer. * report the status of cloud-init in MoTD if it fails What is needed in 24.04: - ship wsl-setup: * it’s moving all the systemd units adjustements to take into account a WSL environment (Microsoft kernel, being a distro inside its own namespace running in parallel to other distros…) * enable cloud init WSL datasource * remove core 22.04 support and installer wrapper script as we don’t ship snaps by default anymore nor installer. * report the status of cloud-init in MoTD if it fails [ Impact ] The impacts are primarly on new rootfses produced by our build pipeline with CPC. It allows CPC also to not special case 24.04 for rootfs publication. So, only new images could see an impact on 24.04 and 22.04 setup, which is easily spottable. The other set of impacts is on systemd units, ensuring that we have the systemd units executed with success as expected and have a working system in the end. Finally, aligning the set of components update in 22.04 which are the defaults tool installed by default, will ensure we are aligning with 24.04. [ Test Plan ] 1. Build new rootfses (with CPC), publish them on cloud-images.ubuntu.com -> we should see one image ending up with "ubuntults" for 22.04 image -> we should have 2 images for 24.04: "ubuntu" and "ubuntults". 2. Build the Ubuntu (24.04), Ubuntu24.04 and Ubuntu22.04 windows package A. New installations: 1. Ship a cloud-init file to touch a file on disk on `%USERPROFILE%\.cloud-init\default.user-data` 2. For each ubuntu application, install them on the machine and create an user on disk -> Check that basic shell commands works -> Check that no MoTD messages complains about cloud-init failure -> Check that the file from the cloud-init profile was applied -> Run systemctl --failed and ensure nothing is listed related to WSL specific configuration itself -> Pro attach the machine and check that it’s attached B. Upgrade testing: Have a 22.04 and 24.04 WSL application installed. On each of them, do the following: 1. apt update && apt full-upgrade 2. wsl --shutdown 3. restart the instance 4. Check the A.2 items all pass. [ Where problems could occur ] Most of the issues could happen on initial boot. It will be really easy to spot any issues there with the previous test plan. On upgrade, the main difference will be in that we replace already shipped systemd unit overrides created by the launcher with some coming from a package. So, the override should still be applied, just in a cleaner way. This is also easily detectable thanks to the previous test plan. The set of updated default tools in 22.04 will show a bigger update than usual, but as we expect most of people to use the "ubuntu" image and also ubuntu24.04 Windows store application, the alignements is risk-less and will give coherence from an user perspective. [ Other info ] We are already building and testing special Pro for WSL images which are using this build pipeline and properties (+ shipping wsl-pro-service + new golang which will be treated separately) in those PPA: - https://launchpad.net/~u
[Bug 1747759] Re: [MIR] cpdb-libs
$ ./change-override -c main -t cpdb-libs Override component to main cpdb-libs 2.0~b5-1.2build1 in oracular: universe/net -> main Override [y|N]? y 1 publication overridden. $ ./change-override -c main libcpdb-frontend2t64 libcpdb2t64 Override component to main libcpdb-frontend2t64 2.0~b5-1.2build1 in oracular amd64: universe/libs/optional/100% -> main libcpdb-frontend2t64 2.0~b5-1.2build1 in oracular arm64: universe/libs/optional/100% -> main libcpdb-frontend2t64 2.0~b5-1.2build1 in oracular armhf: universe/libs/optional/100% -> main libcpdb-frontend2t64 2.0~b5-1.2build1 in oracular i386: universe/libs/optional/100% -> main libcpdb-frontend2t64 2.0~b5-1.2build1 in oracular ppc64el: universe/libs/optional/100% -> main libcpdb-frontend2t64 2.0~b5-1.2build1 in oracular riscv64: universe/libs/optional/100% -> main libcpdb-frontend2t64 2.0~b5-1.2build1 in oracular s390x: universe/libs/optional/100% -> main libcpdb2t64 2.0~b5-1.2build1 in oracular amd64: universe/libs/optional/100% -> main libcpdb2t64 2.0~b5-1.2build1 in oracular arm64: universe/libs/optional/100% -> main libcpdb2t64 2.0~b5-1.2build1 in oracular armhf: universe/libs/optional/100% -> main libcpdb2t64 2.0~b5-1.2build1 in oracular i386: universe/libs/optional/100% -> main libcpdb2t64 2.0~b5-1.2build1 in oracular ppc64el: universe/libs/optional/100% -> main libcpdb2t64 2.0~b5-1.2build1 in oracular riscv64: universe/libs/optional/100% -> main libcpdb2t64 2.0~b5-1.2build1 in oracular s390x: universe/libs/optional/100% -> main Override [y|N]? y 14 publications overridden. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747759 Title: [MIR] cpdb-libs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpdb-libs/+bug/1747759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747760] Re: [MIR] cpdb-backend-cups
$ ./change-override -c main -S cpdb-backend-cups Override component to main cpdb-backend-cups 2.0b5-1ubuntu1 in oracular: universe/net -> main cpdb-backend-cups 2.0b5-1ubuntu1 in oracular amd64: universe/net/optional/100% -> main cpdb-backend-cups 2.0b5-1ubuntu1 in oracular arm64: universe/net/optional/100% -> main cpdb-backend-cups 2.0b5-1ubuntu1 in oracular armhf: universe/net/optional/100% -> main cpdb-backend-cups 2.0b5-1ubuntu1 in oracular ppc64el: universe/net/optional/100% -> main cpdb-backend-cups 2.0b5-1ubuntu1 in oracular riscv64: universe/net/optional/100% -> main cpdb-backend-cups 2.0b5-1ubuntu1 in oracular s390x: universe/net/optional/100% -> main Override [y|N]? y 7 publications overridden. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747760 Title: [MIR] cpdb-backend-cups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpdb-backend-cups/+bug/1747760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074086] Re: MIR libimobiledevice-glue
Review for Source Package: libimobiledevice-glue [Summary] MIR team ACK As the package had many CVEs in the past, and as it’s parsing external content fdrom untrusted source, I think we should then ask for a security review. I'll thus assign ubuntu-security. List of specific binary packages to be promoted to main: libimobiledevice-glue-1.0-0, libimobiledevice-glue-dev [Rationale, Duplication and Ownership] There is no other package in main providing the same functionality. A team is committed to own long term maintenance of this package. The rationale given in the report seems valid and useful for Ubuntu [Dependencies] OK: - no other Dependencies to MIR due to this - libimobiledevice-glue checked with `check-mir` all dependencies can be found in `seeded-in-ubuntu` (already in main) - none of the (potentially auto-generated) dependencies (Depends and Recommends) that are present after build are not in main - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have unexpected Built-Using entries - not a go package, no extra constraints to consider in that regard - not a rust package, no extra constraints to consider in that regard [Security] OK: - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not expose any external endpoint (port/socket/... or similar) - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) - does not deal with cryptography (en-/decryption, certificates, signing, ...) - this makes appropriate (for its exposure) use of established risk mitigation features (dropping permissions, using temporary environments, restricted users/groups, seccomp, systemd isolation features, apparmor, ...) Problems: - Many CVEs in the past. I think we should then ask for a security review, parsing external content fdrom untrusted source [Common blockers] OK: - does not FTBFS currently - does have a non-trivial test suite that runs as autopkgtest - no new python2 dependency Problems: - No package build time testsuite, but autopkgtests one. [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking is in place. - debian/watch is present and looks ok - Upstream update history is good - Debian/Ubuntu update history is good - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far - no massive Lintian warnings - debian/rules is rather clean - It is not on the lto-disabled list [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (as far as we can check it) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside tests) - no use of user nobody (consider at least `grep -Hrn nobody` for it and run `find . -user nobody` in source and built binaries) - no use of setuid / setgid (consider at least `grep -Hrn -e setuid -e setgid` for it and run `find . \( -perm -4000 -o -perm -2000 \)` in source and built binaries) - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit or libseed - not part of the UI for extra checks - no translation present, but none needed for this case ** Changed in: libimobiledevice-glue (Ubuntu) Assignee: Didier Roche-Tolomelli (didrocks) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074086 Title: MIR libimobiledevice-glue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice-glue/+bug/2074086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071396] Re: [MIR] libdisplay-info
Override component to main libdisplay-info 0.2.0-2 in oracular: universe/misc -> main libdisplay-info-dev 0.2.0-2 in oracular amd64: universe/libdevel/optional/100% -> main libdisplay-info-dev 0.2.0-2 in oracular arm64: universe/libdevel/optional/100% -> main libdisplay-info-dev 0.2.0-2 in oracular armhf: universe/libdevel/optional/100% -> main libdisplay-info-dev 0.2.0-2 in oracular ppc64el: universe/libdevel/optional/100% -> main libdisplay-info-dev 0.2.0-2 in oracular riscv64: universe/libdevel/optional/100% -> main libdisplay-info-dev 0.2.0-2 in oracular s390x: universe/libdevel/optional/100% -> main libdisplay-info2 0.2.0-2 in oracular amd64: universe/libs/optional/100% -> main libdisplay-info2 0.2.0-2 in oracular arm64: universe/libs/optional/100% -> main libdisplay-info2 0.2.0-2 in oracular armhf: universe/libs/optional/100% -> main libdisplay-info2 0.2.0-2 in oracular ppc64el: universe/libs/optional/100% -> main libdisplay-info2 0.2.0-2 in oracular riscv64: universe/libs/optional/100% -> main libdisplay-info2 0.2.0-2 in oracular s390x: universe/libs/optional/100% -> main ** Changed in: libdisplay-info (Ubuntu) Status: Fix Committed => 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/2071396 Title: [MIR] libdisplay-info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdisplay-info/+bug/2071396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071396] Re: [MIR] libdisplay-info
I had a rereview as requested by jbicha to unblock GNOME-Shell as slyon is unavailable for some time. All required TODOs are fixed and some recommended TODOs are. The package is showing up in c-m mistmatch now. Acking the MIR. ** Changed in: libdisplay-info (Ubuntu) Status: New => 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/2071396 Title: [MIR] libdisplay-info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdisplay-info/+bug/2071396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071396] Re: [MIR] libdisplay-info
** Changed in: libdisplay-info (Ubuntu) Assignee: Lukas Märdian (slyon) => Didier Roche-Tolomelli (didrocks) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071396 Title: [MIR] libdisplay-info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdisplay-info/+bug/2071396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073895] Re: [MIR] isa-support
Review for Source Package: isa-support [Summary] MIR team ACK This does not need a security review. I only have one question: you mention that this package "… has no purpose on its own, but only via being depended on by other software". Do you have any examples about what is going to depend on each variation of the binary packages so that they are pulled from a package in main? [Rationale, Duplication and Ownership] There is no other package in main providing the same functionality. The rationale given in the report seems valid and useful for Ubuntu [Dependencies] OK: - no other Dependencies to MIR due to this - isa-support checked with `check-mir` - all dependencies can be found in `seeded-in-ubuntu` (already in main) - none of the (potentially auto-generated) dependencies (Depends and Recommends) that are present after build are not in main - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have unexpected Built-Using entries - not a go package, no extra constraints to consider in that regard - not a rust package, no extra constraints to consider in that regard [Security] OK: - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not parse data formats (files [images, video, audio, xml, json, asn.1], network packets, structures, ...) from an untrusted source. - does not expose any external endpoint (port/socket/... or similar) - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) - does not deal with cryptography (en-/decryption, certificates, signing, ...) - this makes appropriate (for its exposure) use of established risk mitigation features (dropping permissions, using temporary environments, restricted users/groups, seccomp, systemd isolation features, apparmor, ...) [Common blockers] OK: - does not FTBFS currently - does have a non-trivial test suite that runs as autopkgtest - This does not need special HW for build or test - no new python2 dependency Problems: - does not have a test suite that runs at build time, but those don’t make sense at this stage. It does have autopkgtests for each feature. [Packaging red flags] OK: - Ubuntu does not carry a delta (only a rebuild) - symbols tracking not applicable for this kind of code. - debian/watch is not present but also not needed (e.g. native) - Upstream update history is (good/slow/sporadic) - Debian/Ubuntu update history is (good/slow/sporadic) - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far - no massive Lintian warnings - debian/rules is rather clean - It is not on the lto-disabled list [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (as far as we can check it) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside tests) - no use of user nobody - no use of setuid / setgid - use of setuid, but ok because TBD (prefer systemd to set those for services) - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit or libseed - not part of the UI for extra checks - no translation present, but none needed for this case ** Changed in: isa-support (Ubuntu) Assignee: Didier Roche-Tolomelli (didrocks) => (unassigned) ** Changed in: isa-support (Ubuntu) Status: New => 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/2073895 Title: [MIR] isa-support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isa-support/+bug/2073895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074086] Re: MIR libimobiledevice-glue
Ok, I see now that the autopkgtest part was merged and the description was updated even if the part "- The package does have not failing autopkgtests right now" was still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074086 Title: MIR libimobiledevice-glue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice-glue/+bug/2074086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074086] Re: MIR libimobiledevice-glue
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074086 Title: MIR libimobiledevice-glue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice-glue/+bug/2074086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073895] Re: [MIR] isa-support
** Changed in: isa-support (Ubuntu) Assignee: (unassigned) => Didier Roche-Tolomelli (didrocks) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073895 Title: [MIR] isa-support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isa-support/+bug/2073895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071396] Re: [MIR] libdisplay-info
** Changed in: libdisplay-info (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) ** Changed in: libdisplay-info (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071396 Title: [MIR] libdisplay-info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdisplay-info/+bug/2071396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074078] Re: [MIR] ubuntu-x13s-settings
** Changed in: ubuntu-x13s-settings (Ubuntu) Assignee: (unassigned) => Christian Ehrhardt (paelzer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074078 Title: [MIR] ubuntu-x13s-settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-x13s-settings/+bug/2074078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074086] Re: MIR libimobiledevice-glue
** Changed in: libimobiledevice-glue (Ubuntu) Assignee: (unassigned) => Didier Roche-Tolomelli (didrocks) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074086 Title: MIR libimobiledevice-glue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice-glue/+bug/2074086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058192] Re: [MIR] lenovo-wwan-unlock
r/lib (/usr/lib/libconfigservice350.so, /usr/lib/libconfigserviceR+.so, /usr/lib/libmodemauth.so). Are they really shared library being used by 3rd parties (I think dlopened without -dev package)? If so, they would need symbol tracking. If not, I suggest probably shipping them under /opt and either using RPATH or LD_LIBRARY_PATH on their corresponding services? - The lintian output marked as Error should be cleaned up. As they are all about having binaries in /opt, a lintian override with a comment taken from the rationale of the description would be great. - There are multiple other warnings in the lintian output. Some of them, like the -dbgsym package not shipping debug symbols could be fixed by bypassing -dbgsym generation. Others that are not in our control could be overridden to mute the warning. - Why unpacking under debian/temp, while in case of multi-binary packages, the install target is automatically set to debian/tmp? I would suggest using debian/tmp to conform with the multi binary packages. This would help simplify the debian/rules files (no need for cleaning manually for instance). [Upstream red flags] OK: - no Errors/warnings during the build - no use of user nobody - no use of setuid / setgid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit or libseed - not part of the UI for extra checks - no translation present, but none needed for this case (user visible)? Note: closed source, so most of the upstream code check can’t be done. ** Changed in: lenovo-wwan-unlock (Ubuntu) Assignee: Didier Roche-Tolomelli (didrocks) => Canonical Security Team (canonical-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058192 Title: [MIR] lenovo-wwan-unlock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2058192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058192] Re: [MIR] lenovo-wwan-unlock
** Changed in: lenovo-wwan-unlock (Ubuntu) Assignee: (unassigned) => Didier Roche-Tolomelli (didrocks) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058192 Title: [MIR] lenovo-wwan-unlock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2058192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065349] Re: [SRU] Default user created by cloud-init confuses WSLg
I have sponsored the package to oracular first. This one is 0.5.3. I did change the VCS to update debian/changelog. And tag it as v0.5.3. I have changed the SRU (noble) backport to: - target noble as release series in the SRU bug. - have a version that is SRU compatible (it needs to be ealier than the one in oracular, so it’s 0.5.3~24.04) - not removing previous rebuild upload changelog in noble (we don't really remove changelog in the SRU, to minimize the diff and not remove the package history in a given pocket). Subscribing SRU team. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065349 Title: [SRU] Default user created by cloud-init confuses WSLg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2065349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065349] Re: [SRU] Default user created by cloud-init confuses WSLg
** Also affects: wsl-setup (Ubuntu Noble) 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/2065349 Title: [SRU] Default user created by cloud-init confuses WSLg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2065349/+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
golang 1.22 is now in mantic NEW queue and adsys 0.14.1~23.10 is in the unapproved queue (the only change on the last one is that I adapted the debdiff to not remove the rebuild upload changelog entry). -- 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 (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&queue_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 qual
[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&queue_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 qual
[Bug 2048232] Re: [SRU] Backport to 22.04 LTS
** Description changed: As part of our entreprise desktop offering, there is the request to backport ubuntu-proxy-manager to 22.04 LTS. The package is in universe for now. Ubuntu Proxy Manager is a D-Bus mediated service intended to be triggered by ADSys, our Active Directory GPO integration. ADSys has been available starting Ubuntu 21.04, and Ubuntu Proxy Manager was first released in Ubuntu 23.04. + + It depends on the new golang 1.22 SRU attached to + https://bugs.launchpad.net/ubuntu/+source/golang-1.22/+bug/2059756 [Impact] * ubuntu-proxy-manager is a new package. Impact is thus only for people installing. * To leverage the functionality of the package, a recent enough ADSys version must be used (at least 0.11.0, not currently in Jammy but there are approved plans to backport ADSys 0.13.2). * In addition to the ADSys requirement above, the machine must be Pro-enabled and a Proxy GPO must be configured on the Windows AD controller. * No impact is expected if the conditions above are not met. * This is a entreprise feature requested by desktop customers running LTS. [Test Plan] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5 (AD user should be able to log in). Instructions can be found on https://github.com/ubuntu/adsys/wiki/2.-Prerequisites 2. Install admx and adml files on your AD controller: https://canonical-adsys.readthedocs-hosted.com/en/stable/how-to/set-up-ad/ 3. Join machine to Ubuntu Pro to enable proxy policy application 4. Configure some proxy settings in AD (https://canonical-adsys.readthedocs-hosted.com/en/stable/explanation/proxy/), for instance: * HTTP Proxy * Ignored hosts 5. Install ADSys (at least version 0.11.0) and ubuntu-proxy-manager, then run `adsysctl update -m` to force a refresh of the policies 6. Ensure GSettings/APT/environment proxy values are correctly set (full list of supported proxy backends can be seen here: https://github.com/ubuntu/ubuntu-proxy-manager#supported-backends) 7. Remove/purge the ubuntu-proxy-manager package and run `adsysctl update -m` again -- a warning should show reflecting that ADSys has detected a configured proxy policy but ubuntu-proxy-manager is not installed for it to be applied. ADSys's exit code will remain 0. [Where problems could occur] * Network access of various programs will be hindered if incorrect proxy settings are configured. [Other Info] * The current version of ADSys in Jammy does not interact with this package whatsoever, but there are plans to backport the latest version. * A passing PPA build for ubuntu-proxy-manager can be seen here: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/15678628/+listing-archive-extra - * We have previously requested a FFe for ubuntu-proxy-manager for Focal: https://bugs.launchpad.net/ubuntu/jammy/+source/adsys/+bug/2012371 + * We have previously requested a FFe for ubuntu-proxy-manager for Focal: https://bugs.launchpad.net/ubuntu/jammy/+source/adsys/+bug/2012371 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048232 Title: [SRU] Backport to 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-proxy-manager/+bug/2048232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048514] Re: [SRU] Backport to 22.04 LTS
** Changed in: python-cepces (Ubuntu) Status: In Progress => New ** Changed in: python-requests-gssapi (Ubuntu) Status: In Progress => New ** Also affects: python-requests-gssapi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: python-cepces (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: python-cepces (Ubuntu) Status: New => Fix Released ** Changed in: python-requests-gssapi (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/2048514 Title: [SRU] Backport to 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-cepces/+bug/2048514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048232] Re: [SRU] Backport to 22.04 LTS
** Changed in: ubuntu-proxy-manager (Ubuntu) Status: In Progress => New ** Also affects: ubuntu-proxy-manager (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ubuntu-proxy-manager (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/2048232 Title: [SRU] Backport to 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-proxy-manager/+bug/2048232/+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
** Changed in: golang-1.22 (Ubuntu) Status: New => Fix Released ** 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 + * 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&queue_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:
[Bug 2061850] Re: Can't authenticate in TTY after installing authd, but sudo works
The issue had been identified to be in GDM. ** Package changed: authd (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061850 Title: Can't authenticate in TTY after installing authd, but sudo works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2061850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048781] Re: [MIR] authd
We decided to remove the authd package in noble for the time being. The current implementation (in particular the one in the PAM module) is not up to our standard in terms of quality and what we are confortable to support in the long term. Rather than releasing as is and having risky SRUs in the future changing a large part of the implementation, we decided against this and rather polishing the code, securing it, adding even more tests and releasing all that as a new package SRUed to the 24.04 LTS in the coming months. That way, we won’t risk to regress any potential users and we will use an architecture we are more confortable supporting for the next 5/10 years of the LTS release. It means that when we reintroduce it, we will rerequest a new MIR too as the PAM module will largely change and we want to ensure we follow the process and quality standard we expect for the Ubuntu distribution. ** Changed in: authd (Ubuntu) Status: In Progress => 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/2048781 Title: [MIR] authd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2048781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060546] Re: [FFe] Update authd to current version
Removing packages from noble: authd 0.2.1 in noble authd 0.2.1 in noble amd64 authd 0.2.1 in noble arm64 authd 0.2.1 in noble armhf authd 0.2.1 in noble ppc64el authd 0.2.1 in noble riscv64 authd 0.2.1 in noble s390x Comment: Removing from noble for now. See the rationale in LP: #2060546 Remove [y|N]? y 1 package successfully removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060546 Title: [FFe] Update authd to current version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2060546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060546] Re: [FFe] Update authd to current version
We decided to remove the authd package in noble for the time being. The current implementation (in particular the one in the PAM module) is not up to our standard in terms of quality and what we are confortable to support in the long term. Rather than releasing as is and having risky SRUs in the future changing a large part of the implementation, we decided against this and rather polishing the code, securing it, adding even more tests and releasing all that as a new package SRUed to the 24.04 LTS in the coming months. That way, we won’t risk to regress any potential users and we will use an architecture we are more confortable supporting for the next 5/10 years of the LTS release. It means that when we reintroduce it, we will rerequest a new MIR too as the PAM module will largely change and we want to ensure we follow the process and quality standard we expect for the Ubuntu distribution. ** Changed in: authd (Ubuntu) Status: Triaged => 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/2060546 Title: [FFe] Update authd to current version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2060546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052495] Re: [MIR] wsl-pro-service
The last security request (having per user certificate to secure the gRPC communication so that they can’t be hijacked cross-users) is now addressed with 0.1.4 with many other enhancements fixing some recommended TODOs. I’m proceeding thus with the promotion. ** Changed in: wsl-pro-service (Ubuntu Noble) 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/2052495 Title: [MIR] wsl-pro-service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2052495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062133] Re: Migration to the snap issues
yeah, informing the user will go a long way IMHO! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062133 Title: Migration to the snap issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2062133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062133] [NEW] Migration to the snap issues
Public bug reported: After migrating to the snap, I noticed the following: - the launcher icon disappeared (I guess it’s because the .desktop file is now "thunderbird_thunderbird.desktop" - the snap migration took a good 5 minutes on my machine (I guess it’s the copy of the email folder), without any feedbacks that something is happening if you don’t look at ps output. You don’t have any visual feedback about the migration and we should have a progress window (maybe zenity?) to reassure on this one time transition - all unread emails triggered notification (I guess it’s because the state is considered "New") on any folders. - I know have 2 15G folders now: ~/snap/thunderbird/common/ and ~/.thunderbird. I think the latter was the old one which is unused right now and it should be cleaned up after the migration to the snap? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 09:28:35 2024 InstallationDate: Installed on 2020-04-24 (1455 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SnapChanges: Identifiant État DescendancePrêt Résumé 700 Done 2024-04-18T09:06:12+02:00 2024-04-18T09:07:34+02:00 Installer le paquet Snap "thunderbird" SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062133 Title: Migration to the snap issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2062133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver
Confirming that it’s fixed on the same machine with 550. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061079 Title: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061079] [NEW] Rendering issues on text with nvidia driver
Public bug reported: With nvidia driver, all GTK4 applications have label rendering issues. They are not refresh until passing the cursor over them, giving blank windows. The corner are white and not themed. Passing from one app scren to another one reproduces the issue. gnome-control-center or files, for instance, are blank by default. As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue. Related upstream bugs and discussions are: - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 -- $ glxinfo name of display: :1 display: :1 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 4096 MB Total available memory: 4096 MB Currently available dedicated video memory: 3041 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1050/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.239.06 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_bindless_texture, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, GL_ARB_color_buffer_float, GL_ARB_compressed_texture_pixel_storage, GL_ARB_compute_shader, GL_ARB_compute_variable_group_size, GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_cull_distance, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_derivative_control, GL_ARB_direct_state_access, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect, GL_ARB_draw_instanced, GL_ARB_enhanced_layouts, GL
[Bug 2060546] Re: [FFe] Update authd to current version
** Summary changed: - Update authd to current version + [FFe] Update authd to current version ** Description changed: Authd is a new package in noble, in universe. This package is not shipped by default, we made many improvements and fixes in the current version. We don’t plan to seed it this release, despite the MIR being approved. Update contains a lot of vendoring updates, and code changes (using a C wrapper to wrap around the Go code in the PAM module to fix some instability), multiple thousands of line due to the C wrapper in particular. The diff itself will not be meaningful. Part of meaningful fixes are the default group being added and ssh precheck API. Full changelog is available at https://github.com/ubuntu/authd/pull/237/files. + It also fixes a vulnerability by depending on latest Go and latest + x/net/http. + This is the code level we are testing and relying on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060546 Title: [FFe] Update authd to current version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2060546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060548] Re: [FFe] Update and seed wsl-pro-service in the WSL images
** Summary changed: - Update and seed wsl-pro-service in the WSL images + [FFe] Update and seed wsl-pro-service in the WSL images ** Description changed: This is a new package for this release. It’s only functional with a Windows agent which is not publically released and under beta for now. As the end of the beta will be after the 24.04 release, we want to get as close as possible to the current code level, knowing that current code will still certainly grow feature-wise once with the Beta user feedback. However, having it seeded (the MIR is approved and security issues fixed but the certificate one, which has been discussed as minor for now) with the current code level will be great to diminish the diff when the SRU that will be needed then. The impact is on existing non beta users (and beta users are using a ppa with the ppa containing the current code level). Current diff is large as the development is very active and won’t really provide anything more. Note that it contains also a packaging change to fix bug #2057651. + + It also fixes a vulnerability by depending on latest Go and latest + x/net/http. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060548 Title: [FFe] Update and seed wsl-pro-service in the WSL images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060548] [NEW] Update and seed wsl-pro-service in the WSL images
Public bug reported: This is a new package for this release. It’s only functional with a Windows agent which is not publically released and under beta for now. As the end of the beta will be after the 24.04 release, we want to get as close as possible to the current code level, knowing that current code will still certainly grow feature-wise once with the Beta user feedback. However, having it seeded (the MIR is approved and security issues fixed but the certificate one, which has been discussed as minor for now) with the current code level will be great to diminish the diff when the SRU that will be needed then. The impact is on existing non beta users (and beta users are using a ppa with the ppa containing the current code level). Current diff is large as the development is very active and won’t really provide anything more. Note that it contains also a packaging change to fix bug #2057651. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Affects: wsl-pro-service (Ubuntu) Importance: Undecided Status: New ** 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/2060548 Title: Update and seed wsl-pro-service in the WSL images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060546] [NEW] Update authd to current version
Public bug reported: Authd is a new package in noble, in universe. This package is not shipped by default, we made many improvements and fixes in the current version. We don’t plan to seed it this release, despite the MIR being approved. Update contains a lot of vendoring updates, and code changes (using a C wrapper to wrap around the Go code in the PAM module to fix some instability), multiple thousands of line due to the C wrapper in particular. The diff itself will not be meaningful. Part of meaningful fixes are the default group being added and ssh precheck API. Full changelog is available at https://github.com/ubuntu/authd/pull/237/files. This is the code level we are testing and relying on. ** Affects: authd (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/2060546 Title: Update authd to current version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2060546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060273] [NEW] secondary users are not listed in polkit graphical prompt
Public bug reported: Tested with 124-1ubuntu1 on noble 1. Create 3 users on the machine: - sudo-user1, part of sudo group - sudo-user2, part of sudo group - normal-user, not part of the sudo group 2. Login with normal-user 3. Try to execute pkexec or any other command prompting for polkit -> only sudo-user1 password auth is proposed, before, we had a listbox to select all eligible user 4. Remove sudo-user1 5. Try pkexec again: -> now sudo-user2 is proposed, showing that the configuration for this user is correct. It seems that only the first "admin" of the machine is taken into account. However, as normal-user, I may not have sudo-user1 around, but only sudo-user2. ** Affects: policykit-1 (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/2060273 Title: secondary users are not listed in polkit graphical prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2060273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054480] Re: [MIR] nbd-client
With this in light (but we have the wider "everything that is in main for a very long time in ubuntu, even being security reviewed and got multiple uploads), I would agree that -server could have another security/fresh look. Do you think it’s something the security team has the capacity to look? Otherwise, we may not want to special case this case, as the problem is really linked to the pre-existing packages in main (even GNOME for instance in general, didn’t get a security review… and even if it did, GNOME has nothing looking like the one released in 2004). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054480 Title: [MIR] nbd-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004442] Re: [MIR] aom (dependency of libheif)
Confirming that the only REQUIRED TODO is now fixed. Thanks for checking it slyon! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004442 Title: [MIR] aom (dependency of libheif) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aom/+bug/2004442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051916] Re: [MIR] promote libtraceevent as a trace-cmd dependency
Hey everyone and Paul. First, sorry for the delayed answered (I was thinking you would get me reassign and for some reason, I missed subscribing to the bug) > But I do not really understand the harm of having these entries kept for documentation, except this could pile up and become a mess at some point. Do we have a policy regarding the removal of these entries (count of version, age)? There is no strict policy, I understand the historical part of having it for documenting. I suggest to keep it for some release, but if this is doable, cleanup after a while. It’s not something we want to keep hanging around forever. I see that you want to remove them in a future upload, good! All the required TODOs are now fullfilled, thanks for working on those! I’m thus happy to MIR ack this package now! ** Changed in: libtraceevent (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/2051916 Title: [MIR] promote libtraceevent as a trace-cmd dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtraceevent/+bug/2051916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048781] Re: [MIR] authd
I continued exploring this topic myself last week and was able to rely on a tool developed for this: https://github.com/coreos/cargo-vendor- filterer/. This tool is not ideal in the sense that: - it vendorize the whole content - then, it filters by replacing entire crates based on some filtering rules, like arch, platform or file exclusion. The replacement is done by empty module, and rechecksumming. So basically, cargo and rustc still thinks the crate is available, it just happens to be empty. Consequently, we wouldn’t know if we are impacted or not by security issue before manual checking. However, I see this as a step in the right direction, so I implemented this in authd: https://github.com/ubuntu/authd/pull/270/files. Here, we are filtering to only keep Linux platform, on all our supported architectures (which is tier 1 and 2 in Rust world). The benefit is that we are now able to remove our manual recheckshumming after purging the binary library archive files which are part of some crates. This tool run during the package source build. I would feel better if this was packaged and maintained in ubuntu (as this injects potentially some code), and part of our standard tooling. I will reach out the Rust maintainer for the incoming engineering sprint. I think we can still trust this repository as it’s part of a well-known organization with multi-decades open source famous maintainers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048781 Title: [MIR] authd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2048781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054480] Re: [MIR] nbd-client
blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a non-trivial test suite that runs as autopkgtest - no new python2 dependency Problems: - there is a really trivial autopkgtests (which is good for bootstrapping), but does not cover most of the functionality of the package. We should either get a more exhaustive autopkgtest testsuite or (as a fallback) a manual test plan [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - Upstream update history is good - Debian/Ubuntu update history is good - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - debian/rules is rather clean - It is not on the lto-disabled list Problems: - debian/watch is not present, but the debian maintainer is upstream too :) [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (as far as we can check it) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside tests) - no use of user nobody (consider at least `grep -Hrn nobody` for it and run `find . -user nobody` in source and built binaries) - use of setuid, but ok because this is not in the -client package but -server which already had a security review - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case Problems: - Some usage of setuid, but ok as this is not in the -client package but -server. ** Changed in: nbd (Ubuntu) Status: New => Incomplete ** Changed in: nbd (Ubuntu) Assignee: Didier Roche-Tolomelli (didrocks) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054480 Title: [MIR] nbd-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048781] Re: [MIR] authd
We agreed during the MIR meeting that a generic tooling as part of debhelper would be the best way, didn’t we? See my arguments above different upstream policies in different source packages, where if we start introducing this in a per-package base, that would create divergences between projects. Does it make sense to have this centrally managed (by our Rust toolchain expert, ideally?). That way, we can go beyond trimming the windows crates, like tree shaking and so on? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048781 Title: [MIR] authd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2048781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
