[Touch-packages] [Bug 2059796] Re: Other Software > Remove button doesn't work
This looks like a good fix to have for 24.04 release but does not look beta-critical. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2059796 Title: Other Software > Remove button doesn't work Status in software-properties package in Ubuntu: Fix Committed Bug description: Test Case - - Add a PPA with apt-add-repository, not with software-properties (we want a deb822 format for the test). - Open the Software & Updates tab - Switch to the Other Software tab - Select the PPA line and click Remove - After Authentication, nothing happens. No error is emitted to the command line. The repo line still shows. The repo is still in /etc/apt/sources.list.d/ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-gtk 0.99.44 ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1 Uname: Linux 6.8.0-20-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 12:06:07 2024 InstallationDate: Installed on 2022-04-06 (723 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2023-12-09 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1
** Changed in: c2esp (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: Fix Committed Status in cups package in Ubuntu: Fix Released Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd
** Changed in: c2esp (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059281 Title: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd Status in c2esp package in Ubuntu: Invalid Status in cups package in Ubuntu: Fix Released Bug description: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060062] Re: libpam0g-dev cannot be installed
The noble release pocket is currently in an inconsistent state because of rebuilds for CVE-2024-3094. This is not a bug in the pam package. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094 ** Changed in: pam (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2060062 Title: libpam0g-dev cannot be installed Status in pam package in Ubuntu: Invalid Bug description: When trying to install libpam0g-dev on noble numbat, I get the following output: The following packages have unmet dependencies: libpam0g-dev : Depends: libpam0g (= 1.5.2-9.1ubuntu3) but 1.5.3-5ubuntu3 is to be installed E: Unable to correct problems, you have held broken packages. I have a nightly build from a few days ago, but have been keeping it up to date with the latest packages via apt full-upgrade. LSB release output: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Noble Numbat (development branch) Release: 24.04 Codename: noble ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam0g-dev (not installed) ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 13:13:31 2024 InstallationDate: Installed on 2024-03-26 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2060062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986542] Re: Issue building the debian source archive
Since this bug report was filed, there has been a security update of gst-plugins-good1.0 in jammy which built successfully. Closing invalid. ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1986542 Title: Issue building the debian source archive Status in gst-plugins-good1.0 package in Ubuntu: Invalid Bug description: I cannot build the ubuntu source package gst-plugins- good1.0_1.20.3-0ubuntu1.dsc. I am doing: > dget -q http://archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gst-plugins-good1.0_1.20.3-0ubuntu1.dsc > cd gst-plugins-good1.0-1.20.3/ > DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -d -nc -b and I receive the error: ../gst-libs/gst/basecamerabinsrc/meson.build:28:3: ERROR: Unknown variable "static_build". I am testing inside of an ubuntu:jammy-20220801 container. I have narrowed the issue down to a patch in the changelog on the 15th Mar which states "Import plugins from -bad that are needed for main applications". This patch imports some "bad" plugins into the source but the meson file isn't setup correctly for this to work. Manually removing the patches related to the bad plugins fixed the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1986542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026885] Re: nano is not available on i386
packages are provided on i386 only if they are required for binary compatibility. ** Changed in: nano (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/2026885 Title: nano is not available on i386 Status in nano package in Ubuntu: Won't Fix Bug description: There is no i386 Nano package in Jammy. I used Nano all the time including in chroots, which is where this reared its ugly head. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/2026885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058242] Re: Demote isc-dhcp to universe
anyway, this doesn't need an ubuntu-archive bug, it just needs the dependency removed. ** Package changed: isc-dhcp (Ubuntu) => avahi (Ubuntu) ** Changed in: avahi (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/2058242 Title: Demote isc-dhcp to universe Status in avahi package in Ubuntu: Triaged Bug description: Following the replacement of dhclient by dhcpcd as new DHCP client tool, it is now time to demote isc-dhcp-client. After demoting isc- dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted. ``` $ reverse-depends -c main,restricted isc-dhcp-client $ reverse-depends -c main,restricted -b isc-dhcp-client ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2058242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058242] Re: Demote isc-dhcp to universe
avahi-autoipd still depends on it. But I was sure I uploaded avahi to drop it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2058242 Title: Demote isc-dhcp to universe Status in avahi package in Ubuntu: Triaged Bug description: Following the replacement of dhclient by dhcpcd as new DHCP client tool, it is now time to demote isc-dhcp-client. After demoting isc- dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted. ``` $ reverse-depends -c main,restricted isc-dhcp-client $ reverse-depends -c main,restricted -b isc-dhcp-client ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2058242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1
c2esp autopkgtest still fails with the current cups in noble-proposed - though it appears to fail differently now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: New Status in cups package in Ubuntu: Fix Committed Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058769] Re: proposed-migration for click 0.5.2-2
** Description changed: - click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on ppc64el, - s390x. + click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on all archs + except amd64. In order to be able to run the tests without all-proposed=1, glib 2.0 is needed, which is why I marked it as affected. Excerpt of the test logs: ERROR: test_list_simple (click_package.tests.integration.test_list.TestList.test_list_simple) -- Traceback (most recent call last): - File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py", line 29, in test_list_simple - self.click_install(path_to_click, name, user) - File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py", line 99, in click_install - subprocess.check_call(cmd) - File "/usr/lib/python3.12/subprocess.py", line 413, in check_call - raise CalledProcessError(retcode, cmd) + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py", line 29, in test_list_simple + self.click_install(path_to_click, name, user) + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py", line 99, in click_install + subprocess.check_call(cmd) + File "/usr/lib/python3.12/subprocess.py", line 413, in check_call + raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '--allow-unauthenticated', '/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit status 1. == ERROR: test_debsig_install_valid_signature (click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature) -- Traceback (most recent call last): - File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 207, in test_debsig_install_valid_signature - subprocess.check_call( - File "/usr/lib/python3.12/subprocess.py", line 413, in check_call - raise CalledProcessError(retcode, cmd) + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 207, in test_debsig_install_valid_signature + subprocess.check_call( + File "/usr/lib/python3.12/subprocess.py", line 413, in check_call + raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '/tmp/tmpymtfsjg9/org.example.debsig-valid-sig_1.0_all.click']' returned non-zero exit status 1. == ERROR: test_debsig_install_can_install_with_sig_override (click_package.tests.integration.test_signatures.TestSignatureVerificationNoSignature.test_debsig_install_can_install_with_sig_override) -- Traceback (most recent call last): - File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 164, in test_debsig_install_can_install_with_sig_override - subprocess.check_call( - File "/usr/lib/python3.12/subprocess.py", line 413, in check_call - raise CalledProcessError(retcode, cmd) + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 164, in test_debsig_install_can_install_with_sig_override + subprocess.check_call( + File "/usr/lib/python3.12/subprocess.py", line 413, in check_call + raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--allow-unauthenticated', '--user=root', '/tmp/tmpheysy9ze/org.example.debsig-no-sig_1.0_all.click']' returned non-zero exit status 1. ** Changed in: glib2.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2058769 Title: proposed-migration for click 0.5.2-2 Status in click package in Ubuntu: New Status in glib2.0 package in Ubuntu: Invalid Bug description: click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on all archs except amd64. In order to be able to run the tests without all-proposed=1, glib 2.0 is needed, which is why I marked it as affected. Excerpt of the test logs: ERROR: test_list_simple (click_package.tests.integration.test_list.TestList.test_list_simple) -- Traceback (most recent call last): File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py", line 29, in test_list_simple
[Touch-packages] [Bug 2059157] [NEW] proposed-migration for cups 2.4.7-1.2ubuntu1
Public bug reported: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. ** Affects: c2esp (Ubuntu) Importance: Critical Status: New ** Affects: cups (Ubuntu) Importance: Critical Status: New ** Tags: time-t update-excuse ** Description changed: - cups 2.4.7-1.2ubuntu1 is stuck in -proposed. + multiple cups-related packages are having test failures on armhf after time_t transition. + https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf + https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 + + I am suspecting a common cups-based issue. + + cups-browsed already has a separate bug open at + https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. ** Tags added: time-t ** Changed in: cups (Ubuntu) Importance: Undecided => Critical ** Also affects: c2esp (Ubuntu) Importance: Undecided Status: New ** Changed in: c2esp (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1
marking critical because these packages are being allowed into the release pocket as-is but the printing stack may be broken, which is of high importance in a server/embedded context. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
privoxy rebuild fails in containers with the same issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: Invalid Status in cups-browsed package in Ubuntu: Fix Released Status in privoxy package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
Thanks! Since this issue was seen only with the package in -proposed, I'm closing this bug. There are other unrelated test failures now blocking the build on armhf. I will open a separate bug for these. ** Changed in: cups-browsed (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: apparmor (Ubuntu) Status: New => Invalid ** Also affects: privoxy (Ubuntu) Importance: Undecided Status: New ** Changed in: privoxy (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: Invalid Status in cups-browsed package in Ubuntu: Fix Released Status in privoxy package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
On Mon, Mar 25, 2024 at 05:16:57AM -, John Johansen wrote:
> Do we know if there is a difference in the kernel between the runs?
> The 2.0.0.0~0ubuntu3 autopackage run log I was pointed at was on a
> Linux 5.4.0-170-generic #188-Ubuntu
> Do we know what kernel that 2.0.0-0ubuntu7 is failing on? There was a
> change to when security checks were made in on the exec path, this
> particular denial makes me wonder if we are seeing an artifact of that
> here.
All logs on https://autopkgtest.ubuntu.com/packages/c/cups-browsed/noble/armhf
should include kernel information.
Latest 2.0.0-0ubuntu8 failure has:
211s autopkgtest [22:10:53]: testbed running kernel: Linux
5.15.0-101-generic #111-Ubuntu SMP Wed Mar 6 18:01:01 UTC 2024
Last successful 2.0.0-0ubuntu3 log has:
349s autopkgtest [18:43:33]: testbed running kernel: Linux
5.4.0-170-generic #188-Ubuntu SMP Wed Jan 10 09:51:10 UTC 2024
But that was a retry of the release version of the package AFTER things
started failing;
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/c/cups-browsed/20240322_173402_07be9@/log.gz
is earlier and has:
351s autopkgtest [17:30:50]: testbed running kernel: Linux
5.4.0-170-generic #188-Ubuntu SMP Wed Jan 10 09:51:10 UTC 2024
so it's not a kernel difference.
It appears to be a genuine change in the binaries when built with new
toolchain that causes them to have a new mmap that wasn't there before?
If I aa-enforce and run strace, I see:
execve("/usr/sbin/cups-browsed", ["cups-browsed"], 0xffa82a54 /* 12 vars
*/) = -1 EACCES (Permission denied)
so this failure happens before we even reach the executable?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2058866
Title:
proposed-migration for cups-browsed 2.0.0-0ubuntu8
Status in apparmor package in Ubuntu:
New
Status in cups-browsed package in Ubuntu:
New
Bug description:
cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
via an autopkgtest), early enough that LD_DEBUG=all gives no output.
A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
executable ran, so 8 was uploaded to try to fix this. But the
executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
browsed and segfaults when invoked as /usr/sbin/cups-browsed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
cupsd 2.0.0-0ubuntu8 contains no sourceful changes vs 2.0.0-0ubuntu3 in noble release; these are no-change rebuilds only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: New Status in cups-browsed package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
Reproducible on amd64. [6037055.006277] audit: type=1400 audit(1711335561.053:35916): apparmor="DENIED" operation="file_mmap" class="file" namespace="root//lxd-noble_" profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed" pid=788055 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100 So this is a regression wrt cups-browsed running under apparmor in a container, and not specific to armhf. ** Changed in: cups-browsed (Ubuntu) Importance: Undecided => Critical ** Changed in: cups-browsed (Ubuntu) Assignee: Steve Langasek (vorlon) => (unassigned) ** Tags added: time-t ** Changed in: apparmor (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: New Status in cups-browsed package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
[1724567.629003] audit: type=1400 audit(1711133926.877:813): apparmor="DENIED" operation="file_mmap" class="file" namespace="root//lxd-noble-armhf_" profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed" pid=876865 comm="cups-browsed" requested_mask="rm" denied_mask="rm" fsuid=1000110 ouid=100 ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: New Status in cups-browsed package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058769] [NEW] proposed-migration for click 0.5.2-2
Public bug reported: click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf, and possibly on all archs. armhf binary will be removed from the release pocket. ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Description changed: - click 0.5.2-2 is stuck in -proposed. + click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf, + and possibly on all archs. + + armhf binary will be removed from the release pocket. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/2058769 Title: proposed-migration for click 0.5.2-2 Status in click package in Ubuntu: New Bug description: click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf, and possibly on all archs. armhf binary will be removed from the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/2058769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058767] Re: proposed-migration for auto-multiple-choice 1.6.0-3build3
mesa bootstrap had not been unwound all the way. Fixed mesa is building now. ** Package changed: auto-multiple-choice (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2058767 Title: proposed-migration for auto-multiple-choice 1.6.0-3build3 Status in mesa package in Ubuntu: Fix Released Bug description: auto-multiple-choice 1.6.0-3build3 is stuck in -proposed due to regressing armhf autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2058767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057822] Re: Removing irqbalance disables power button on Raspberry Pi 5
** Package changed: ubuntu-meta (Ubuntu) => ubuntu-raspi-settings (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2057822 Title: Removing irqbalance disables power button on Raspberry Pi 5 Status in ubuntu-raspi-settings package in Ubuntu: New Bug description: As discussed in Bug #1833322: "Please consider no more having irqbalance enabled by default (per image/use-case/TBD)" (https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322) the irqbalance package will no longer be installed by default in Noble. So as a test I removed the package from my Raspberry Pi 5 running Mantic Server, after which the Pi 5's power button no longer worked to poweroff the system. Re-installing irqbalance caused the button to work again. With irqbalance installed I see these messages at boot time: kernel: input: pwr_button as /devices/platform/pwr_button/input/input1 systemd-logind[694]: Watching system buttons on /dev/input/event0 (pwr_button) Without irqbalance I see this: kernel: gpio-keys pwr_button: Unable to get irq number for GPIO 0, error -6 So the Raspberry Pi 5 might still need irqbalance installed, or perhaps there's a better solution for enabling the button. I have the following appended to the Mantic default /boot/firmware/config.txt: # Trickle charge the RTC battery (default: don't charge) dtparam=rtc_bbat_vchg=300 # Enable the PCIe external connector dtparam=nvme # Force PCIe Gen 3.0 (default: Gen 2.0; not certified for Gen 3.0) # dtparam=pciex1_gen=3 # Enable second serial port on GPIO 14 & 15 (default: disabled) dtparam=uart0 # Change activity LED behavior (default: blink for MMC access) dtparam=act_led_trigger=heartbeat # Disable Bluetooth (not wanted on a server) dtoverlay=disable-bt-pi5 # Enable PPS on GPIO 18 for MAX-M8Q GNSS HAT dtoverlay=pps-gpio,gpiopin=18,capture_clear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2057822/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056496] Re: [FFe] AppArmor 4.0-beta2 + prompting support for noble
FFe granted ** Changed in: apparmor (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2056496 Title: [FFe] AppArmor 4.0-beta2 + prompting support for noble Status in apparmor package in Ubuntu: Triaged Bug description: AppArmor 4.0-beta2 contains fixes that prevented AppArmor 4.0-beta1 from landing pre feature freeze. Landing AppArmor 4.0-beta's will enable us to more easily track upstream bug fixes, and is needed to support network rules in prompting. The addition of the prompting patch on top of AppArmor 4.0 is required to support snapd prompting in general for both file and network rules. Currently the prompting patch is not part of the upstream release but is part of the vendored apparmor in snapd. In ordered for snapd to be able to vendor the noble release of apparmor it requires support for prompting. The prompting patch is a straight rebase to AppArmor 4.0 of the patch that has been in testing in snapd prompting for more than six months. Changes from 4.0.0~alpha4-0ubuntu1 (current noble) version Beta1 added three additional features that were not present in alpha4 (current Noble). • support for fine grained (address based) IPv4 and IPv6 mediation (required for prompting to support networking). • aa-notify support message filters to reduce notifications • aa-logprof/genprof support for mount rules None of these features affect existing policy, which will continue to function under the abi that it was developed under. This can be seen in the regression testing below. I addition to the 3 features introduced in Beta1, Beta1 and Beta2 add several bug fixes the most important are highlighted below with the full list available in the upstream release notes, available at https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_4.0-beta1 and https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_4.0-beta2 • new unconfined profiles in support of unprivileged user namespace mediation https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626 ∘ nautalus, devhelp, element-desktop, epiphany, evolution, keybase, opam • fix policy generation for non-af_inet rules (MR:1175) • Fix race when reading proc files (AABUG:355, MR:1157) • handle unprivileged_userns transition in userns tests (MR:1146) • fix usr-merge failures on exec and regex tests (MR:1146) This proposed change has been tested via the QA Regression Testing project, in particular with the specific test added in https://git.launchpad.net/qa-regression- testing/commit/?id=6f2c5ab7c8659174adac772ce0e894328bb5045d The output of a test run is in the attached qrt.output file. Of which the summary is below Ran 62 tests in 811.542s OK (skipped=3) apparmor_4.0.0~beta2-0ubuntu3 has been installed on several up to date (as of March 7) noble systems. Boot/Reboot and regression tests have been done, against different kernel versions. 6.8.0-11-generic #11-Ubuntu 6.5.0-14-generic #14-Ubuntu 6.7.0 (upstream custom build) 6.8-rc3 (upstream custom build) The changelog is available here https://launchpad.net/~apparmor-dev/+archive/ubuntu/apparmor-devel/+files/apparmor_4.0.0~beta2-0ubuntu3_source.changes The prepared package is available via the ppa https://launchpad.net/~apparmor-dev/+archive/ubuntu/apparmor-ffe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056496/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
I've sponsored this for noble. For the SRUs, I would like to see a test case explicitly included that says you will regression-test this on other bluetooth pairings on other devices: the patch is not a platform- specific quirk, it is a change to generic bluetooth code, so there should be explicit tests that it does not break other devices. You mention in "where problems could occur" that you *have* tested the patch; but we should test the actual binaries produced as part of the SRU process, to be certain. ** Changed in: pulseaudio (Ubuntu Noble) Status: In Progress => Fix Committed ** Changed in: pulseaudio (Ubuntu Mantic) Status: In Progress => Incomplete ** Changed in: pulseaudio (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: Incomplete Status in pulseaudio source package in Mantic: Incomplete Status in pulseaudio source package in Noble: Fix Committed Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] Install the patched pulseaudio and reboot, connect to the LENOVO XT99 bt headset, select it to work in HFP mode, tested playback and capture, all worked well. [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055806] Re: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd
** Tags added: rls-nn-incoming ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2055806 Title: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd Status in openssh package in Ubuntu: New Bug description: Symptom: ssh.service is not running and not accepting new SSH connections and returns socket closed error upon attempted connection. ssh.service shows a failed with error message "Missing privilege separation directory: /run/sshd". The following line is needed in the SystemD Unit configuration of the ssh.service file for the openssh-server package to fix what appears to be a race condition when ssh.service is sometimes started before systemd-tmpfiles-setup.service is finished processing the file in /usr/lib/tmpfiles.d/openssh.server.conf that is required to create the /run/sshd directory that is required by ssh.service to start property. There might be more depth or an alternative reason to why /run/sshd/ still didn't exist after using ```systemctl reset-failed ssh.service```. So more investigation is needed by someone with more background in systemd-tmpfiles-setup.service and openssh-server package after it when to socket activation. = Error Messages = ``` $journalctl -u ssh.service -b-1 Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1271]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1369]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1454]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1465]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1475]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Start request repeated too quickly. Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57
[Touch-packages] [Bug 2054925] Update Released
The verification of the Stable Release Update for debootstrap has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: Fix Released Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mk-sbuild - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly
On Thu, Feb 29, 2024 at 10:19:40AM -, Frank Heimes wrote:
> Fix Committed with having:
> pam | 1.5.3-4ubuntu1 | noble-proposed | source
FTR this has been temporarily reverted, but it will be fix-committed again
shortly
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2045250
Title:
pam_lastlog doesn't handle localtime_r related errors properly
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in pam package in Ubuntu:
Fix Committed
Status in pam package in Fedora:
Fix Released
Bug description:
The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to
noble) are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Customers report a command going through PAM crashing for a given user.
A potential follow on issue can be that no ssh remote connections to an
affected server are possible anymore, esp. painful with headless systems (was
reported on a different distro).
This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
with tm = localtime_r(...) that can be NULL and needs to be handled.
There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
314- ll_time = last_login.ll_time;
315: if ((tm = localtime_r (_time, _buf)) != NULL) {
316- strftime (the_time, sizeof (the_time),
317- /* TRANSLATORS: "strftime options for date of last
login" */
--
574-
575- lf_time = utuser.ut_tv.tv_sec;
576: tm = localtime_r (_time, _buf);
577- strftime (the_time, sizeof (the_time),
578- /* TRANSLATORS: "strftime options for date of last login" */
Case 1 (line 315) is properly handled, but not case 2 (line 576).
The second case got fixed by:
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c
This fix should be included in Ubuntu (and Debian).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2045250/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Description changed: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - - mksbuild - - pbuilder whatever chroot management tool it has + - mk-sbuild + - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr - [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: Fix Committed Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mk-sbuild - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage
[Touch-packages] [Bug 2052399] Re: kbd is not built for i386
i386 is not supported as a standalone architecture in Ubuntu. ** Changed in: kbd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2052399 Title: kbd is not built for i386 Status in kbd package in Ubuntu: Won't Fix Bug description: kbd is not built for i386 which leads to Bug #1463840 dpkg: dependency problems prevent configuration of console-setup-linux: console-setup-linux depends on kbd (>= 0.99-12) | console-tools (>= 1:0.2.3-16); however: Package kbd is not installed. Package console-tools is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2052399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2054908] Re: gpg-wks-server pulls in postfix
On Sun, Feb 25, 2024 at 07:13:30PM -, Julian Andres Klode wrote: > Steve - it is a server package for hosting a web key server, it's > entirely reasonable for it to depend on a mail transport agent. A WKS > server, upon uploading a key, sends confirmation emails to the UIDs in > the key, before publishing it, so that it only published keys with > consent. Ok. This is a sensible rationale, unfortunately. But it was important to surface that in this bug report. > It's problematic that it was installed by default, and I'm fixing this > here and in Debian by doing the restructuring I did. This is not optimal > for people upgrading without quirks (i.e. Debian users especially) but I > don't think breaking the wks server to make upgrades without quirks > nicer is a better choice. Yeah, I don't see any better solution here. The only non-quirk solution would be to add an artificial Conflicts: against gpg-wks-server. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2054908 Title: gpg-wks-server pulls in postfix Status in Auto Package Testing: New Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Confirmed Status in munin package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Example 1 I did a sudo apt dist-upgrade today on my developer machine running Ubuntu Desktop 24.04 LTS and it surprisingly pulled in postfix. I did not built this into a full reproducible test case because I found another test case… Example 2 munin's autopkgtests are now failing because postfix is now unexpectedly being installed. https://autopkgtest.ubuntu.com/packages/munin/noble/amd64 Other Info gnupg2's changelog indicates that there was an attempt to avoid this misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is **nothing** in Ubuntu 24.04 LTS that Depends or Recommends gpg-wks-server. I added a munin bug task as a pointer in case anyone wonder's about the autopkgtest regression but I don't believe munin needs any changes. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: New Bug description: The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced against any up-to-date Ubuntu public archive mirror as of today. Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054908] Re: gpg-wks-server pulls in postfix
What is the rationale for a gpg package pulling in an MTA at all? I think this needs assessed. ** Changed in: gnupg2 (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2054908 Title: gpg-wks-server pulls in postfix Status in Auto Package Testing: New Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: New Status in munin package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Example 1 I did a sudo apt dist-upgrade today on my developer machine running Ubuntu Desktop 24.04 LTS and it surprisingly pulled in postfix. I did not built this into a full reproducible test case because I found another test case… Example 2 munin's autopkgtests are now failing because postfix is now unexpectedly being installed. https://autopkgtest.ubuntu.com/packages/munin/noble/amd64 Other Info gnupg2's changelog indicates that there was an attempt to avoid this misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is **nothing** in Ubuntu that Depends or Recommends gpg-wks-server. I added a munin bug task as a pointer in case anyone wonder's about the autopkgtest regression but I don't believe munin needs any changes. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Changed in: base-files (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: New Bug description: The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced against any up-to-date Ubuntu public archive mirror as of today. Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Belated response, but just for the record, Paride's recounting of upstream's position in the context of the Debian decision was definitive for me: On Wed, Jan 10, 2024 at 11:47:56AM -, Paride Legovini wrote: > Back in the day I asked upstream their take on irqbalance usefulness > with newer kernels, here is their reply: In effect what this says is that: irqbalance is still useful, but unless the admin configures it, the policy it provides is not a discernable improvement over the in-kernel default policy. Therefore I think it is the right path forward to unseed this and let users install it in situations where they want to configure it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in cloud-images: New Status in Release Notes for Ubuntu: In Progress Status in Ubuntu on IBM z Systems: Opinion Status in irqbalance package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
On Fri, Feb 16, 2024 at 06:51:46PM -, Philip Roche wrote: > @vorlon @jchittum @paelzer given the above findings are you still -1 on > any snap preseeding? Based on the data, I vote not to preseed any snaps. That is my position. Thanks for bringing data to this! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2019026] Re: systemd /tmp cleaning is suboptimal
On Fri, Feb 16, 2024 at 01:06:07PM -, Paride Legovini wrote: > Maybe we could make that 40d, as 30d is likely to be a time interval at > which a lot of periodic things happen (e.g. an off-site backup). The period here is the age at which files are considered old and to be clean up, not the interval at which the clean-up happens. Also fwiw I have edited my /usr/lib/tmpfiles.d/tmp.conf locally (using a diversion) since this bug was moving forward and it doesn't actually seem to be working. $ grep -v ^# /usr/lib/tmpfiles.d/tmp.conf d /tmp 1777 root root 30d $ sudo find /tmp -type f -mtime +30 | wc -l 130319 $ sudo find /tmp -atime +30 | wc -l 8 $ sudo find /tmp -ctime +30 | wc -l 744 $ So at least on desktop I have something that is regularly changing ctime/atime on the contents of /tmp and therefore preventing them from being garbage collected... -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2019026 Title: systemd /tmp cleaning is suboptimal Status in systemd package in Ubuntu: Confirmed Bug description: Historically on Debian and Ubuntu, before systemd, the default handling of /tmp was to periodically, and at boot, remove all files/directories older than 30 days; and leave other contents alone. With the move to systemd, the "default" (really, hard-coded in /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but at boot to remove all contents. This is suboptimal for two reasons. By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp and has lots of inodes under it, possibly due to failures of some process to clean up after itself, at boot the system will be unavailable for an unnecessarily long time while these files are removed. By cleaning *all* files under /tmp, this makes a reboot an Event where in-progress files may be unnecessarily lost. While the FHS does not *guarantee* that files under /tmp will persist across boot (because /tmp may be a tmpfs), it also does not *require* that /tmp be cleared on boot. Although data stored in /tmp may be deleted in a site-specific manner, it is recommended that files and directories located in /tmp be deleted whenever the system is booted. FHS added this recommendation on the basis of historical precedent and common practice, but did not make it a requirement because system administration is not within the scope of this standard. I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf to restore past behavior is 'd /tmp 1777 root root 30d'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2019026] Re: systemd /tmp cleaning is suboptimal
You say "Nick's preference", but it's Nick who took the position here that the default behavior should not change? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2019026 Title: systemd /tmp cleaning is suboptimal Status in systemd package in Ubuntu: Confirmed Bug description: Historically on Debian and Ubuntu, before systemd, the default handling of /tmp was to periodically, and at boot, remove all files/directories older than 30 days; and leave other contents alone. With the move to systemd, the "default" (really, hard-coded in /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but at boot to remove all contents. This is suboptimal for two reasons. By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp and has lots of inodes under it, possibly due to failures of some process to clean up after itself, at boot the system will be unavailable for an unnecessarily long time while these files are removed. By cleaning *all* files under /tmp, this makes a reboot an Event where in-progress files may be unnecessarily lost. While the FHS does not *guarantee* that files under /tmp will persist across boot (because /tmp may be a tmpfs), it also does not *require* that /tmp be cleared on boot. Although data stored in /tmp may be deleted in a site-specific manner, it is recommended that files and directories located in /tmp be deleted whenever the system is booted. FHS added this recommendation on the basis of historical precedent and common practice, but did not make it a requirement because system administration is not within the scope of this standard. I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf to restore past behavior is 'd /tmp 1777 root root 30d'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
> This is a significant difference and for a workload we intend to remain as a > core tested > and tracked workload. As such I propose we re-introduce core22 and snapd > snaps to our seed. I disagree that the image should be optimized by default to prioritize the one-time startup performance of an optional use case. 15 seconds vs 30 seconds, on a thing that won't affect most cloud customers, and happens at most once per image, AND should be weighed against the first-boot speed improvements in clouds resulting from having a smaller image? Also, statically seeding a particular base snap is bad form, as soon as lxd upgrades its base you lose your performance benefit and have to play catch-up in a stable release. If "time to initialize lxd" is your metric, I think you're measuring the wrong thing :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
$ git tag --contains 85c975df2c2 v9.1 v9.2 v9.3 v9.4 $ git tag --contains 92cb8427c53 v9.1 v9.2 v9.3 v9.4 $ Ubuntu 23.10 includes coreutils 9.1, 24.04 LTS will include coreutils 9.4. So this bug is fixed in the latest release of Ubuntu. ** Changed in: coreutils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: Fix Released Status in coreutils package in Fedora: Fix Released Bug description: Release: 22.04.3 LTS coreutils 8.32-4.1ubuntu1 ls triggers unwanted mounts of autofs filesystems cause: coreutils 8.32.4.1ubuntu1 uses statx which not pass the AT_NO_AUTOMOUNT flag This bug is also known (and fixed) at Redhat https://bugzilla.redhat.com/show_bug.cgi?id=2044981 upstream commits: https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-178-g92cb8427c53 fedora commit https://src.fedoraproject.org/rpms/coreutils/c/d736cafa20f13eeb037a3950bdbb4b63dc39b7e3?branch=f35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051765] Re: Plymouth FTBFS (even after apt-get build-dep plymouth)
packages in launchpad always build against -proposed. How are you building this that you're not getting the systemd in proposed? ** Tags removed: regression-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2051765 Title: Plymouth FTBFS (even after apt-get build-dep plymouth) Status in plymouth package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Fix Committed Bug description: dh_install dh_install: warning: Cannot find (any matches for) "lib/systemd/system" (tried in ., debian/tmp) dh_install: warning: plymouth missing files: lib/systemd/system dh_install: error: missing files, aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2051765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051594] Re: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
The log output shows that you have pam_tally or pam_tally2 in your pam configuration. The preinst fails in order to save you from upgrading and breaking your system, leaving you with a configuration referencing an obsolete pam module. The message says: you are using pam_tally or pam_tally2 in your configuration The pam_tally and pam_tally2 modules have been removed from PAM. You are using one of these modules in your PAM configuration in /etc/pam.d. You must remove the uses of these modules before PAM can be upgraded; including these modules in your PAM configuration after the upgrade will stop users from being able to log into the system. Consider the pam_faillock module as a replacement for pam_tally. The fact that this message was shown to you via the pam preinst script also indicates that you were not using ubuntu-release-upgrader, the recommended way to upgrade between Ubuntu releases. On servers, please upgrading using 'sudo do-release-upgrade'. On desktops, please use 'update-manager'. ** Changed in: pam (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2051594 Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 Status in pam package in Ubuntu: Invalid Bug description: failed during upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4.7 ProcVersionSignature: Ubuntu 5.4.0-170.188-generic 5.4.257 Uname: Linux 5.4.0-170-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 29 13:45:41 2024 ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2017-09-02 (2340 days ago) InstallationMedia: Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.10 SourcePackage: pam Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2024-01-29 (0 days ago) modified.conffile..etc.security.limits.conf: [modified] mtime.conffile..etc.security.limits.conf: 2017-09-01T17:53:53.083396 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2051594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2049318] Re: [SRU] free(): double free detected in tcache 2
Hello Jo, or anyone else affected, Accepted iptables into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables/1.8.7-1ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: iptables (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: Fix Committed Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] 1. Simple test plan based on upstream test case: sudo nft -f - < rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2042587] Re: jammy's version breaks existing dhcp scripts with relay
Hello Timo, or anyone else affected, Accepted dnsmasq into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dnsmasq/2.86-1.1ubuntu0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dnsmasq (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Committed Bug description: [ Impact ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. This was fixed in 2.87, therefore making only jammy carry an affected package. [ Test Plan ] To easily test this on a single machine, a test script is being provided to setup networking and dnsmasq configuration. # Launch a jammy VM lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm # open a root shell in that VM. All subsequent commands must be executed as root in that VM lxc shell j-dnsmasq-2042587 # download test script wget https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738174/+files/setup- and-server.sh # make it executable chmod +x setup-and-server.sh # install dnsmasq. Ignore the postinst error (because systemd-resolved is also running and there is a port conflict) apt update && apt install dnsmasq -y # run the setup script. It will configure things and start dnsmasq ready to be tested ./setup-and-server.sh # in another root session inside the vm (so run "lxc shell j-dnsmasq-2042587" in another terminal), run the proposed commands from the setup script (and press ctrl-c after the result is shown): No DHCP relay: ip netns exec client dhclient -d -v p2 The setup script should log an IP that is not a relay. For example: dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.150 ### With DHCP relay set to 192.168.47.9, IP should NOT be that address: ip netns exec client dhclient -d -v p2 -g 192.168.47.9 With the affected dnsmasq package, we will see an error: dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.9 TEST FAILED ### The error is that the obtained IP is that of the dhcp relay (provided via the -g option). With the fixed dnsmasq package, "TEST FAILED" must not appear, and the IP should not be that of the provided dhcp relay. [ Where problems could occur ] If the fix is incorrect, it would mean the dhcp-script would get an incorrect IP again, or perhaps we could have crashes in dnsmasq when dealing with buffers and pointers if the dhcp-script option is in use. This fix was committed upstream a few months after the bug was introduced, so it took a while to be noticed. [ Other Info ] Not at this time. [ Original description ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The
[Touch-packages] [Bug 2045570] Re: dnsmasq crash when no servers in resolv.conf
Hello Alfred, or anyone else affected, Accepted dnsmasq into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dnsmasq/2.86-1.1ubuntu0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dnsmasq (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2045570 Title: dnsmasq crash when no servers in resolv.conf Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Committed Bug description: [ Impact ] dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the file is updated. When that happens and for some reason there were no "nameserver" declarations in the updated file, dnsmasq can crash. Here is a log of a reproducer: $ dig +short @127.0.0.1 ubuntu.com ;; communications error to 127.0.0.1#53: timed out ;; communications error to 127.0.0.1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached We can see the startup, then when resolv.conf is read again and no nameservers were found, and the crash: Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 cachesize 150 Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local subnets Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 10.0.100.1#53 Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in /etc/resolv.conf, will retry Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with result 'core-dump'. dnsmasq has provisions for this situation, we can see that in the 13:58:01 message where it says it will retry, but due to this bug, it crashes instead. The problem was introduced[1] in version 2.86, and fixed in 2.87, so only jammy is affected. 1. https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=d290630d31f4517ab26392d00753d1397f9a4114;hp=d2ad5dc073aaacaf22b117f16106282a73586803 The commit message says: """ This problem was introduced in 2.86. """ And indeed, I wasn't able to crash 2.80 shipped in focal. [ Test Plan ] It might take a few tries to reproduce the bug, but here is the general outline. Also keep in mind that it's important to use a DNS name that isn't cached already by a previous query. # Create a jammy lxd container lxc launch ubuntu-daily:jammy j-dnsmasq-2045570 # Enter the container lxc shell j-dnsmasq-2045570 # From now on, all commands should be executed in the container. # Install dnsmasq, and disable systemd-resolved apt update && apt install -y dnsmasq # Disable systemd-resolved, and start dnsmasq systemctl disable --now systemd-resolved systemctl enable --now dnsmasq # In one terminal inside the container, watch the dnsmasq logs: journalctl -u dnsmasq.service -f # In another terminal, remove /etc/resolv.conf and create a new one, empty rm /etc/resolv.conf echo "nameserver 1.1.1.1" > /etc/resolv.conf # restart dnsmasq systemctl restart dnsmasq.service # Perform a dns query dig @127.0.0.1 +short linux.com # Comment the
[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
Hello Gil, or anyone else affected, Accepted openssl into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Kinetic: Won't Fix Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/pull/18876 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate
Hello bugproxy, or anyone else affected, Accepted openssl into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Jammy) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2023545 Title: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] Openssl using an engine dumps core upon certificate creation; other operations are probably affected too. Overall, engines are likely mostly unusable. [Test plan] - An openssl engine is req. to test the fix. - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN. - Check with 'lszcrypt -V' the availability (online) of the hw crypto resources. - Install the needed package that allows to exploit the hw crypto resources: sudo apt-get install libica-utils libica? openssl-ibmca - And copy a working sample openssf.cnf file: sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample /etc/ssl/openssl.cnf - Verify if the 'openssl engine' lists an ibmca engine, in addition to the dynamic engine: (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support <=== - try to create a new certificate, using this cmd-line: openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' - The above command must not lead to a 'Segmentation fault (core dumped)', rather than create a proper certificate file. Also watch /var/log/syslog / journalctl for more details. - The issue is fixed in openssl 3.0.8 which landed in lunar. [Where problems could occur] I don't pretend to understand the lifecycle of providers in openssl3 but the patch is simple and has been widely tested by now, including on ubuntu. Thus, I see little chance an unexpected problem would occur with it. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/issues/18578 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy- sru-0001-Release-the-drbg-in-the-global-default-context- befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024 Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not tainted 5.15.0-73-generic #80-Ubuntu Jun 07
[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
Hello Adrien, or anyone else affected, Accepted openssl into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains THREE changes which are listed in the section below. [Meta] This bug is part of a series of three bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses three issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections (this one) The SRU information has been added to the three bug reports and I am attaching the debdiff here only for all three. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture-dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used
[Touch-packages] [Bug 2040011] Re: [SRU] Ensure supported codenames are accurate
** Changed in: vim (Ubuntu Mantic) Status: In Progress => Incomplete ** Changed in: vim (Ubuntu Jammy) Status: In Progress => Incomplete ** Changed in: vim (Ubuntu Focal) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2040011 Title: [SRU] Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Released Status in vim source package in Focal: Incomplete Status in vim source package in Jammy: Incomplete Status in vim source package in Lunar: Won't Fix Status in vim source package in Mantic: Incomplete Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems
** Changed in: util-linux (Ubuntu Lunar) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: Fix Committed Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: Won't Fix Status in util-linux source package in Mantic: Fix Released Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047450] Re: tail emits no output for sysfs files when using large page kernels
An upload of coreutils to lunar-proposed has been rejected from the upload queue for the following reason: "lunar EOL in 9 days; no more SRUs". ** Changed in: coreutils (Ubuntu Lunar) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: In Progress Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: In Progress Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2048914] Re: System program problem detected at every login Xubuntu Update Notifier
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2048914/+attachment/5738098/+files/apport.log shows thermald having crashed. If you disable the thermald service with `sudo systemctl disable thermald; sudo systemctl stop thermald` does the problem persist after the next couple of logins? ** Changed in: whoopsie (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2048914 Title: System program problem detected at every login Xubuntu Update Notifier Status in update-notifier package in Ubuntu: New Status in whoopsie package in Ubuntu: Incomplete Bug description: Every time I log in to my new installation of Xubuntu 24.04 (daily ISO) after a reboot, I get an error message that says, "System program problem detected." Clicking either Cancel or Report Problem only dismisses the pop-up without any further action. This has occurred on multiple computers. This began with the first boot after installation and occurs at each subsequent reboot upon logging in. Logging out and back in does not cause the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: update-notifier 3.192.66 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Jan 10 09:57:25 2024 ExecutablePath: /usr/bin/update-notifier InstallationDate: Installed on 2024-01-10 (0 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240110) ProcEnviron: LANG=C.UTF-8 LANGUAGE=en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2048914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040011] Proposed package upload rejected
An upload of vim to lunar-proposed has been rejected from the upload queue for the following reason: "lunar EOL in 9 days; no more SRUs". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2040011 Title: [SRU] Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Released Status in vim source package in Focal: In Progress Status in vim source package in Jammy: In Progress Status in vim source package in Lunar: Won't Fix Status in vim source package in Mantic: In Progress Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040011] Re: [SRU] Ensure supported codenames are accurate
lunar EOLs in 7 days. Not accepting any more SRUs. ** Changed in: vim (Ubuntu Lunar) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2040011 Title: [SRU] Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Released Status in vim source package in Focal: In Progress Status in vim source package in Jammy: In Progress Status in vim source package in Lunar: Won't Fix Status in vim source package in Mantic: In Progress Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2048914] Re: System program problem detected at every login Xubuntu Update Notifier
** Also affects: whoopsie (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2048914 Title: System program problem detected at every login Xubuntu Update Notifier Status in update-notifier package in Ubuntu: New Status in whoopsie package in Ubuntu: New Bug description: Every time I log in to my new installation of Xubuntu 24.04 (daily ISO) after a reboot, I get an error message that says, "System program problem detected." Clicking either Cancel or Report Problem only dismisses the pop-up without any further action. This has occurred on multiple computers. This began with the first boot after installation and occurs at each subsequent reboot upon logging in. Logging out and back in does not cause the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: update-notifier 3.192.66 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Jan 10 09:57:25 2024 ExecutablePath: /usr/bin/update-notifier InstallationDate: Installed on 2024-01-10 (0 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240110) ProcEnviron: LANG=C.UTF-8 LANGUAGE=en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2048914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Christian, I see a lot of strong opinions being given, but aside from the "don't use it in KVM" guidance which appears to be based on GCE's engineering expertise, very little evidence that irqbalance is actually a problem. I think it's true that in the default config, irqbalance can interfere with putting CPUs into higher C states to conserve power. However, I don't see any indication of quantitative analysis showing the impact. Recent versions of irqbalance have a '--powerthresh' argument that can be used to tell irqbalance to rebalance across fewer cores when CPU load is low, to allow some of the cores to be put into a sleep state and conserve power. My own initial testing on my desktop shows that this gets used for all of about 10 seconds at a time every few hours, before the load increases and irqbalance wakes the core back up... I would want any decision to remove irqbalance from the desktop to be based on evidence, not conjecture. At a minimum, I think what I would like to see is output from powertop showing both power consumption and CPU idle stats over a reasonable amount of time (10 minutes?), on a representative client machine, for a 2x3 matrix of configurations: - idle vs normal desktop load - irqbalance disabled vs irqbalance enabled with defaults vs irqbalance enabled with IRQBALANCE_ARGS=--powerthresh=1 System should be rebooted between each of the irqbalance configurations, as I'm not sure what does or doesn't persist in the CPU config after irqbalance exits. I am specifically not going to try to rebut the various webpages referenced here, beyond saying that there's an awful lot of these pages pointing to one other as authoritative sources on irqbalance without there actually being evidence to back them up (and a heaping spoonful of misinformation / outdated information along the way). So if we're going to make a change, there should be due diligence to demonstrate a benefit, it should not be based on Internet hype. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047008] Re: [SRU] Add Telit FN990 compositions
Hello Laider, or anyone else affected, Accepted modemmanager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: modemmanager (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045621] Please test proposed package
Hello Artur, or anyone else affected, Accepted systemd-hwe into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd- hwe/249.11.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: Fix Committed Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045621] Re: Improve power consumption on Framework systems
Hello Artur, or anyone else affected, Accepted systemd-hwe into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd- hwe/253.5.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd-hwe (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: systemd-hwe (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: Fix Committed Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036253] Re: FTBFS: missing strl* symbols fail the build
This fixes a build failure but has no user-facing impact, it does not need to be released to -updates. Setting block-proposed tag. ** Tags added: block-proposed-mantic ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: Fix Released Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Released Status in heimdal package in Debian: Fix Released Bug description: [ Impact ] Currently, the build of the heimdal package against glibc 2.38 is not possible due to the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. We need this fix to build the heimdal package successfully. It's also important to be able to apply security fixes in the future (if needed). [ Test plan ] Build the package in a ppa to check that the error is gone and that the package builds successfully. # Install the package and check it works ok #0.Prepare a VM or Container. i.e: # lxc launch ubuntu-daily:mantic Mheimdal # lxc shell Mheimdal #1. Install heimtools from heimdal-clients # apt update && apt upgrade -y # apt install -y heimdal-clients #1.1 Check the libraries are installed well # dpkg -l libroken19-heimdal | grep ii # dpkg -l libkafs0-heimdal | grep ii #1.2 Check that the command is not broken (you get a Usage: : heimtools [--version] [--help] command ..) # heimtools --help #2. Install aklog from src:aftools, openafs-krb5 binary package. A rebuild of aftools against the new heimdal package is needed for this to be successfull. # apt install -y openafs-krb5 #2.1 Check that the command is not broken (you don't get a aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0) # aklog --help [ Where problems could occur ] I tried to get a complete list of libraries and binaries that use the symbols affected in this fix (inside and outside the ones provided by src:heimdal itself), but, I don't know if there are other third-party pieces of software outside the archive that depends on these libraries. If that is the case, when executing, the affected binary will no run and a message like this could appear: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0 Could be a disruption in the way the heimdal suite works? Unlikely, but there is always room for it. It should be fine since the symbols, in this case, are available to all heimdal-dependants libraries in the build. This case could arise if a mix of heimdal libraries (provided by two different versions of src:heimdal) are installed, but this is what the 'Breaks:' that was added in the d/control wants to avoid. [ Other Info ] A rebuild of the openafs package against this new version of the libraries provided by this heimdal package is needed. (bug 2046441). [ Original Description ] See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base 1.4.0+git20110226 k_afs_cell_of_file@Base 1.4.0+git20110226 k_hasafs@Base 1.4.0+git20110226 k_hasafs_recheck@Base 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:18: override_dh_makeshlibs] Error 25 This one might need a fix similar to the krb5 one[3]. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042784.html 2. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html#ubuntu-server-team 3. https://launchpad.net/ubuntu/+source/krb5/1.20.1-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036253] Please test proposed package
Hello Andreas, or anyone else affected, Accepted heimdal into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/heimdal/7.8.git20221117.28daf24+dfsg-3ubuntu1.23.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: Fix Released Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Released Status in heimdal package in Debian: Fix Released Bug description: [ Impact ] Currently, the build of the heimdal package against glibc 2.38 is not possible due to the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. We need this fix to build the heimdal package successfully. It's also important to be able to apply security fixes in the future (if needed). [ Test plan ] Build the package in a ppa to check that the error is gone and that the package builds successfully. # Install the package and check it works ok #0.Prepare a VM or Container. i.e: # lxc launch ubuntu-daily:mantic Mheimdal # lxc shell Mheimdal #1. Install heimtools from heimdal-clients # apt update && apt upgrade -y # apt install -y heimdal-clients #1.1 Check the libraries are installed well # dpkg -l libroken19-heimdal | grep ii # dpkg -l libkafs0-heimdal | grep ii #1.2 Check that the command is not broken (you get a Usage: : heimtools [--version] [--help] command ..) # heimtools --help #2. Install aklog from src:aftools, openafs-krb5 binary package. A rebuild of aftools against the new heimdal package is needed for this to be successfull. # apt install -y openafs-krb5 #2.1 Check that the command is not broken (you don't get a aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0) # aklog --help [ Where problems could occur ] I tried to get a complete list of libraries and binaries that use the symbols affected in this fix (inside and outside the ones provided by src:heimdal itself), but, I don't know if there are other third-party pieces of software outside the archive that depends on these libraries. If that is the case, when executing, the affected binary will no run and a message like this could appear: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0 Could be a disruption in the way the heimdal suite works? Unlikely, but there is always room for it. It should be fine since the symbols, in this case, are available to all heimdal-dependants libraries in the build. This case could arise if a mix of heimdal libraries (provided by two different versions of src:heimdal) are installed, but this is what the 'Breaks:' that was added in the d/control wants to avoid. [ Other Info ] A rebuild of the openafs package against this new version of the libraries provided by this heimdal package is needed. (bug 2046441). [ Original Description ] See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226
[Touch-packages] [Bug 2047656] Re: [SRU] Players terminate after stopping and restarting
> * Begin midi playback in any midi player using fluidsynth from the terminal This is not a reproducible test case that can be actioned by someone just reading the bug. Please provide a specific test case showing how to reproduce the failure. If possible, it would be best to also provide a reference midi file to use. ** Changed in: fluidsynth (Ubuntu Mantic) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/2047656 Title: [SRU] Players terminate after stopping and restarting Status in fluidsynth package in Ubuntu: Fix Released Status in fluidsynth source package in Mantic: Incomplete Status in fluidsynth source package in Noble: Fix Released Bug description: [ Impact ] Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop of playback of a midi song, causing issues for a multitude of players including EasyABC. This will cause said player to be unable to playback again and perhaps even crash. See https://github.com/FluidSynth/fluidsynth/issues/1272, fix in https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055. This is the included patch with the upload of 2.3.3-2.1ubuntu-0.23.10.1 [ Test Case ] * Begin midi playback in any midi player using fluidsynth from the terminal * Stop midi playback * Attempt start again * Error in terminal: fluidsynth: error: The maximum playback duration has been reached. Terminating player! [ What could go wrong ] This is actually a fix for a regression that was found in version 2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble. I think the only thing that can go wrong here is that this patch is not the actual fix and we need to find more solutions within. I have tested this in my PPA and it *seems* to fix it, but it would be nice if the original reporter could verify once this lands in proposed. [ Other information ] Included below is the original report, in which case the reporter deduces that the problem is the binary being spat-out is the 2.3.2 version from the 2.3.3 sources. This is not the case, as it appears to be confusion due to the -2.1 Debian revision number. I assure, this is definitely the 2.3.3, and the bug, per the github link in the Impact section, is pertinent to this version. --- The latest package of fluidsynth should include the sources from version 2.3.3 but the binary includes only version 2.3.2 This version has a bug (see https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to problems in EasyABC. Please include the latest version 2.3.3 from upstream in the ubuntu package. -- Description: Ubuntu 23.10 Release: 23.10 Codename: mantic $ apt-cache policy libfluidsynth3 libfluidsynth3: Installiert: 2.3.3-2.1 Installationskandidat: 2.3.3-2.1 Versionstabelle: *** 2.3.3-2.1 500 500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047314] Please test proposed package
Hello Bill, or anyone else affected, Accepted tzdata into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023d-0ubuntu0.20.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047314] Please test proposed package
Hello Bill, or anyone else affected, Accepted tzdata into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023d-0ubuntu0.22.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047314] Please test proposed package
Hello Bill, or anyone else affected, Accepted tzdata into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023d-0ubuntu0.23.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
Hello Bill, or anyone else affected, Accepted tzdata into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023d-0ubuntu0.23.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Mantic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: tzdata (Ubuntu Lunar) Status: New => Fix Committed ** Tags added: verification-needed-lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2048192] Re: package ssh 1:8.2p1-4ubuntu0.10 failed to install/upgrade: problèmes de dépendances - laissé non configuré
janv. 05 08:36:19 machineubuntu sshd[5752]: /etc/ssh/sshd_config.d/port.conf: line 4: Bad configuration option: CleintAliveCountMax janv. 05 08:36:19 machineubuntu sshd[5752]: /etc/ssh/sshd_config.d/port.conf: terminating, 1 bad configuration options You have an invalid configuration option in your config file, because it is misspelled. You will need to correct this configuration to be able to start sshd. At which point 'sudo dpkg --configure -a' should resolve the package install issue. ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2048192 Title: package ssh 1:8.2p1-4ubuntu0.10 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in openssh package in Ubuntu: Invalid Bug description: seems I won't be able to upgrade the system to the next LTS untill this package is updated ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ssh 1:8.2p1-4ubuntu0.10 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: openssh-sftp-server:amd64: Install openssh-server:amd64: Install openssh-client:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 5 08:36:19 2024 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-08-18 (504 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: openssh Title: package ssh 1:8.2p1-4ubuntu0.10 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2048192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046971] Re: RM signon from noble
Removing packages from noble: signon 8.59+17.10.20170606-0ubuntu3 in noble Comment: superseded by signond; LP: #2046971 1 package successfully removed. ** Changed in: signon (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/2046971 Title: RM signon from noble Status in signon package in Ubuntu: Fix Released Bug description: signond was merged from Debian, making this signon a source package providing no binaries. Please kick it out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/2046971/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
There is no workaround for this with the stock netplan config on raspberry pi, which trips this bug. But you can customize /etc/netplan/ on your system to mark your expected/required network interfaces as "optional: false" (which is the default if unspecified); AIUI that would avoid this issue with systemd-networkd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046116] Re: bluetooth device connected but not recognised as output device
** Tags added: regression-security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2046116 Title: bluetooth device connected but not recognised as output device Status in bluez package in Ubuntu: New Bug description: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when preconfiguring packages
Ok. Then I still have absolutely no idea how/why this is happening for you, because that doesn't seem to match the code we ship. Unless you have some non-distribution version of the apt- extracttemplates program installed? (which apt-extracttemplates; sudo apt install debsums; debsums -s apt-utils) ** Changed in: debconf (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/2043711 Title: Open3.pm tries to run code in /tmp when preconfiguring packages Status in debconf package in Ubuntu: New Bug description: During update of ubuntu-drivers-common: Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1. open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 1:0.9.6.2~0.22.04.4 failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59. Preconfiguring packages ... Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1. open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 1:0.9.6.2~0.22.04.4 failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59. /tmp is mounted with noexec because running code from /tmp has been a vulnerability vector for several decades, hence reporting this as a vulnerability in perl-base. This error did not appear to prevent the update of ubuntu-drivers- common and "dpkg --verify ubuntu-drivers-common" returns 0. ___ Attempting to use the package search on this form by clicking the created a modal in which there is an error Sorry, something went wrong with your search. We've recorded what happened, and we'll fix it as soon as possible. (Error ID: OOPS-c80f71590b02908a1187b9f743c53eac) which is repeated with any attempt to search for a package. ___ Submitting this form gives an error "perl-base" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" $ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm $ dpkg -l perl-base Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--=> ii perl-base 5.34.0-3ubuntu1.2 amd64minimal Perl system Looks like a package to me. Nevertheless, using "Did you mean..." offers "perl". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: perl-base 5.34.0-3ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3 Uname: Linux 6.5.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 16 10:08:48 2023 InstallationDate: Installed on 2016-04-23 (2763 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: perl UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2043711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when preconfiguring packages
Thanks, this definitely does point at debconf. However:
> Preconfiguring packages ...
This line is from /usr/sbin/dpkg-preconfigure, which is called via
/etc/apt/apt.conf.d/70debconf.
> Can't exec "/tmp/cryptsetup-initramfs.config.UaZ02N": Permission
denied at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,
line 1.
This line shows a path which is NOT where /usr/sbin/dpkg-preconfigure
unpacks the configure script. It uses a hard-coded path of
/var/cache/debconf/tmp.ci:
my $tempdir='/var/cache/debconf/tmp.ci';
[...]
if (system("apt-extracttemplates", "--tempdir",
$tempdir, @collect) != 0) {
[...]
What does `readlink -f /var/cache/debconf/tmp.ci` return on your system?
** Changed in: debconf (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/2043711
Title:
Open3.pm tries to run code in /tmp when preconfiguring packages
Status in debconf package in Ubuntu:
Incomplete
Bug description:
During update of ubuntu-drivers-common:
Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure
1:0.9.6.2~0.22.04.4 failed: Permission
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure
1:0.9.6.2~0.22.04.4 failed: Permission
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
/tmp is mounted with noexec because running code from /tmp has been a
vulnerability vector for several decades, hence reporting this as a
vulnerability in perl-base.
This error did not appear to prevent the update of ubuntu-drivers-
common and "dpkg --verify ubuntu-drivers-common" returns 0.
___
Attempting to use the package search on this form by clicking the
created a modal in which there is an error
Sorry, something went wrong with your search. We've recorded what
happened, and we'll fix it as soon as possible. (Error ID:
OOPS-c80f71590b02908a1187b9f743c53eac)
which is repeated with any attempt to search for a package.
___
Submitting this form gives an error
"perl-base" does not exist in Ubuntu. Please choose a different
package. If you're unsure, please select "I don't know"
$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-=--=>
ii perl-base 5.34.0-3ubuntu1.2 amd64minimal Perl system
Looks like a package to me. Nevertheless, using "Did you mean..."
offers "perl".
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: perl-base 5.34.0-3ubuntu1.2
ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3
Uname: Linux 6.5.0-1007-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 16 10:08:48 2023
InstallationDate: Installed on 2016-04-23 (2763 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=rxvt
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: perl
UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2043711/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable
The usrmerge transition was completed already in Ubuntu several cycles ago. We should not promote usr-is-merged to main, we should drop the dependencies on it instead. usrmerge can also be dropped from main now. It is only in main because it is seeded with the rationale: * (usrmerge) # xnox Default since Disco. Will be mandatory in 22.10. Only recommend, such that it is installed on upgrades, can be removed afterwards. The comment is misleading, the commit talking about "mandatory in 22.10" was made in November 2020. We've had a full LTS cycle since then where users, whether on new installs or upgrades, have been in a usrmerge configuration and there is no support for non-usrmerged filesystems in Ubuntu 21.04 or later. So we should drop this recommends, drop usrmerge source from main, and drop dbus's dependency on usr-is-merged. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2045668 Title: Please merge dbus 1.14.10-3 (main) from Debian unstable Status in dbus package in Ubuntu: In Progress Bug description: 1.14.10-3 Published in sid-release on 2023-10-30 dbus (1.14.10-3) unstable; urgency=medium * d/control: dbus Depends on usr-is-merged (>= 38~). Non-merged /usr has been unsupported since Debian 12, as per Technical Committee resolutions #978636 and #994388 (please see the Debian 12 release notes for details). The version of usr-is-merged shipped in Debian 12 had an undocumented opt-out mechanism intended for use on buildds and QA systems targeting Debian 12 (piuparts, reproducible-builds, autopkgtest and similar), to ensure that the upgrade path from Debian 11 to 12 will continue to work and continue to undergo automated tests. That opt-out is no longer applicable or available in trixie/sid, and was removed in usrmerge version 38. Since version 1.14.10-2, dbus ships its systemd units in /usr/lib/systemd/system, as part of the distro-wide transition away from making use of "aliased" paths. This is entirely valid on merged-/usr systems, but will no longer work in the unsupported filesystem layout with non-merged /usr, because for historical reasons, current versions of systemd on non-merged-/usr systems will only read units from /lib/systemd/system. In the case of dbus, the symptom when this assumption is broken is particularly bad (various key system services will not start, with long delays during boot, login and shutdown), so let's hold back this upgrade on unsupported non-merged-/usr systems until they have completed the switch to merged-/usr and can install usr-is-merged (>= 38~). (Closes: #1054650) -- Simon McVittie Mon, 30 Oct 2023 11:51:35 + 1.14.10-2 Superseded in sid-release on 2023-10-30 dbus (1.14.10-2) unstable; urgency=low * Backport packaging changes from experimental: - Install systemd system units into /usr/lib/systemd/system. This was allowed by TC resolution #1053901. The shared library is still in /lib, for now. Build-depend on debhelper 13.11.6~ to ensure that the units are still picked up by dh_installsystemd. - Build-depend on pkgconf rather than pkg-config - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation environment. These variables are specific to a single login session. * d/copyright: Drop unused entry for pkg.m4. This is no longer included in the upstream source release since 1.14.6. * d/dbus-tests.lintian-overrides: Drop unused overrides. Lintian no longer flags our RUNPATH as problematic. -- Simon McVittie Wed, 25 Oct 2023 15:56:36 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046026] Re: Performance problem with openssh-client
Working: OpenSSH_9.2p1 Raspbian-2, OpenSSL 3.0.11 19 Sep 2023 Problem: OpenSSH_9.2p1 -2+deb12u1, OpenSSL 3.0.11 19 Sep 2023 Neither of these are Ubuntu packages. ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2046026 Title: Performance problem with openssh-client Status in openssh package in Ubuntu: Invalid Bug description: I have noticed a massive loss of performance in the openssh-client package. It has no impact on a raspberry pi 4 because it has enough CPU power, but on a pi zeroW it took about 10 seconds until the command prompt is shown to enter the password (or autologin) while CPU load is 100%. It can be reproduced very simple: On a Pi ZeroW open a terminal and connect to a ssh server. It has worked before, but then "Raspian-2" version was replaced with "-2+deb12u1" which has this problem. Working: OpenSSH_9.2p1 Raspbian-2, OpenSSL 3.0.11 19 Sep 2023 Problem: OpenSSH_9.2p1 -2+deb12u1, OpenSSL 3.0.11 19 Sep 2023 As you can see, the version number is the same. But the description is different. It looks like something like hardware acceleration is missing. If i replace /usr/bin/ssh with the "old" one it works perfect. Login prompt is shown in about 2 seconds. But with the new version it took about 10 seconds until the prompt is shown. Please let me know if you need any further information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2046026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
On Sun, Dec 10, 2023 at 01:45:36AM -, Roger Nelson wrote: > I'm curious if this bug is still being investigated. RPI4 with wlan0, > eth0 and eth1 (USB3 using r8152 driver) definitely manifests this bug. I > need to wait ~30 minutes before either wlan0 or eth0 becomes available > in order to restart systemd-networkd to activate eth1 and then ip link > set up eth1. This bug report is about a change in behavior of the systemd wait-online target at boot. "Need to wait 30 minutes before network device becomes available" sounds unrelated. You should file a separate bug report for your issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
Oh. To the question of whether there was a systemd change in this window: yes absolutely, because this is the point at which the riscv64 builders moved from lgw manually-operated qemu with a 20.04 guest image, to bos03 openstack-operated qemu with a 22.04 guest image. Which is also why we've moved from 5.13.0-1019-generic to 5.19.0-1021-generic. But again, it was my understanding that these devices are supposed to be created synchronously WITHOUT the involvement of udev. In fact, we had to make launchpad-buildd changes to make use of these devices at all because udev would NOT set them up for us. So if these are now being set up via udev, that's a significant departure from expectations and it's not clear we even CAN have synchronous behavior given that they would be set up by the host udev and not the udev in the lxd container! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
On Sat, Dec 09, 2023 at 05:13:28PM -, Andy Whitcroft wrote: > Was there any systemd/udev change in this timeframe? As the device > files are very much connected to those. My understanding is that these devices are supposed to be created directly by the kernel on devtmpfs and NOT via udev, which is part of how we expected to fix the earlier races. And systemd did not change in this time frame in any release. If there was a change to the HOST udev in this timeframe causing a regression because a new base image was published that includes a newer udev, we don't have visibility on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046022] Re: Failed to disable unit: Unit file NetworkManager-wait-online-service.service does not exist.
The unit is called 'NetworkManager-wait-online.service' not 'NetworkManager-wait-online-service.service'. ** Package changed: plymouth (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2046022 Title: Failed to disable unit: Unit file NetworkManager-wait-online- service.service does not exist. Status in network-manager package in Ubuntu: Invalid Bug description: when i try to disable network manager wait online service - I get a notificaiton saying as below Failed to disable unit: Unit file NetworkManager-wait-online-service.service does not exist. But when i do the analyze blame - i clearly see close to 15 seconds being eaten up by the network manager needs attention - since boot speed is pathetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable
This test plan does not describe in what environment to run the command, or how to check afterwards that the locale has been changed. ** Changed in: systemd (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2035122 Title: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Bug description: [Impact] When working with ubuntu core or ubuntu core desktop, neither */etc/default/locale* nor */etc/default/keyboard* are modifiable, so it's not possible to set the global keyboard or the global language. This is required to allow to set the GDM language, and the default one during installation. The first half of the solution is to create the folder */etc/writable/default*, and make soft-links from */etc/default/locale* to */etc/writable/default/locale* and from */etc/default/keyboard* to */etc/writable/default/keyboard*, just like it is already being done with */etc/hostname*, */etc/issue*, */etc/localtime*, */etc/motd* and , */etc/timezone*. This solution, unfortunately, isn't complete. Although any application that just reads the files will work, not all of the applications that write to them will; specifically the systemd utilities that set the contents for those files, because they don't open the file directly; instead, they create first the new file in the same folder than the old one, fill its contents, and only then delete the old one and rename the new one. To solve this, systemd in Ubuntu already has several patches that detect if a file is a soft-link, in which case it replaces the old path with the destination one. Currently I have in place a patch for Ubuntu Core Desktop that implements both changes for both */etc/default/locale* and */etc/default/keyboard*. [Test plan] Using *localectl set-lang LANG="xx_YY.UTF-8"* should change the locale to the specified one. Also, *localectl* should return the current locale. [Where problems could occur] In general, applications just read the content of the file and use the DBus interface to set the locale, so only those applications that modify by themselves the */etc/default/keyboard* and/or */etc/default/locale* would present a problem, in which case they would require specific patches. Anyway, those applications neither would work with the current state (with those files in a read-only filesystem). [Other info] For Noble, this will be addressed when we merge systemd v255 from Debian. This is only needed on core, so we don't need to fix for Mantic or Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037281] Re: Shutdown when triggering daemon-reload early in boot
** Summary changed: - Shutdown when triggering daemon-reload eary in boot + Shutdown when triggering daemon-reload early in boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037281 Title: Shutdown when triggering daemon-reload early in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Jammy: New Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. [ Impact ] If a user adds a service that calls `systemctl daemon-reload`, and if this service is started before systemd-udevd. And if the initrd is systemd (the case of Ubuntu Core), then most service will be stopped or cancel, and the machine will mostly shutdown everything and hang. The fix has been backported down to 250 upstream. It is already on kinetic and later. The fix only affects systems where systemd is used in initrd. [ Test Plan ] On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on any system that uses systemd in initrd. Add a systemd service that calls `systemctl daemon-reload`. The service should have `DefaultDependencies=no` in order to start as soon as possible and be enabled. Restart the machine. If fix is not applied, after the service is started, most of units with be shutdown, and the system will be unusable. [ Where problems could occur ] This should affect systems with systemd in initrd. There are risks on systems that have an udev rule in initrd not present in the main system. There are risks on systems that use db_persist in initrd where the device can potentially get dead state. Though this does not seem to happen on Ubuntu Core 22, even though we use db_persist for dev mapper devices. Regression is upstream bug #23429. Commits named "core/device: device_coldplug(): don't set DEVICE_DEAD" and "core/device: do not downgrade device state if it is already enumerated" could be applied as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/544490 is a log from a build with a new livecd-rootfs that spits out more debugging info on failure. + sgdisk binary/boot/disk-uefi.ext4 --print Disk binary/boot/disk-uefi.ext4: 9437184 sectors, 4.5 GiB Sector size (logical): 512 bytes Disk identifier (GUID): CD1DD3AE-E4C8-4C5F-BD64-9236C39B9824 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 9437150 Partitions will be aligned on 2-sector boundaries Total free space is 0 sectors (0 bytes) Number Start (sector)End (sector) Size Code Name 1 235520 9437150 4.4 GiB 8300 12 227328 235519 4.0 MiB 8300 CIDATA 13 342081 1024.0 KiB loader1 142082 10239 4.0 MiB loader2 15 10240 227327 106.0 MiB EF00 + mount_image binary/boot/disk-uefi.ext4 1 + trap clean_loops EXIT + backing_img=binary/boot/disk-uefi.ext4 + local rootpart=1 ++ losetup --show -f -P -v binary/boot/disk-uefi.ext4 + loop_device=/dev/loop5 + '[' '!' -b /dev/loop5 ']' + rootfs_dev_mapper=/dev/loop5p1 + '[' '!' -b /dev/loop5p1 ']' + echo '/dev/loop5p1 is not a block device' /dev/loop5p1 is not a block device + ls -l /dev/loop5p1 /dev/loop5p12 brw--- 1 root root 259, 2 Dec 9 04:16 /dev/loop5p1 brw--- 1 root root 259, 3 Dec 9 04:16 /dev/loop5p12 + exit 1 This clearly shows that: - there are 5 partitions on the image being passed to losetup - after losetup exits, /dev/loop5p1 is not present - after this check fails, an ls of /dev/loop5p* shows devices present for two of the partitions - including /dev/loop5p1 that we were looking for in the first place - but not all 5. So this definitely means we have a race after calling losetup -P. Is this the expected behavior from the kernel? How do we make this race-free? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
** Changed in: ubuntu-settings (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Mantic: In Progress Bug description: [SRU Justification] In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). [Test case] No testing is planned beyond any autopkgtests which may be none (the package itself doesn't have any). This should not be released to -updates on its own, but should be staged in -proposed so any future SRUs needed don't fail to copy due to out-of-date packages. [Where problems may occur] It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
** Tags added: block-proposed-mantic ** Description changed: + [SRU Justification] + In response to LP: #2038964 and due to the timing we have forked ubuntu- raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi-settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). + + [Test case] + No testing is planned beyond any autopkgtests which may be none (the package itself doesn't have any). This should not be released to -updates on its own, but should be staged in -proposed so any future SRUs needed don't fail to copy due to out-of-date packages. + + [Where problems may occur] + It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Mantic: New Bug description: [SRU Justification] In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). [Test case] No testing is planned beyond any autopkgtests which may be none (the package itself doesn't have any). This should not be released to -updates on its own, but should be staged in -proposed so any future SRUs needed don't fail to copy due to out-of-date packages. [Where problems may occur] It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
Failing build had kernel Kernel version: Linux bos03-riscv64-014 5.19.0-1021-generic #23~22.04.1-Ubuntu SMP Thu Jun 22 12:49:35 UTC 2023 riscv64 The build immediately before the first failure had kernel Kernel version: Linux riscv64-qemu-lgw01-069 5.13.0-1019-generic #21~20.04.1-Ubuntu SMP Thu Mar 24 22:36:01 UTC 2022 riscv64 So maybe this is a kernel regression? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
November 16 was 2 days after livecd-rootfs 24.04.4 landed in the noble release pocket, superseding 24.04.2. The code delta between 24.04.2 and 24.04.4 includes removal of support for "legacy" images (SUBPROJECT=legacy) which doesn't apply here; and some reorganization of code related to "preinstalled" images which could affect the riscv64+generic image, that is a preinstalled image using the cpc project, but there were no code changes touching any of the image partitioning code so it's unclear how those code changes could have introduced this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045586] [NEW] livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
Public bug reported: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
Hello Mate, or anyone else affected, Accepted mesa into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Mantic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: Fix Committed Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1485396] Re: impossible to upgrade package from vivid to wily because of maintainer script reference to upstart job without matching init script
Well also this bug was fixed in later releases, the package doesn't fail to unpack on systems with systemd as init ** Changed in: isc-dhcp (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1485396 Title: impossible to upgrade package from vivid to wily because of maintainer script reference to upstart job without matching init script Status in isc-dhcp package in Ubuntu: Fix Released Bug description: The isc-dhcp-server package is not upgradable on a real machine (vs. a chroot) in vivid or wily, because it installs two upstart jobs in the usual debhelper way, but only one of them has a matching init script. As a result, on a system with systemd as init, isc-dhcp-server will fail to even unpack over a running system: Preparing to unpack .../isc-dhcp-server_4.3.1-5ubuntu3_amd64.deb ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused invoke-rc.d: unknown initscript, /etc/init.d/isc-dhcp-server6 not found. dpkg: warning: subprocess old pre-removal script returned error exit status 100 dpkg: trying script from the new package instead ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused invoke-rc.d: unknown initscript, /etc/init.d/isc-dhcp-server6 not found. dpkg: error processing archive /var/cache/apt/archives/isc-dhcp-server_4.3.1-5ubuntu3_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 100 This is because both new and old packages include the following in the prerm: # Automatically added by dh_installinit if [ -x "/etc/init.d/isc-dhcp-server6" ] || [ -e "/etc/init/isc-dhcp-server6.conf" ]; then invoke-rc.d isc-dhcp-server6 stop || exit $? fi # End automatically added section This code will never succeed on a system running systemd. It may be that debhelper's behavior here should be changed. However, as we have two upstart jobs in the package for a reason, I think the more important fix is to split the init script. This will then also require some particular upgrade handling in the prerm since the prerm runs before any new /etc/init.d/isc-dhcp-server6 script would be unpacked. It's also worth noting that this problem was apparently not picked up by the reports about packages missing init scripts; presumably because the isc-dhcp-server has an init script, but not init scripts matching all of the included upstart jobs. https://people.canonical.com/~jhunt/systemd/packages-to-convert/2015-08-17.txt ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: isc-dhcp-server 4.3.1-5ubuntu2.2 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 17 02:58:14 2015 InstallationDate: Installed on 2010-09-24 (1787 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: isc-dhcp UpgradeStatus: Upgraded to wily on 2015-08-17 (0 days ago) modified.conffile..etc.dhcp.dhcpd.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2013-09-19T21:48:37.910820 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1485396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
I think the concerns Andreas raises regarding debian/patches/lp1994165/0002-Handle-SMIME_crlf_copy-return-code.patch are valid. Yes, there are cases where the return value of SMIME_crlf_copy() is currently ignored and this results in other API calls returning success when they should not. However, it appears no one is reporting bugs about this behavior. This means either the code is never called in a way that triggers this wrong behavior; or, it is called, hits the wrong behavior, and the current wrong behavior is being handled up the stack[1]. From an SRU perspective, if no one is reporting bugs about the current behavior, it is better to leave it alone - I would not expect a change in *how* the failure of SMIME_crlf_copy() is handled to result in "good" behavior by the caller - the function still failed and isn't supposed to - so there's basically no upside here within the SRU guidelines, only possible downside. I'm therefore rejecting this upload; please reupload without debian/patches/lp1994165/0002-Handle-SMIME_crlf_copy-return-code.patch. [1] Note that "handled up the stack" could mean "user knows that the behavior is broken in this way and just copes with it rather than filing a bug report in Ubuntu"; or "user encounters this error, is puzzled by it, but doesn't file a bug (maybe they don't know how)". I am not asserting that the current error handling is *good*; only that it is *stable*, and therefore if no one is reporting a bug, it's best not to change the current behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: Won't Fix Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/pull/18876 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1994165] Proposed package upload rejected
An upload of openssl to jammy-proposed has been rejected from the upload queue for the following reason: "Please reupload without debian/patches/lp1994165/0002-Handle-SMIME_crlf_copy-return-code.patch". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: Won't Fix Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/pull/18876 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate
> Excuse me for chiming in so late, but we can test (and even recreate) > the situation by ourselves on our system (and we have systems with > attached crypto hw to it). Someone please update the bug description accordingly with a complete description of the SRU test case. ** Changed in: openssl (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2023545 Title: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: Incomplete Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] Openssl using an engine dumps core upon certificate creation; other operations are probably affected too. Overall, engines are likely mostly unusable. [Test plan] An engine is needed to test the fix and I don't think we have many in the archive. This complicates reproducing the issue. I have been relying on user reports which have been very detailled and helpful. The issue has also been reported independently and with another engine (devcrypto). The issue is fixed in openssl 3.0.8 which landed in lunar. [Where problems could occur] I don't pretend to understand the lifecycle of providers in openssl3 but the patch is simple and has been widely tested by now, including on ubuntu. Thus, I see little chance an unexpected problem would occur with it. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/issues/18578 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy- sru-0001-Release-the-drbg-in-the-global-default-context- befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024 Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not tainted 5.15.0-73-generic #80-Ubuntu Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0) Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708 Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:0 PM:0 RI:0 EA:3 Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 02aa3289f9d0 Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 02aa328a4300 Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 02aa03ff Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 03ffae437c22 03ffec2fe000 Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2 lgr%r11,%r2 03ffae11c700: 4700bc0,0 #03ffae11c704: b24f00a0ear%r10,%a0 >03ffae11c708: 58102018l%r1,24(%r2) 03ffae11c70c: ebaa002dsllg%r10,%r10,32 03ffae11c712: b24f00a1ear%r10,%a1 03ffae11c716: 5910a0d0c%r1,208(%r10) 03ffae11c71a: a7840033brc8,03ffae11c780 Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address: Jun 07 13:06:08 SYSTEM kernel: [<03ffae33242c>] 0x3ffae33242c
[Touch-packages] [Bug 2023545] Proposed package upload rejected
An upload of openssl to jammy-proposed has been rejected from the upload queue for the following reason: "Please reupload without debian/patches/lp1994165/0002-Handle-SMIME_crlf_copy-return-code.patch". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2023545 Title: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: Incomplete Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] Openssl using an engine dumps core upon certificate creation; other operations are probably affected too. Overall, engines are likely mostly unusable. [Test plan] An engine is needed to test the fix and I don't think we have many in the archive. This complicates reproducing the issue. I have been relying on user reports which have been very detailled and helpful. The issue has also been reported independently and with another engine (devcrypto). The issue is fixed in openssl 3.0.8 which landed in lunar. [Where problems could occur] I don't pretend to understand the lifecycle of providers in openssl3 but the patch is simple and has been widely tested by now, including on ubuntu. Thus, I see little chance an unexpected problem would occur with it. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/issues/18578 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy- sru-0001-Release-the-drbg-in-the-global-default-context- befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024 Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not tainted 5.15.0-73-generic #80-Ubuntu Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0) Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708 Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:0 PM:0 RI:0 EA:3 Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 02aa3289f9d0 Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 02aa328a4300 Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 02aa03ff Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 03ffae437c22 03ffec2fe000 Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2 lgr%r11,%r2 03ffae11c700: 4700bc0,0 #03ffae11c704: b24f00a0ear%r10,%a0 >03ffae11c708: 58102018l%r1,24(%r2) 03ffae11c70c: ebaa002dsllg%r10,%r10,32 03ffae11c712: b24f00a1ear%r10,%a1 03ffae11c716: 5910a0d0c%r1,208(%r10) 03ffae11c71a: a7840033brc8,03ffae11c780 Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address: Jun 07 13:06:08 SYSTEM kernel: [<03ffae33242c>] 0x3ffae33242c Jun 07 13:06:08 SYSTEM systemd[1]: Started Process Core Dump (PID 2345/UID 0). Jun 07 13:06:08 SYSTEM systemd-coredump[2350]: Process 2344 (openssl) of
[Touch-packages] [Bug 2033422] Proposed package upload rejected
An upload of openssl to jammy-proposed has been rejected from the upload queue for the following reason: "Please reupload without debian/patches/lp1994165/0002-Handle-SMIME_crlf_copy-return-code.patch". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains THREE changes which are listed in the section below. [Meta] This bug is part of a series of three bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses three issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections (this one) The SRU information has been added to the three bug reports and I am attaching the debdiff here only for all three. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture-dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt that they are within the error margin. This is consistent with the high-concurrency in the benchmark which both saturates CPU, and "hides" latencies that are relatively low. Finally, there are positive reports on github. Unfortunately they are not always completely targeted at these patches only and therefore I will not link directly to them but they have also been encouraging. [Where problems could occur] The change is spread over several patches which touch the
[Touch-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
The directx-headers part of this is easy because it's just a build- dependency of mesa, but mesa itself is a big delta to a library that affects all users of the graphics stack: unlike the kernel, which has both GA and HWE versions where the user can opt out of the rolling kernel updates on the LTS, there is only one mesa package, so the impact of any regressions is higher. I see that the current bug description is in line with the previous update, LP: #2019212; and of course, with respect to hardware enablement, this is an SRU we're going to want to take; but I think it would be best if there were a more explicit test case than just "Install the new mesa on various hw". Do we expect this new mesa to be tested on all certified hardware before it's released to -updates? Is there a feedback mechanism for us to *know* if Certification finds regressions on some of the certified platforms? Is any effort made to check for regressions on non-certified hardware? ** Changed in: mesa (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Incomplete Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted directx-headers into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/directx- headers/1.610.2-2~ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: directx-headers (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: New Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040273] Re: [SRU] Enable support for Caracal Cloud Archive
Hello Corey, or anyone else affected, Accepted software-properties into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software- properties/0.99.22.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: software-properties (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2040273 Title: [SRU] Enable support for Caracal Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Committed Status in software-properties source package in Noble: Fix Released Bug description: Please add support for: cloud-archive:caracal cloud-archive:caracal-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the caracal cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:caracal sudo add-apt-repository cloud-archive:caracal-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2040273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044034] Re: /etc/security/limits.conf memlock changes have no effect
** Changed in: pam (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2044034 Title: /etc/security/limits.conf memlock changes have no effect Status in pam package in Ubuntu: Invalid Bug description: APT reports package as libpam-modules + launchpad says pam is the closest package. Please change package name, if required. Summary says it all. Default of memlock seems to be 64 (which limits.conf suggests means 64k). Changing this setting seems to have no effect. The following entry seems to be correct, and has no effect after reboot, meaning ulimit -l still reports 64. I've tried 128, -1, unlimited, nothing seems to work. Maybe I just misunderstand the correct settings or maybe Ubuntu overrides limits.conf at boot time. My entry... *- memlock unlimited Be great if someone can help me fixing this, as likely it's a simple config file fix somewhere. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common
On Sun, Nov 19, 2023 at 08:02:42PM -, Andrew J. Caines wrote: > the fact remains that processes running as root created a file directly in > /tmp not using a safe *mktemp* process There is no evidence in this bug of unsafe temp file creation in /tmp. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2043711 Title: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common Status in perl package in Ubuntu: Invalid Bug description: During update of ubuntu-drivers-common: Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1. open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 1:0.9.6.2~0.22.04.4 failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59. Preconfiguring packages ... Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1. open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 1:0.9.6.2~0.22.04.4 failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59. /tmp is mounted with noexec because running code from /tmp has been a vulnerability vector for several decades, hence reporting this as a vulnerability in perl-base. This error did not appear to prevent the update of ubuntu-drivers- common and "dpkg --verify ubuntu-drivers-common" returns 0. ___ Attempting to use the package search on this form by clicking the created a modal in which there is an error Sorry, something went wrong with your search. We've recorded what happened, and we'll fix it as soon as possible. (Error ID: OOPS-c80f71590b02908a1187b9f743c53eac) which is repeated with any attempt to search for a package. ___ Submitting this form gives an error "perl-base" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" $ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm $ dpkg -l perl-base Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--=> ii perl-base 5.34.0-3ubuntu1.2 amd64minimal Perl system Looks like a package to me. Nevertheless, using "Did you mean..." offers "perl". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: perl-base 5.34.0-3ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3 Uname: Linux 6.5.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 16 10:08:48 2023 InstallationDate: Installed on 2016-04-23 (2763 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: perl UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2043711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common
On Mon, Nov 20, 2023 at 08:50:05PM -, Andrew J. Caines wrote: > You are of course quite right that the risk associated with a file > created with a "random" six character case-insensitive alphanumeric > suffix and run a moment later is far smaller than more obviously risky > misuses of /tmp. No. The use of a random filename is not a security feature; it is a mechanism to avoid filename *collisions* (either accidental or as part of a denial of service). > or if the code checks for the presence of the file before trying to create > it (which I trust it does) That is not how you securely handle temp files. I'm sorry, but you have a very incomplete understanding of how secure temp file handling works. You have /tmp mounted noexec on your system. This is fine, and supported. It is not a protection against vulnerable system code. It is a mechanism to protect against attackers from writing payload code to /tmp and then executing it. System software must handle temp files under /tmp securely *independently of whether the files it's writing are intended to be executed*. You have something on your system trying to write a file to /tmp and then execute it. That should be fixed. But it's not a bug in perl, and it's not a bug in apt-utils, and it's entirely unclear what code is doing this since this in not part of the standard debconf code path. If you can identify where this is coming from in Ubuntu, we can reassign the bug report and get it fixed. The rest is off-topic for an Ubuntu bug report. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2043711 Title: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common Status in perl package in Ubuntu: Invalid Bug description: During update of ubuntu-drivers-common: Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1. open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 1:0.9.6.2~0.22.04.4 failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59. Preconfiguring packages ... Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1. open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 1:0.9.6.2~0.22.04.4 failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59. /tmp is mounted with noexec because running code from /tmp has been a vulnerability vector for several decades, hence reporting this as a vulnerability in perl-base. This error did not appear to prevent the update of ubuntu-drivers- common and "dpkg --verify ubuntu-drivers-common" returns 0. ___ Attempting to use the package search on this form by clicking the created a modal in which there is an error Sorry, something went wrong with your search. We've recorded what happened, and we'll fix it as soon as possible. (Error ID: OOPS-c80f71590b02908a1187b9f743c53eac) which is repeated with any attempt to search for a package. ___ Submitting this form gives an error "perl-base" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" $ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm $ dpkg -l perl-base Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--=> ii perl-base 5.34.0-3ubuntu1.2 amd64minimal Perl system Looks like a package to me. Nevertheless, using "Did you mean..." offers "perl". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: perl-base 5.34.0-3ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3 Uname: Linux 6.5.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 16
[Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common
This is not a security bug, or a bug at all in perl. Software that executes commands under /tmp is not intrinsically insecure. Various hardening guides recommend mounting /tmp noexec because it's harder for programmers to get security handling of files under /tmp *right*; but an attempt to execute a command under /tmp is not evidence that the programmer has gotten it wrong. The perl package did not create the file /tmp/ubuntu-drivers- common.config.55GJ8b and try to execute it. This was done by some other software that then invoked perl to try to execute it. Perl should not refuse to try to execute the command because the path starts with "/tmp", it should do what it has been asked to do. The specific path in use is suggestive of a debconf config script that has been unpacked as part of the apt "pre-configuration" stage and is being run from a temporary directory. However, the normal interface for this is /usr/sbin/dpkg-preconfigure as invoked via /etc/apt/apt.conf.d/70debconf; and dpkg-preconfigure explicitly specifies to extract the config script to /var/cache/debconf/tmp.ci in order to avoid site policies that restrict execution of binaries under /tmp. So I do not know why this script has been unpacked to /tmp on your system; that does not appear to be the normal flow of operation (and also has not been, for decades). Since there is not a confirmed securtiy bug here, and since I don't know where those files on your system came from, I am closing this bug invalid. If you can provide further information that would show this path is coming from an Ubuntu package, it would be appropriate to reopen the bug report and assign it to the corresponding package. I am also marking this as a public non-security bug. ** Changed in: perl (Ubuntu) Status: New => Invalid ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2043711 Title: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common Status in perl package in Ubuntu: Invalid Bug description: During update of ubuntu-drivers-common: Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1. open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 1:0.9.6.2~0.22.04.4 failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59. Preconfiguring packages ... Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178, line 1. open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 1:0.9.6.2~0.22.04.4 failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59. /tmp is mounted with noexec because running code from /tmp has been a vulnerability vector for several decades, hence reporting this as a vulnerability in perl-base. This error did not appear to prevent the update of ubuntu-drivers- common and "dpkg --verify ubuntu-drivers-common" returns 0. ___ Attempting to use the package search on this form by clicking the created a modal in which there is an error Sorry, something went wrong with your search. We've recorded what happened, and we'll fix it as soon as possible. (Error ID: OOPS-c80f71590b02908a1187b9f743c53eac) which is repeated with any attempt to search for a package. ___ Submitting this form gives an error "perl-base" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" $ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm $ dpkg -l perl-base Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--=> ii perl-base 5.34.0-3ubuntu1.2 amd64minimal Perl system Looks like a package to me. Nevertheless, using "Did you mean..." offers "perl". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: perl-base 5.34.0-3ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3 Uname: Linux 6.5.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 16 10:08:48 2023 InstallationDate: Installed on 2016-04-23 (2763
Re: [Touch-packages] [Bug 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
On Tue, Nov 07, 2023 at 05:34:02PM -, Dave Jones wrote: > Thanks for the quick review! Could someone set up a "mantic" branch Done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Mantic: New Bug description: In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
