[Bug 2080257] Re: [WSL] systemd fails to upgrade on WSL1
root@drenec:~# SYSTEMD_LOG_LEVEL=debug systemd-sysusers basic.conf systemd-journal.conf systemd-network.conf Locking /etc/.pwd.lock failed: Invalid argument Failed to take /etc/passwd lock: Invalid argument -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080257 Title: [WSL] systemd fails to upgrade on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2080257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078473] Re: Discovery of KRB5 ticket fails even if ticket is discoverable
** Description changed: tracking bug https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245 [ Impact ] Even if the krb5 ticket is discoverable, the discovery fails (but actually succeeded) So we cannot retrieve the policies or do any action with the controller. [ Test Plan ] This is not something that can be easily reproduced in a real environment, so the best approach to reproduce this issue is: - 1. Get adsys codebase before the fix. You can do this by getting the available version in the archive with `apt source adsys`. - 2. Run the TestTicketPath test located in internal/ad/krb5_test.go as many times as needed to get the failure (using `go test -run TestTicketPatch -count X` inside the mentioned directory runs the test X times). + 1. Get adsys codebase before the fix. You can do this by getting the available version in the archive with the command: + apt source adsys + 2. Run the TestTicketPath test located in internal/ad/krb5_test.go as many times as needed to get the failure. To run the test, open a terminal and, inside the mentioned directory, runs the test X times with the command: + go test -run TestTicketPatch -count X 3. The test can fail due to krb5_init_context changing the errno without returning any error. + + Without the patched version the test will fail after a number of runs. + With the patch, it will not fail. [ Where problems could occur ] We now reset errno to 0, because krb5_init_context() can alter it, even if it succeeds. So the discovery always returns success when it succeeds. Worst case would be that discovery failed but errno is set to 0 but this is handled earlier in the code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078473 Title: Discovery of KRB5 ticket fails even if ticket is discoverable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080233] Re: [wsl] do-release-upgrade fails with systemd disabled
** Description changed: Original report: https://github.com/ubuntu/WSL/issues/493 On WSL, systemd is not always enabled. This is the case on WSL1 where it cannot be enabled and on WSL2 when it's been disabled or not enabled by default. When systemd is not available do-release-upgrade fails with the error below and upgrade is cancelled: - """ + From the report + === Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-uqmd8iby/noble", line 8, in sys.exit(main()) File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeMain.py", line 241, in main if app.run(): File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2642, in run return self.fullUpgrade() File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2447, in fullUpgrade if not self.doPostInitialUpdate(): File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 1438, in doPostInitialUpdate self.quirks.run("PostInitialUpdate") File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 102, in run func() File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 127, in noblePostInitialUpdate self._test_and_fail_on_tpm_fde() File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 1898, in _test_and_fail_on_tpm_fde snap_list = subprocess.check_output(['snap', 'list']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['snap', 'list']' returned non-zero exit status 1. """ This error should be ignored when systemd is not running. Read https://github.com/ubuntu/WSL/issues/493#issuecomment-2324510606 for details. Thanks to Vadim for the investigation. + + """ + In /tmp/ubuntu-release-upgrader-t8sg0mg9/DistUpgrade/DistUpgradeQuirks.py: + + def _test_and_fail_on_tpm_fde(self): + """ + LP: #2065229 + """ + try: + snap_list = subprocess.check_output(['snap', 'list']) + snaps = [s.decode().split()[0] for s in snap_list.splitlines()] + except FileNotFoundError: + # snapd not installed? + return + I think except FileNotFoundError: should be extended to except: + + Because DistUpgradeQuirks.py is stored in some temp directory, it was hard to change it inplace, but I succeeded, and then the upgrade process continued as it should + === -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080233 Title: [wsl] do-release-upgrade fails with systemd disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080257] [NEW] [WSL] systemd fails to upgrade on WSL1
Public bug reported: Original report: https://github.com/ubuntu/WSL/issues/493 On WSL with systemd disabled (wsl1 or wsl2 without systemd enabled), systemd fails to upgrade. # Test Case WSL1 1. Install Ubuntu 24.04 with WSL from a Windows shell wsl --install --enable-wsl1 ubuntu-24.04 or wsl --install ubuntu-24.04 wsl --set-version ubuntu-24.04 1 => Verify that 24.04 is using version 1 NAMESTATE VERSION Ubuntu-22.04Stopped 2 Ubuntu-24.04Running 1 2. Start the distro if it is not already running ubuntu2404.exe 3. In the distro run the following command: sudo apt install --reinstall systemd # Expected result systemd is reinstalled without any issue # Actual result systemd postinst script fails and the following error is displayed to the user: ``` root@drenec:~# apt install --reinstall systemd Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 2 not upgraded. Need to get 3470 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 systemd amd64 255.4-1ubuntu8.4 [3470 kB] Fetched 3470 kB in 1s (2816 kB/s) (Reading database ... 40771 files and directories currently installed.) Preparing to unpack .../systemd_255.4-1ubuntu8.4_amd64.deb ... Unpacking systemd (255.4-1ubuntu8.4) over (255.4-1ubuntu8.4) ... Setting up systemd (255.4-1ubuntu8.4) ... Failed to take /etc/passwd lock: Invalid argument dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 1 Processing triggers for dbus (1.14.10-4ubuntu4.1) ... Processing triggers for man-db (2.12.0-4build2) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) ``` There is no easy way to recover from the error. ** Affects: systemd (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/2080257 Title: [WSL] systemd fails to upgrade on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2080257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080233] Re: [wsl] do-release-upgrade fails with systemd disabled
** Description changed: Original report: https://github.com/ubuntu/WSL/issues/493 On WSL, systemd is not always enabled. This is the case on WSL1 where it cannot be enabled and on WSL2 when it's been disabled or not enabled by default. When systemd is not available do-release-upgrade fails with the error below and upgrade is cancelled: """ Traceback (most recent call last): - File "/tmp/ubuntu-release-upgrader-uqmd8iby/noble", line 8, in - sys.exit(main()) - File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeMain.py", line 241, in main - if app.run(): - File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2642, in run - return self.fullUpgrade() - File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2447, in fullUpgrade - if not self.doPostInitialUpdate(): - File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 1438, in doPostInitialUpdate - self.quirks.run("PostInitialUpdate") - File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 102, in run - func() - File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 127, in noblePostInitialUpdate - self._test_and_fail_on_tpm_fde() - File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 1898, in _test_and_fail_on_tpm_fde - snap_list = subprocess.check_output(['snap', 'list']) - File "/usr/lib/python3.10/subprocess.py", line 421, in check_output - return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, - File "/usr/lib/python3.10/subprocess.py", line 526, in run - raise CalledProcessError(retcode, process.args, + File "/tmp/ubuntu-release-upgrader-uqmd8iby/noble", line 8, in + sys.exit(main()) + File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeMain.py", line 241, in main + if app.run(): + File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2642, in run + return self.fullUpgrade() + File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2447, in fullUpgrade + if not self.doPostInitialUpdate(): + File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 1438, in doPostInitialUpdate + self.quirks.run("PostInitialUpdate") + File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 102, in run + func() + File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 127, in noblePostInitialUpdate + self._test_and_fail_on_tpm_fde() + File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 1898, in _test_and_fail_on_tpm_fde + snap_list = subprocess.check_output(['snap', 'list']) + File "/usr/lib/python3.10/subprocess.py", line 421, in check_output + return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, + File "/usr/lib/python3.10/subprocess.py", line 526, in run + raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['snap', 'list']' returned non-zero exit status 1. """ This error should be ignored when systemd is not running. + + Read https://github.com/ubuntu/WSL/issues/493#issuecomment-2324510606 + for details. Thanks to Vadim for the investigation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080233 Title: [wsl] do-release-upgrade fails with systemd disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080233] [NEW] [wsl] do-release-upgrade fails with systemd disabled
Public bug reported: Original report: https://github.com/ubuntu/WSL/issues/493 On WSL, systemd is not always enabled. This is the case on WSL1 where it cannot be enabled and on WSL2 when it's been disabled or not enabled by default. When systemd is not available do-release-upgrade fails with the error below and upgrade is cancelled: """ Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-uqmd8iby/noble", line 8, in sys.exit(main()) File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeMain.py", line 241, in main if app.run(): File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2642, in run return self.fullUpgrade() File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2447, in fullUpgrade if not self.doPostInitialUpdate(): File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 1438, in doPostInitialUpdate self.quirks.run("PostInitialUpdate") File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 102, in run func() File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 127, in noblePostInitialUpdate self._test_and_fail_on_tpm_fde() File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 1898, in _test_and_fail_on_tpm_fde snap_list = subprocess.check_output(['snap', 'list']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['snap', 'list']' returned non-zero exit status 1. """ This error should be ignored when systemd is not running. ** Affects: ubuntu-release-upgrader (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/2080233 Title: [wsl] do-release-upgrade fails with systemd disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078246] Re: Ignore casing in domain/ section of sssd.conf
** Description changed: Upstream issues: https://github.com/ubuntu/adsys/issues/1054 + tracking bug https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245 [ Impact ] adsys does not accept uppercase domainnames and lowercase ones mixed like this: - [sssd] domains = domain.tld config_file_version = 2 services = nss, pam, ifp default_domain_suffix = domain.tld [domain/DOMAIN.TLD] default_shell = /bin/bash - This imposed to set all the domains to lower cases. This has been introduced by the support for Winbind. - [ Test Plan ] 1. In sssd.conf set the value of the key "domains" and the correponding section to the same domain but with different casing 2. Log in without the patch, the user cannot log in and the following error is displayed in the logs: Jul 17 15:06:09 HOSTNAME systemd[1]: Starting ADSys daemon service... Jul 17 15:06:09 HOSTNAME adsysd[35284]: level=error msg="couldn't create adsys service: could not initialize AD backend: can't get domain configuration from {Conf:/etc/sssd/sssd.conf CacheDir:/var/lib/sss/db}:could not find AD domain section corresponding to "domain.tld"> with the patch the user can log in - [ Where problems could occur ] Worst case, the user still cannot log in [ Other Info ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078246 Title: Ignore casing in domain/ section of sssd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078245] Re: DCONF policy manager removes userdb on empty policy
** Description changed: Upstream issue https://github.com/ubuntu/adsys/issues/1002 + tracking bug https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245 [ Impact ] - This is a regression introduced by the implementation of the purge command in 0.14.1. + This is a regression introduced by the implementation of the purge command in 0.14.1. When the user doesn't have at least one dconf setting set in a policy, the following error is thrown: unable to open named profile (user@domain): using the null configuration - [ Test Plan ] - 1. Create a policy with no dconf rule and make sure it applies to the user or the machiune under test + 1. Create a policy with no dconf rule and make sure it applies to the user or the machiune under test 2. Login on the machine Without the patched version the following error is displayed: "unable to open named profile (user@domain): using the null configuration" With the patched version no error happens - [ Where problems could occur ] The code that purges the dconf DB has been removed. Worst case, a dconf setting still applies while all the dconf rules have been removed from the policy. But then next time the policies applies you'll just end up with an empty dconf db and no dconf settings enforced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078245 Title: DCONF policy manager removes userdb on empty policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078247] Re: rewrite from / to @ formats overwrites usernames
** Description changed: + tracking bug + https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245 + [ Impact ] In this code, the string was not zero terminated properly when overwritten resulting in extra characters: static char *slash_to_at_username(const char *username) { - char *backslash = strchr(username, '\\'); - if (backslash != NULL) { - char *ret = malloc((strlen(username) + 1) * sizeof(char)); - strcpy(ret, backslash + 1); - strcat(ret, "@"); - strncpy(ret + strlen(ret), username, backslash - username); - return ret; - } - return strdup(username); + char *backslash = strchr(username, '\\'); + if (backslash != NULL) { + char *ret = malloc((strlen(username) + 1) * sizeof(char)); + strcpy(ret, backslash + 1); + strcat(ret, "@"); + strncpy(ret + strlen(ret), username, backslash - username); + return ret; + } + return strdup(username); For instance: domain.tld\\user was changed to user@domain.tldld So se user cannot login with the domain\user format [ Test Plan ] 1. On a machine joined to an AD domain with ADsys installed, login with domain\user => Without the patch the user cannot log in => With the patch the user can log in - [ Where problems could occur ] Worst case the user still cannot log in -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078247 Title: rewrite from / to @ formats overwrites usernames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078473] Re: Discovery of KRB5 ticket fails even if ticket is discoverable
** Description changed: + tracking bug + https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245 + [ Impact ] Even if the krb5 ticket is discoverable, the discovery fails (but actually succeeded) So we cannot retrieve the policies or do any action with the controller. - [ Test Plan ] 1. [ Where problems could occur ] We now reset errno to 0, because krb5_init_context() can alter it, even if it succeeds. So the discovery always returns success when it succeeds. Worst case would be that discovery failed but errno is set to 0 but this is handled earlier in the code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078473 Title: Discovery of KRB5 ticket fails even if ticket is discoverable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079824] [NEW] [SRU] bug fix release of adsys 0.14.2
Public bug reported: This is the master bug to track the SRU of ADSys 0.14.2 to 22.04 and 24.04 This version is a bug fix release that addresses the following issues: adsys (0.15) oracular; urgency=medium * Fix DCONF policy manager removing user DB on empty policy (LP: #2078245) * Ignore casing in domain/ section of sssd.conf (LP: #2078246) * Fix parsing of slash usernames (i.e. domain\user) (LP: #2078247) * Fix errno in get_ticket_path(LP: #2078473) ** Affects: adsys (Ubuntu) Importance: High Status: Fix Released ** Affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: adsys (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: adsys (Ubuntu) Status: New => Fix Released ** Changed in: adsys (Ubuntu) Importance: Undecided => High ** Summary changed: - [sru] release of adsys 0.15.2 + [sru] release of adsys 0.14.2 ** Summary changed: - [sru] release of adsys 0.14.2 + [SRU] bug fix release of adsys 0.14.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079824 Title: [SRU] bug fix release of adsys 0.14.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2079824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024377] Re: Adsys can't fetch GPOs
@Sean thanks for your report. Could you file a separate but report for your issue? Also we've a bug fix release coming that is currently available in a PPA. If you can reproduce your issue, could you test the version from the PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and report if it fixes your issue. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024377 Title: Adsys can't fetch GPOs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2024377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078473] Re: Discovery of KRB5 ticket fails even if ticket is discoverable
** Description changed: - [placeholder for - https://github.com/ubuntu/adsys/pull/1065/commits/3d71626665b1560de9159b3b12c13bd5dc3d091a] + [ Impact ] + + Even if the krb5 ticket is discoverable, the discovery fails (but + actually succeeded) So we cannot retrieve the policies or do any action + with the controller. + + + [ Test Plan ] + + 1. + + [ Where problems could occur ] + + We now reset errno to 0, because krb5_init_context() can alter it, even + if it succeeds. So the discovery always returns success when it + succeeds. + + Worst case would be that discovery failed but errno is set to 0 but this + is handled earlier in the code. ** Also affects: adsys (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078473 Title: Discovery of KRB5 ticket fails even if ticket is discoverable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078247] Re: rewrite from / to @ formats overwrites usernames
** Description changed: - [placeholder for https://warthogs.atlassian.net/browse/UDENG-4314] + [ Impact ] + + In this code, the string was not zero terminated properly when + overwritten resulting in extra characters: + + static char *slash_to_at_username(const char *username) { + char *backslash = strchr(username, '\\'); + if (backslash != NULL) { + char *ret = malloc((strlen(username) + 1) * sizeof(char)); + strcpy(ret, backslash + 1); + strcat(ret, "@"); + strncpy(ret + strlen(ret), username, backslash - username); + return ret; + } + return strdup(username); + + For instance: + domain.tld\\user was changed to user@domain.tldld + + So se user cannot login with the domain\user format + + [ Test Plan ] + + 1. On a machine joined to an AD domain with ADsys installed, login with + domain\user + + => Without the patch the user cannot log in + => With the patch the user can log in + + + [ Where problems could occur ] + + Worst case the user still cannot log in ** Also affects: adsys (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078247 Title: rewrite from / to @ formats overwrites usernames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078246] Re: Ignore casing in domain/ section of sssd.conf
** Description changed: - [placeholder for https://github.com/ubuntu/adsys/pull/1079] + Upstream issues: https://github.com/ubuntu/adsys/issues/1054 + + [ Impact ] + + adsys does not accept uppercase domainnames and lowercase ones mixed + like this: + + + [sssd] + domains = domain.tld + config_file_version = 2 + services = nss, pam, ifp + default_domain_suffix = domain.tld + + [domain/DOMAIN.TLD] + default_shell = /bin/bash + + + This imposed to set all the domains to lower cases. + This has been introduced by the support for Winbind. + + + [ Test Plan ] + + 1. In sssd.conf set the value of the key "domains" and the correponding section to the same domain but with different casing + 2. Log in + + without the patch, the user cannot log in and the following error is displayed in the logs: + Jul 17 15:06:09 HOSTNAME systemd[1]: Starting ADSys daemon service... + Jul 17 15:06:09 HOSTNAME adsysd[35284]: level=error msg="couldn't create adsys service: could not initialize AD backend: can't get domain configuration from {Conf:/etc/sssd/sssd.conf CacheDir:/var/lib/sss/db}:could not find AD domain section corresponding to "domain.tld"> + + with the patch the user can log in + + + [ Where problems could occur ] + + Worst case, the user still cannot log in + + [ Other Info ] ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: adsys (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/2078246 Title: Ignore casing in domain/ section of sssd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078245] Re: DCONF policy manager removes userdb on empty policy
** Description changed: - upstream issue https://github.com/ubuntu/adsys/pull/1070 + Upstream issue https://github.com/ubuntu/adsys/issues/1002 + [ Impact ] - * An explanation of the effects of the bug on users and justification -for backporting the fix to the stable release. + This is a regression introduced by the implementation of the purge command in 0.14.1. + When the user doesn't have at least one dconf setting set in a policy, the following error is thrown: - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + unable to open named profile (user@domain): using the null configuration + [ Test Plan ] - * detailed instructions how to reproduce the bug + 1. Create a policy with no dconf rule and make sure it applies to the user or the machiune under test + 2. Login on the machine - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package -fixes the problem. + Without the patched version the following error is displayed: + "unable to open named profile (user@domain): using the null configuration" - * if other testing is appropriate to perform before landing this -update, this should also be described here. + With the patched version no error happens + [ Where problems could occur ] - - * Think about what the upload changes in the software. Imagine the -change is wrong or breaks something else: how would this show up? - - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the event -of a regression. - - * This must never be "None" or "Low", or entirely an argument as to why -your upload is low risk. - - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. - - [ Other Info ] - - * Anything else you think is useful to include - - * Anticipate questions from users, SRU, +1 maintenance, security teams -and the Technical Board and address these questions in advance + The code that purges the dconf DB has been removed. Worst case, a dconf setting still applies while all the dconf rules have been removed from the policy. But then next time the policies applies you'll just end up with an empty dconf db and no dconf settings enforced. ** Also affects: adsys (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: adsys (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078245 Title: DCONF policy manager removes userdb on empty policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078245] Re: DCONF policy manager removes userdb on empty policy
** Description changed: - [placeholder for https://github.com/ubuntu/adsys/pull/1070] + upstream issue https://github.com/ubuntu/adsys/pull/1070 + [ Impact ] + + * An explanation of the effects of the bug on users and justification +for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [ Test Plan ] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package +fixes the problem. + + * if other testing is appropriate to perform before landing this +update, this should also be described here. + + [ Where problems could occur ] + + * Think about what the upload changes in the software. Imagine the +change is wrong or breaks something else: how would this show up? + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the event +of a regression. + + * This must never be "None" or "Low", or entirely an argument as to why +your upload is low risk. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [ Other Info ] + + * Anything else you think is useful to include + + * Anticipate questions from users, SRU, +1 maintenance, security teams +and the Technical Board and address these questions in advance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078245 Title: DCONF policy manager removes userdb on empty policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078245] [NEW] DCONF policy manager removes userdb on empty policy
Public bug reported: [placeholder for https://github.com/ubuntu/adsys/pull/1070] ** Affects: adsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078245 Title: DCONF policy manager removes userdb on empty policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078246] [NEW] Ignore casing in domain/ section of sssd.conf
Public bug reported: [placeholder for https://github.com/ubuntu/adsys/pull/1079] ** Affects: adsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078246 Title: Ignore casing in domain/ section of sssd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078247] [NEW] rewrite from / to @ formats overwrites usernames
Public bug reported: [placeholder for https://warthogs.atlassian.net/browse/UDENG-4314] ** Affects: adsys (Ubuntu) Importance: Undecided Status: New ** Summary changed: - username overwritten during rewrite from / to @ + rewrite from / to @ formats overwrites usernames -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078247 Title: rewrite from / to @ formats overwrites usernames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060769] Re: pro-client execs `apt list --installed` instead of using python3-apt - leading to utf-8 errors
The only difference I noticed between you case and mine, is that your machine is not attached and mine is. ``` $ LC_ALL=C pro status SERVICE ENTITLED STATUS DESCRIPTION anbox-cloud yes disabled Scalable Android in the cloud esm-apps yes enabled Expanded Security Maintenance for Applications esm-infrayes disabled Expanded Security Maintenance for Infrastructure landscapeyes disabled Management and administration tool for Ubuntu For a list of all Ubuntu Pro services, run 'pro status --all' Enable services with: pro enable Account: Subscription: Ubuntu Pro - free personal subscription ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060769 Title: pro-client execs `apt list --installed` instead of using python3-apt - leading to utf-8 errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060769] Re: pro-client execs `apt list --installed` instead of using python3-apt - leading to utf-8 errors
I tried on noble and it doesn't fix the problem. * Firstly the upgrade to the package in proposed doesn't work if I do not force the locale. ``` Il est n cessaire de prendre 250 ko dans les archives. Apr s cette op ration, 12,3 ko d'espace disque suppl mentaires seront utilis s. R ception de :1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 ubuntu-pro-client-l10n amd64 33~24.04 [19,3 kB] R ception de :2 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 ubuntu-pro-client amd64 33~24.04 [231 kB] 250 ko r ceptionn s en 0s (938 ko/s) (Lecture de la base de donn es... 40702 fichiers et r pertoires d j install s.) Pr paration du d paquetage de .../ubuntu-pro-client-l10n_33~24.04_amd64.deb ... D paquetage de ubuntu-pro-client-l10n (33~24.04) sur (32.3~24.04) ... Pr paration du d paquetage de .../ubuntu-pro-client_33~24.04_amd64.deb ... Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 54, in from_package stdout = str(stdout, 'utf-8') UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 584: invalid continuation byte dpkg: avertissement: le sous-processus ancien paquet ubuntu-pro-client script pre-removal a renvoy un tat de sortie d'erreur 1 ``` * Secondly, once the package is installed, pro status is still failing: ``` u@drenec:~$ locale LANG=fr_FR LANGUAGE= LC_CTYPE="fr_FR" LC_NUMERIC="fr_FR" LC_TIME="fr_FR" LC_COLLATE="fr_FR" LC_MONETARY="fr_FR" LC_MESSAGES="fr_FR" LC_PAPER="fr_FR" LC_NAME="fr_FR" LC_ADDRESS="fr_FR" LC_TELEPHONE="fr_FR" LC_MEASUREMENT="fr_FR" LC_IDENTIFICATION="fr_FR" LC_ALL= u@drenec:~$ apt policy ubuntu-pro-client ubuntu-pro-client: Install�: 33~24.04 Candidat�: 33~24.04 Table de version�: *** 33~24.04 100 100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 32.3.1~24.04 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 31.2.3 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages u@drenec:~$ pro status An unexpected error occurred: 'utf-8' codec can't decode byte 0xa0 in position 18: invalid start byte For more details, see the log: /home/u/.cache/ubuntu-pro/ubuntu-pro.log If you think this is a bug, please run: ubuntu-bug ubuntu-advantage-tools ``` From the log the error is: ``` ["2024-07-10T12:14:41.978", "ERROR", "ubuntupro.cli", "wrapper", 1360, "Unhandled exception, please file a bug", {"exc_info": "Traceback (most recent call last):\n File \"/usr/lib/python3/dist-packages/uaclient/cli/__init__.py\", line 1297, in wrapper\nreturn func(*args, **kwargs)\n ^\n File \"/usr/lib/python3/dist-packages/uaclient/cli/__init__.py\", line 1434, in main\nreturn_value = args.action(args, cfg=cfg, extra_args=extra_args)\n ^\n File \"/usr/lib/python3/dist-packages/uaclient/cli/__init__.py\", line 1104, in action_status\nstatus_dict, ret = actions.status(\n ^^^\n File \"/usr/lib/python3/dist-packages/uaclient/actions.py\", line 292, in status\nstatus = ua_status.status(cfg=cfg, show_all=show_all)\n \n File \"/usr/lib/python3/dist-packages/uaclient/status.py\", line 384, in status\nresponse = _attached_status(cfg)\n ^\n File \"/usr/lib/python3/dist-packages/uaclient/status.py\", line 271, in _attached_status\n_attached_service_status(ent, inapplicable_resources, cfg)\n File \"/usr/lib/python3/dist-packages/uaclient/status.py\", line 172, in _attached_service_status\nent_status, details = ent.user_facing_status()\n \n File \"/usr/lib/python3/dist-packages/uaclient/entitlements/base.py\", line 1161, in user_facing_status\napplication_status, explanation = self.application_status()\n ^\n File \"/usr/lib/python3/dist-packages/uaclient/entitlements/repo.py\", line 385, in application_status\npolicy = apt.get_apt_cache_policy(error_msg=messages.APT_POLICY_FAILED)\n ^^\n File \"/usr/lib/python3/dist-packages/uaclient/apt.py\", line 254, in get_apt_cache_policy\nreturn run_apt_command(\n \n File \"/usr/lib/python3/dist-packages/uaclient/apt.py\", line 223, in run_apt_command\nout, _err = system.subp(\n \n File \"/usr/lib/python3/dist-packages/uaclient/system.py\", line 721, in subp\nout, err = _subp(\n ^^\n
[Bug 2067922] Re: on WSL systemd status fails output
I've been able to reproduce the problem on Ubuntu WSL 24.04 with systemd 255.4-1ubuntu8.1. I verified that version 255.4-1ubuntu8.2 fixes it. u@drenec:~$ systemctl status ● drenec State: running Units: 359 loaded (incl. loaded aliases) Jobs: 0 queued Failed: 0 units Since: Mon 2024-07-08 09:41:07 CEST; 1h 1min ago systemd: 255.4-1ubuntu8.2 Tainted: cgroupsv1 CGroup: / ├─init.scope │ ├─ 1 /sbin/init │ ├─ 2 /init │ ├─ 6 plan9 --control-socket 6 --log-level 4 --server-fd 7 --pipe-fd 9 --log-truncate │ ├─325 /init │ ├─326 /init │ ├─327 -bash │ ├─546 systemctl status │ └─547 less Marking as verification-done. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067922 Title: on WSL systemd status fails output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060769] Re: pro-client execs `apt list --installed` instead of using python3-apt - leading to utf-8 errors
** Tags added: wsl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060769 Title: pro-client execs `apt list --installed` instead of using python3-apt - leading to utf-8 errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069739] Re: pro status fails with utf-8 decode error
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069739 Title: pro status fails with utf-8 decode error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2069739/+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
@Steve, thanks for the first part of your review. Can you provide the rest of your review so we can do a single upload that addresses all your comments? -- 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 2064280] Re: Hyperv desktop images no longer building in Noble
I tested this build: https://people.canonical.com/~jchittum/hyperv-desktop-2404/ Produced by CPC following thesesteps: * downloaded the source from proposed * used bartender to build: * $ bartender --livecd-rootfs-dir ./livecd-rootfs-24.04.71/ --build-provider multipass -- --series noble --project ubuntu --image-target all --subproject desktop-preinstalled I installed it successfully in Hyper-V. I went through oem-config, the desktop environment started. I could update and install package. The machine also rebooted successfully. Marking as verification-done. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067922] Re: on WSL systemd status fails output
debdiff with patch applied ** Patch added: "systemd_255.4-1ubuntu8_255.4-1ubuntu9.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067922/+attachment/5786232/+files/systemd_255.4-1ubuntu8_255.4-1ubuntu9.debdiff ** Changed in: systemd (Ubuntu Noble) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu Noble) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067922 Title: on WSL systemd status fails output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067922] Re: on WSL systemd status fails output
upstream patch ** Patch added: "8e57759d6d80ef772d8e17a4559a6797e09af93a.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067922/+attachment/5786231/+files/8e57759d6d80ef772d8e17a4559a6797e09af93a.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067922 Title: on WSL systemd status fails output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067922] [NEW] on WSL systemd status fails output
Public bug reported: WSL 24.04 / systemd 255.4-1ubuntu8 * Upstream report: https://github.com/microsoft/WSL/issues/8879 * Upstream PR: https://github.com/systemd/systemd/pull/32534 * Upstream commit: https://github.com/systemd/systemd-stable/commit/8e57759d6d80ef772d8e17a4559a6797e09af93a.patch In WSL, the cgroup.procs PID list for some reason contain a ton of zeros everywhere from unmapped PIDs. Whenever cg_read_pid encounters such a zero, it throws an error. This makes systemd near unusable inside of WSL. # Test Case install Ubuntu WSL 24.04 from the MS STore. This version has systemd already enabled. ## Expected Behavior systemctl status command to work ## Actual Behavior toor@XPS:~$ systemctl status Failed to dump process list for 'XPS', ignoring: Input/output error ● XPS State: degraded Units: 318 loaded (incl. loaded aliases) Jobs: 0 queued Failed: 1 units Since: Sat 2022-09-24 08:43:15 PDT; 14min ago systemd: 251.4-1ubuntu6 Tainted: cgroupsv1 CGroup: / ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: systemd (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/2067922 Title: on WSL systemd status fails output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064280] Re: Hyperv desktop images no longer building in Noble
I verified the Oracular image and it installs, boots and the user session runs successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024377] Re: Adsys can't fetch GPOs
@Joe and all, the master SRU bug is https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756. It is being processed by the SRU team and should be released to 22.04 at some point but unfortunately I don't have an ETA. You can follow the progress on the aforementioned issue number. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024377 Title: Adsys can't fetch GPOs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2024377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 281232] Re: apt-get dist-upgrade shouldn't run when asked to upgrade between two releases
I'd like to reopen this issue. 16 years later, there are still plenty of *informed* users who change their sources.list, run a dist-upgrade to upgrade the release, and break their system. They then come to the desktop team asking for help to rescue their broken system. Even if we don't block them completely, apt should display a bit fat warning informing the users that what they are going to do is definitely not recommended, are they sure they want to proceed with the dist- upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/281232 Title: apt-get dist-upgrade shouldn't run when asked to upgrade between two releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/281232/+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
Yes, the package is ready to upload to Mantic, and it is strictly the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
We plan to SRU the stack to Mantic and align all the supported releases on the same version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Also affects: adsys (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: golang-1.22 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: adsys (Ubuntu Mantic) Status: New => Confirmed ** Changed in: golang-1.22 (Ubuntu Mantic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049061] Re: adsysctl update with a domain user fails if KRB5CCNAME is not set
Hi Timo, We plan to do a release of ADSys from 24.04 to 22.04 which contains much more than this bug and we'll cover the testing of the entirety of the package. Master SRU bug https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756 We'll send the exception request in the coming days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049061 Title: adsysctl update with a domain user fails if KRB5CCNAME is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) * Note: Both are currently in the new queue of 22.04 : https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&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 2062557] Re: [FFe] add trace-cmd to standand seed
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062557 Title: [FFe] add trace-cmd to standand seed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/2062557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062564] Re: [FFe] Seed pemmican
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062564 Title: [FFe] Seed pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: + * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) - * Note: Both are currently in the new queue of 22.04 : https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&queue_text= + * 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
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Changed in: adsys (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] [NEW] [SRU] adsys 0.14.1
Public bug reported: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version ** Affects: adsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. + Version 0.14.1 is available for 22.04 in a PPA and already used in + production by customers. + [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues - Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ + Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] - Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog - * New features -* New policies: - - Add mount / network shares policy manager - - Add AppArmor policy manager - - Support multiple AD backends and implement Winbind support - - Add system proxy policy manager - - Add certificate policy manager for machines - - Add adsysctl policy purge command to purge applied policies - - Full documentation - - Full end to end automated test suite. + Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog + * New features + * New policies: + - Add mount / network shares policy manager + - Add AppArmor policy manager + - Support multiple AD backends and implement Winbind support + - Add system proxy policy manager + - Add certificate policy manager for machines + - Add adsysctl policy purge command to purge applied policies + - Full documentation + - Full end to end automated test suite. - * Enhancements - * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine - * Expose Ubuntu Pro status in the "status" command - * Update scripts manager creation - * List Pro policy types in service status output - * Warn when Pro-only rules are configured - * Use systemd via D-Bus instead of systemctl commands - * Add placeholder notes for entry types - * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos - * Rework policy application sync strategy - * Print logs when policies are up to date - * Update policy definitions to include dconf key for dark mode background - * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) - * Allow sssd backend to work without ad_domain being set (LP: #2054445) - * Update apport hook to include journal errors and package logs + * Enhancements + * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine + * Expose Ubuntu Pro status in the "status" command + * Update scripts manager creation + * List Pro policy types in service status output + * Warn when Pro-only rules are configured + * Use systemd via D-Bus instead of systemctl commands + * Add placeholder notes for entry types + * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos + * Rework policy application sync strategy + * Print logs when policies are up to date + * Update policy definitions to include dconf key for dark mode background + * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) + * Allow sssd backend to work without ad_domain being set (LP: #2054445) + * Update apport hook to include journal errors and package logs - * Bug fixes - * Fix policy update failing when GPT.INI contains no version key - * Fix object lookup for users having a FQDN as their hostname - * Support special characters in domains when parsing sssd configuration - * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf - * Ensure empty state for dconf policy - * Handle case mismatches in GPT.INI file name - * Ensure GPO URLs contain the FQDN of the domain contro
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) [test plan] # Process - Adsys follows a robust continuous integration and testing process. It is covered by a comprehensive automated tests suite (https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated end to end test suite that runs in a real active directory environment. + Adsys follows a robust continuous integration and testing process. It is covered by a comprehensive automated tests suite (https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated end to end test suite that runs in a real active directory
[Bug 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) + * Note: Both are currently in the new queue of 22.04 : https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&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 quality criteria: * All cha
[Bug 2043376] Re: adsys cant fetch gpos ubuntu 22.04.3
** Changed in: adsys (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043376 Title: adsys cant fetch gpos ubuntu 22.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2043376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055300] Re: DEP8 failures in noble/armhf with samba 4.19.5
There is a passing run with samba/2:4.19.5+dfsg-1ubuntu1 This could be a flaky test on armhf. I'm closing this report for now and will look further if it becomes a blocker on this arch in the futur. ** Changed in: adsys (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055300 Title: DEP8 failures in noble/armhf with samba 4.19.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2055300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055300] Re: DEP8 failures in noble/armhf with samba 4.19.5
** Changed in: adsys (Ubuntu) Assignee: (unassigned) => Gabriel Nagy (gabuscus) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055300 Title: DEP8 failures in noble/armhf with samba 4.19.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2055300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929038] Re: [SRU] Backport to 20.04 LTS
It's a desktop package that we do not need on riscv64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958668] Re: Do not propose to reboot on WSL
** Changed in: update-manager (Ubuntu) Status: New => Triaged ** Changed in: update-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958668 Title: Do not propose to reboot on WSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1958668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929038] Re: [SRU] Backport to 20.04 LTS
This has been verified a while ago and already deployed in production for customers. Marking as verification-done. ** Tags removed: removal-candidate verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968150] [NEW] [FFe] Remove zsys from installer
Public bug reported: Zsys is in very low maintenance mode (critical bug fixes only) and must be removed from the LTS. However ZFS and encrypted ZFS are still available as an installation option but the package ZSys is not installed. The ZFS layout remains unchanged. https://git.launchpad.net/ubiquity/commit/?id=76e7718dbdd9dde7a7609f754cf8719469bbf0e5 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Description changed: Zsys is in very low maintenance mode (critical bug fixes only) and must be removed from the LTS. However ZFS and encrypted ZFS are still available as an installation option but the package ZSys is not installed. The ZFS layout remains unchanged. + + https://git.launchpad.net/ubiquity/commit/?id=76e7718dbdd9dde7a7609f754cf8719469bbf0e5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968150 Title: [FFe] Remove zsys from installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1968150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)
** Changed in: zsys (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967585 Title: Failed to start ZSYS daemon service (panic: runtime error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1967585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)
A pool compatibility property has been added to ZFS 2.1 but not to the go binding. ** Changed in: zsys (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967585 Title: Failed to start ZSYS daemon service (panic: runtime error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1967585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session in virt-manager with QXL
** Summary changed: - Jammy fails to boot to live session + Jammy fails to boot to live session in virt-manager with QXL ** Description changed: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. There are crashes of gnome-shell and xorg in /var/crash. - From the journal + From the journal avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 ip 7fa1ca256f44 sp 7fff16f7c2a0 error 4 in libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000] avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00 avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission + + + If I switch from QXL to Virtio then it works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session in virt-manager with QXL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "_usr_lib_xorg_Xorg.0.crash" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577348/+files/_usr_lib_xorg_Xorg.0.crash ** Description changed: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. There are crashes of gnome-shell and xorg in /var/crash. + + I'm on Jammy with libvirt 8.0.0-1ubuntu6 and qemu 6.2+dfsg-2ubuntu5 ** Description changed: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. There are crashes of gnome-shell and xorg in /var/crash. - I'm on Jammy with libvirt 8.0.0-1ubuntu6 and qemu 6.2+dfsg-2ubuntu5 + From the journal + avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 ip 7fa1ca256f44 sp 7fff16f7c2a0 error 4 in libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000] + avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00 + avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "_usr_bin_gnome-shell.999.crash" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577347/+files/_usr_bin_gnome-shell.999.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577346/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "debug" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577344/+files/debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] Re: Jammy fails to boot to live session
** Attachment added: "dm" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577345/+files/dm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967901] [NEW] Jammy fails to boot to live session
Public bug reported: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. There are crashes of gnome-shell and xorg in /var/crash. From the journal avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 ip 7fa1ca256f44 sp 7fff16f7c2a0 error 4 in libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000] avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00 avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: Jammy fails to boot to live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966818] Re: zsys crashing on snap mounts
*** This bug is a duplicate of bug 1967585 *** https://bugs.launchpad.net/bugs/1967585 ** This bug has been marked a duplicate of bug 1967585 Failed to start ZSYS daemon service (panic: runtime error) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966818 Title: zsys crashing on snap mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1966818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)
Thanks for your report. Confirmed with 0.5.8build2. Downgrading and pinning to 0.5.8 is the workaround for now. https://launchpad.net/ubuntu/+source/zsys/0.5.8/+build/21362897/+files/zsys_0.5.8_amd64.deb ** Changed in: zsys (Ubuntu) Status: New => Confirmed ** Changed in: zsys (Ubuntu) Importance: Undecided => Critical ** Changed in: zsys (Ubuntu) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) ** Changed in: zsys (Ubuntu) Milestone: None => ubuntu-22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967585 Title: Failed to start ZSYS daemon service (panic: runtime error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1967585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929201] Re: Packages in PPA are not installed if version higher than in a release pocket
I confirm that adding XB-Task addresses the issue and the package from the PPA is installed. However, when there is no task defined, the package from archive should be installed. ** Changed in: livecd-rootfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929201 Title: Packages in PPA are not installed if version higher than in a release pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1929201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964325] [NEW] Fails to print due to apparmor denied connect operation for cupsd - /run/systemd/userdb/io.systemd.Machine
Public bug reported: On an up to date Jammy machine, printing fails and there is the following apparmor denied message in the journal: apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd" name="/run/systemd/userdb/io.systemd.Machine" pid=892182 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 Printing works after running aa-complain cupsd. The printer is a driverless HP Envy 5020 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apparmor 3.0.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 10:25:10 2022 InstallationDate: Installed on 2020-05-31 (647 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) ProcKernelCmdline: BOOT_IMAGE=/BOOT/ubuntu_nt06gx@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_nt06gx ro snd-intel-dspcfg.dsp_driver=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy rls-jj-incoming ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964325 Title: Fails to print due to apparmor denied connect operation for cupsd - /run/systemd/userdb/io.systemd.Machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1964325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936907] Re: [MIR] ADSys
** Description changed: [Availability] Available on all archs, available starting hirsute. It will be backported to Focal once an FFe has been accepted. [Rationale] We are supporting GPO Active Directory support on ubuntu starting hirsute. This features allows for an administrator to configure their Active Directory server to deploy per-machine and per-user configurations, enforce rules and other domain policies. - Right now, dconf keys are supported. + Right now, dconf keys, sudo administration rights and computer and user + scripts are supported. This feature is built and use the krb5 tickets which are provided by SSSD. Basically: - SSSD is dealing with user and machine registration/authentification and enforce password policies - ADSys is handling GPO enforcement and support. The Ubuntu specific policies needs to be installed on the Active Directory server (they are contained in the daemon). [Security] The daemon is started is running as a root user to be able to enforce machine policies, like rebuilding dconf databases, setting profiles. User only interacts with the client side (both sides communicates over GRPC), which can be ran as any user. Polkit is used to restrain access to some part of the API. There is a PAM module to build on demand per-user policy once authenticated with SSSD. They are rejected if the authentication or not all affected policies could be downloaded. [Quality assurance] Joining a domain in the ubiquity desktop installer makes the machine joining the AD domain and install adsys functionality. The package will be seeded directly on the desktop ISO. - An extensive testsuite (more than 700) is included and available as + An extensive testsuite (more than 1k) is included and available as autopkgtests for rdepends. The whole stack is tested (even the client/daemon interaction) and coverage is measured (including in the small python script). However, tests with a real Active Directory server can only be done manually as there is no setup available in the autopkgtests infrastructure. [Dependencies] Main dependencies are libsmbclient, python3 (an embeeded script allows, via samba, connecting to AD LDAP) and SSSD/KRB5. This is a Go package, and all dependencies are vendored, and versions are controlled via go.mod. We are using dependabot (from Github) to automatically get notified of any dependencies updates (and security issues), which opens a PR, rebuild and run all tests to report it there. We are thus able to quickly merge them. [Standards compliance] Standard debhelper packaging, including a systemd service. [Maintenance] The desktop team will maintain it. * we commit to test no-change-rebuilds triggered by a dependent library/compiler and to fix any issues found for the lifetime of the release (including ESM when included) * we will provide timely testing of no-change-rebuilds from the security team, fixing the rebuilt package as necessary * we commit to provide updates to the security team for any affected vendored code for the lifetime of the release (including ESM when included) * we will provide timely, high quality updates for the security team to sponsor to fix issues in the affected vendored code - [Background information] ADSys is composed of: - a daemon, named adsysd, running as root. This one will shutdown after a period of inactivity without any active request. It is socket activated. - a client, named adsysctl (which is a symlink to adsysd and only differ behavior from its executable name), which is running as the user (or root on boot for machine update). This ones optionally wakes up adsysd, connect through an Unix socket with SO_PEERCRED to communicate current user running the process. We are using grpc to communicate between the client and service. Each client request is validated through polkit, matching user name and permissions. The daemon will reject any unauthorized client connections. Note that all actions are always performed from executing the client, even the scheduled one by a cron. - The daemon contains a python embeeded script to reuse samba utilities to - connect with GSSAPI to the AD LDAP server and list available GPOs. GPOs - are then downloaded in a cache directory which isn’t accessible to + The daemon contains a python embedded script that uses samba utilities + to connect with GSSAPI to the AD LDAP server and list available GPOs. + GPOs are then downloaded in a cache directory which isn’t accessible to users. The daemon also contains all GPOs policies to install on the Active Directory side to reflect them in the UI. This could be accessed online or dumped directly via the command line tool. Finally, those are automatically refreshed for any supported LTSes and intermediate versions. The availability of features can be different cross-releas
[Bug 1959667] [NEW] non informative error message when enabling a non available UA service
Public bug reported: Jammy / software-properties-gtk: Installed: 0.99.17 When trying to enable a service that is not available the error message provide no useful information about what went wrong (cf screenshot) and in the journal: ubuntu-advantag[1461382]: Failed to parse UA status: Operation was cancelled In both cases the error message should be similar to UA CLI: UA Infra: ESM is not available for Ubuntu 22.04 (Jammy Jellyfish). ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2022-02-01_12-06.png" https://bugs.launchpad.net/bugs/1959667/+attachment/5558588/+files/2022-02-01_12-06.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959667 Title: non informative error message when enabling a non available UA service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958668] [NEW] Do not propose to reboot on WSL
Public bug reported: On WSL, at the end of a do-release-upgrade, the upgrader proposes to reboot the machine. Although on WSL it is not possible to reboot due to the lack of systemd and it ends with an error. The message at the end should be different if it is running on a system where systemd is not available or specifically on WSL and do not propose a reboot but to manually shutdown and restart the instance. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958668 Title: Do not propose to reboot on WSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1958668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952999] Re: Wayland blocks the microphone of the webcam
Yes, it works perfectly with Xorg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952999 Title: Wayland blocks the microphone of the webcam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1952999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952999] [NEW] Wayland blocks the microphone of the webcam
Public bug reported: Jammy daily In the wayland session the microphone of the webcam is no available. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.19.0-2build1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 2 07:45:44 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2081] InstallationDate: Installed on 2020-05-31 (549 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_nt06gx@/vmlinuz-5.13.0-20-generic root=ZFS=rpool/ROOT/ubuntu_nt06gx ro snd-intel-dspcfg.dsp_driver=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:br5.16:efr3.4:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:skuBXNUC10i7FNH:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy reproducible rls-jj-incoming single-occurrence ubuntu wayland-session ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952999 Title: Wayland blocks the microphone of the webcam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1952999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952457] Re: choosing Ubuntu on xorg fails to launch X, launches Wayland
There is no crash and this is on hardware. ** Tags added: rls-jj-incoming ** Attachment added: "journal.txt.gz" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1952457/+attachment/5544826/+files/journal.txt.gz ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952457 Title: choosing Ubuntu on xorg fails to launch X, launches Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1952457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952930] Re: Xorg session doesn't stick
** Attachment added: "journal.txt.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1952930/+attachment/5544680/+files/journal.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952930 Title: Xorg session doesn't stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1952930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952930] [NEW] Xorg session doesn't stick
Public bug reported: Jammy daily. *Test Case* 1. Boot to GDM 2. Select an Xorg Session 3. Login 4. Verify that Xorg is running 5. Reboot the machine 6. Check that Xorg session is still selected 7. Login 8. Verify that Xorg is running *Actual result* Wayland is running despite Xorg was preselected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-session 40.1.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 16:28:37 2021 InstallationDate: Installed on 2020-05-31 (549 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy rls-jj-incoming wayland-session ** Tags added: rls-jj-incomping ** Tags removed: rls-jj-incomping ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952930 Title: Xorg session doesn't stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1952930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
Verification Mesa 21.0.3-0ubuntu0.3~20.04.4 has been tested on 2 systems and it fixes the issue. Marking as verification-done. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Changed in: mesa (Ubuntu Focal) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. + + [What could go wrong] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] + On Windows 11 with WSLg and Ubuntu 20.04 + 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] + 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu + 2. Install and launch chrome, edge or vscode + 3. Resize the windows repeatedly + + Verification: + The app must not crash or hang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. + + [Test Case] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950174] [NEW] [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
Public bug reported: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mesa (Ubuntu Focal) Importance: High Status: Triaged ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: [Description] - This is a request to backport this fix to focal-updates which is affecting users of WSL: + This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: mesa (Ubuntu Focal) Status: New => Triaged ** Changed in: mesa (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926267] Re: do-release-upgrade failed silently after failed to connect to snap service
** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute) Status: Confirmed => Won't Fix ** Changed in: ubuntu-release-upgrader (Ubuntu Impish) Status: Confirmed => Triaged ** Changed in: ubuntu-release-upgrader (Ubuntu Impish) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926267 Title: do-release-upgrade failed silently after failed to connect to snap service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
I've this issue too. What else do you need than @Mario's journal? ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Also affects: gdm3 (Ubuntu Impish) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
There is also an additional requirement. The package must install successfully and replace an existing file that would have been created manually (we had to ship the file on the image for the customer since we don't have this fix in a package yet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
IMHO having the fix in network-dispatcher makes more sense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
@Seb this fix has to go to focal for a customer project and must land in the dev release first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
The server is set via a configuration file. The default config file is /etc/systemd/timesyncd.conf and it can be overridden by dropping files in /etc/systemd/timesyncd.conf.d/. There is a pool of free ntp servers available on https://www.ntppool.org/en/. To test this fix you also need a DHCP server that returns NTP records. With VMs, you can use dnsmasq to provide NTP records by changing the values in dnsmasq.conf # Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5 #dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5 Or if you're using libvirt, edit the configuration with "virsh net-edit default" (or the name of the network your VMs are attached to) then pass the option directly to dnsmasq (cf https://libvirt.org/formatnetwork.html for reference) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940925] [NEW] Do not activate spread view on first boot
Public bug reported: On first boot the spread view shows the first boot wizard and it looks really weird. Moreover if you click on the right workspace the wizard is not displayed. The spread view should be disabled and the wizard should be displayed full screen immediately. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 24 12:41:16 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-31 (450 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "Screenshot from 2021-08-24 12-39-28.png" https://bugs.launchpad.net/bugs/1940925/+attachment/5520159/+files/Screenshot%20from%202021-08-24%2012-39-28.png ** Description changed: On first boot the spread view shows the first boot wizard and it looks - really weird. The spread view should be disable and the wizard should be - displayed full screen immediately. + really weird. Moreover if you click on the right workspace the wizard is + not displayed. + + The spread view should be disabled and the wizard should be displayed + full screen immediately. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 24 12:41:16 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-31 (450 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940925 Title: Do not activate spread view on first boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
** Also affects: network-manager (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Focal) Importance: Undecided => High ** Changed in: network-manager (Ubuntu Focal) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940826] Re: customisation steps do not work for 20.04
** Package changed: ubiquity (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940826 Title: customisation steps do not work for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1940826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940822] [NEW] This is a test
Public bug reported: This is a test ** Affects: ubuntu Importance: Undecided Status: Invalid ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940822 Title: This is a test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1940822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940657] Re: Cannot type in address bar nor page content in live session
Thanks for your report. Could you please describe your testing environment (VM vs HW, HW configuration, ...) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940657 Title: Cannot type in address bar nor page content in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921091] Re: [SRU] New feature: Encryption recovery key
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921091 Title: [SRU] New feature: Encryption recovery key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921091] Re: [SRU] New feature: Encryption recovery key
I verified ubiquity 20.04.15.17 in both automated and manual partitioning and it works as expected. Marking as verification done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921091 Title: [SRU] New feature: Encryption recovery key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928860] Re: Recovery key is low-entropy
ubiquity (21.10.4) impish; urgency=medium [ Didier Roche ] [ Jean-Baptiste Lallement ] * Make the recovery key a 48 digits password by default (LP: 1928860) * Recovery key is editable and optional. * Show the recovery key during manual partitioning. * Display a warning if recovery key is stored on a non removable media. ** Changed in: ubiquity (Ubuntu Impish) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928860 Title: Recovery key is low-entropy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1928860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921091] Re: [SRU] New feature: Encryption recovery key
This patch is missing in scripts/plugininstall.py from focal and the install crashes in manual mode partitioning mode: disk = debconf_disk.split('/')[-1].replace('=', '/') if not disk: # disk is not set in manual partitioning mode syslog.syslog( syslog.LOG_ERR, 'Determining installation disk failed. ' 'Setting a recovery key is supported only with partman-auto.') self.clean_crypto_keys() self.db.input('critical', 'ubiquity/install/broken_luks_add_key') self.db.go() return ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-failed verification-failed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921091 Title: [SRU] New feature: Encryption recovery key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921091] Re: [SRU] New feature: Encryption recovery key
pushed to focal branch https://git.launchpad.net/ubiquity/commit/?h=focal&id=b88f5121758599b5f412c56aabe67b22e5e2f586 ** Changed in: ubiquity (Ubuntu Focal) Status: New => In Progress ** Changed in: ubiquity (Ubuntu Focal) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) ** Changed in: ubiquity (Ubuntu Focal) Milestone: None => ubuntu-20.04.3 ** Changed in: ubiquity (Ubuntu Focal) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921091 Title: [SRU] New feature: Encryption recovery key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936488] [NEW] Ubiquity fails to build with GTK4
Public bug reported: With latest updates applied on impish Ubiquity fails to build with: make: Leaving directory '/home/j-lallement/shared/Ubuntu/Dev/ubiquity/src' /home/j-lallement/shared/Ubuntu/Dev/ubiquity/tests/test_gtkwidgets.py:9: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '4.0') before import to ensure that the right version gets loaded. from gi.repository import Gtk, TimezoneMap /home/j-lallement/shared/Ubuntu/Dev/ubiquity/tests/test_usersetup.py:6: PyGIWarning: UbiquityMockResolver was imported without specifying a version first. Use gi.require_version('UbiquityMockResolver', '1.0') before import to ensure that the right version gets loaded. from gi.repository import UbiquityMockResolver Traceback (most recent call last): File "/home/j-lallement/shared/Ubuntu/Dev/ubiquity/./tests/run", line 121, in suite = unittest.TestLoader().loadTestsFromNames(tests) File "/usr/lib/python3.9/unittest/loader.py", line 220, in loadTestsFromNames suites = [self.loadTestsFromName(name, module) for name in names] File "/usr/lib/python3.9/unittest/loader.py", line 220, in suites = [self.loadTestsFromName(name, module) for name in names] File "/usr/lib/python3.9/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) File "/home/j-lallement/shared/Ubuntu/Dev/ubiquity/tests/test_usersetup.py", line 9, in from ubiquity import gtkwidgets, plugin_manager File "/home/j-lallement/shared/Ubuntu/Dev/ubiquity/./ubiquity/gtkwidgets.py", line 38, in class StylizedFrame(Gtk.Alignment): File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 32, in __getattr__ return getattr(self._introspection_module, name) File "/usr/lib/python3/dist-packages/gi/module.py", line 123, in __getattr__ raise AttributeError("%r object has no attribute %r" % ( AttributeError: 'gi.repository.Gtk' object has no attribute 'Alignment' It should be fixed by setting the version of GTK to 3 ** Affects: ubiquity (Ubuntu) Importance: Critical Status: New ** Tags: rls-ii-incoming ** Changed in: ubiquity (Ubuntu) Importance: Undecided => High ** Changed in: ubiquity (Ubuntu) Importance: High => Critical ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936488 Title: Ubiquity fails to build with GTK4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1936488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935818] Re: Black screen if PAM session fails to initialize completely
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: gdm3 (Ubuntu Focal) Assignee: Jean-Baptiste Lallement (jibel) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935818 Title: Black screen if PAM session fails to initialize completely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1935818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs