[Bug 1934988] Re: Upgrade s390-tools to latest version (2.17.0)
Here's a debdiff for the upgrade, along with one for -signed. ** Patch added: "s390-tools-2.17.0-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+attachment/5510535/+files/s390-tools-2.17.0-0ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934988 Title: Upgrade s390-tools to latest version (2.17.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934988] Re: Upgrade s390-tools to latest version (2.17.0)
With the -signed debdiff ** Patch added: "s390-tools-signed-2.17.0-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+attachment/5510536/+files/s390-tools-signed-2.17.0-0ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934988 Title: Upgrade s390-tools to latest version (2.17.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934988] Re: Upgrade s390-tools to latest version (2.17.0)
Oh, I forgot to specify: I tested the changes in a s390x VM by installing all "s390-tools-*" packages and running their binaries with `--help` as argument as a sanity check. I also tested a system reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934988 Title: Upgrade s390-tools to latest version (2.17.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935972] [NEW] postinst: Rely on needrestart when present on the system
Public bug reported: This patch bypasses the custom restarting logic backed into the postinst script if the needrestart utility is present, as it allows sharing the logic with the rest of the system. It also changes the custom logic to compare the old package version to the current one instead of a hard-coded value. I don't feel particularly strongly about this, so feel free to drop it :) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Patch added: "debdiff" https://bugs.launchpad.net/bugs/1935972/+attachment/5510736/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935972 Title: postinst: Rely on needrestart when present on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1935972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935972] Re: postinst: Rely on needrestart when present on the system
** Attachment added: "V2 addressing comments by bdmurray on IRC." https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1935972/+attachment/5510741/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935972 Title: postinst: Rely on needrestart when present on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1935972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934988] Re: Upgrade s390-tools to latest version (2.17.0)
Thank you for the thorough review! Here's an amended patch with the requested modifications. ** Patch added: "s390-tools-2.17.0-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+attachment/5510749/+files/s390-tools-2.17.0-0ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934988 Title: Upgrade s390-tools to latest version (2.17.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Simon Chopin (schopin) ** Changed in: systemd (Ubuntu Hirsute) Status: New => In Progress ** Changed in: systemd (Ubuntu Hirsute) Assignee: (unassigned) => Simon Chopin (schopin) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Changed in: systemd (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu Impish) Assignee: (unassigned) => Simon Chopin (schopin) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: systemd (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: systemd (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
** Attachment added: "Standalone C program from the upstream test case" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/+attachment/5512579/+files/evp_extra_test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
** Attachment removed: "Standalone C program from the upstream test case" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/+attachment/5512579/+files/evp_extra_test.c ** Attachment added: "Tiny test program" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/+attachment/5513212/+files/test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
Updated description in preparation for SRU requests ** Description changed: Problem description: + + When passing a NULL key to reset AES EVC state, the state wouldn't be completely reset on s390x. https://github.com/openssl/openssl/pull/14900 - + Solution available here: https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8 - Should be applied to all distros where openssl 1.1.1 is included for consistency reason. -> 21.10, 20.04, 18.04. I think not needed for 16.04 anymore + + [Test plan] + + $ sudo apt install libssl-dev + $ gcc test.c -o evc-test -lcrypto -lssl # See https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for the test.c program + $ ./evc-test && echo OK + + [Where problems could occur] + + This patch only touches s390x code paths, so there shouldn't be any regression on other architectures. However, on s390x this could reveal + latent bugs by spreading a NULL key to new code paths. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
** Patch added: "Focal SRU debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/+attachment/5513254/+files/openssl_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
** Patch added: "Bionic SRU debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/+attachment/5513255/+files/openssl_bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
** Patch added: "Hirsute SRU debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/+attachment/5513256/+files/openssl_hirsute.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
** Patch added: "Impish debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/+attachment/5513257/+files/openssl_impish.debdiff ** Attachment removed: "Standalone C program from the upstream test case" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/+attachment/5513213/+files/evp_extra_test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Blocks migration to -updates as the fixed mir package FTBFSe. ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Oh, sorry, I know see how my sentence is ambiguous. I meant that the failing autopkgtests are fixed in the latest version of mir uploaded to -proposed, but that version fails to build because of this bug. So the mentioned fix is *not* for this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
Regarding the bugproxy test case, it should be disregarded: I was the one who originally added it, but then found a much smaller and self- contained test case, and removed the attachment. For some reason, bugproxy didn't like that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
Oh, and thank you very much for the upload, much appreciated :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928780] Re: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid
Hi! Would it be possible to have a repro case for the fixed bug? I'm not familiar with the opencryptoki internals, and the checks are introduced somewhat deep in the call hierarchy from what I can tell. Thanks in advance, Cheers, Simon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928780 Title: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1928780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
The mosquitto test seems to be failing regardless of the version of openssl, I'll take a look at puma. On Tue, Jul 27, 2021 at 1:35 PM Gunnar Hjalmarsson < 1931...@bugs.launchpad.net> wrote: > @Simon: autopkgtest for mosquitto and puma fails on s390x. > > https://people.canonical.com/~ubuntu-archive/proposed- > migration/update_excuses.html#openssl > > Please investigate. > > -- > You received this bug notification because you are a member of Canonical > Foundations Team, which is a bug assignee. > https://bugs.launchpad.net/bugs/1931994 > > Title: > [Ubuntu 20.04] OpenSSL bugs im s390x AES code > > Status in Ubuntu on IBM z Systems: > In Progress > Status in openssl package in Ubuntu: > Fix Committed > Status in openssl source package in Bionic: > New > Status in openssl source package in Focal: > New > Status in openssl source package in Hirsute: > New > Status in openssl source package in Impish: > Fix Committed > > Bug description: > Problem description: > > When passing a NULL key to reset AES EVC state, the state wouldn't be > completely reset on s390x. > https://github.com/openssl/openssl/pull/14900 > > Solution available here: > > https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8 > > Should be applied to all distros where openssl 1.1.1 is included for > consistency reason. > -> 21.10, 20.04, 18.04. > I think not needed for 16.04 anymore > > [Test plan] > > $ sudo apt install libssl-dev > $ gcc test.c -o evc-test -lcrypto -lssl # See > https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 > for the test.c program > $ ./evc-test && echo OK > > [Where problems could occur] > > This patch only touches s390x code paths, so there shouldn't be any > regression on other architectures. However, on s390x this could reveal > latent bugs by spreading a NULL key to new code paths. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928767] Re: [21.10 FEAT] Upgrade openCryptoki to latest version (3.16+)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928767 Title: [21.10 FEAT] Upgrade openCryptoki to latest version (3.16+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1928767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code
Thank you, Gunnar! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs im s390x AES code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938268] [NEW] Run the testcases in autopkgtest
Public bug reported: The upstream tarball ships with some test cases that are supposed to be run against an installed package. They were removed from the .orig tarball as they weren't licensed, but that has since been fixed upstream (mostly, see https://github.com/opencryptoki/opencryptoki/pull/430 for the last problematic file). It would be a good thing to run the tests in autopkgtest. ** Affects: opencryptoki (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938268 Title: Run the testcases in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/1938268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938268] Re: Run the testcases in autopkgtest
** Tags added: fr-1527 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938268 Title: Run the testcases in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/1938268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853271] Re: [21.10 FEAT] Valgrind support for new s390 hardware
Here's a debdiff incorporating the above patchset into our version of Valgrind ** Information type changed from Private to Public ** Changed in: valgrind (Ubuntu) Status: Expired => In Progress ** Changed in: valgrind (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) ** Patch added: "z15 support debdiff" https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1853271/+attachment/5514350/+files/valgrind.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853271 Title: [21.10 FEAT] Valgrind support for new s390 hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853271] Re: [21.10 FEAT] Valgrind support for new s390 hardware
My apologies, it turns out I didn't actually test-build on s390x. After doing so, the build fails. I have a potential fix, waiting on the build to finish. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853271 Title: [21.10 FEAT] Valgrind support for new s390 hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853271] Re: [21.10 FEAT] Valgrind support for new s390 hardware
Fixed version (some helper functions and macros were missing) ** Patch added: "valgrind.debdiff" https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1853271/+attachment/5514357/+files/valgrind.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853271 Title: [21.10 FEAT] Valgrind support for new s390 hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928780] Re: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid
Here's a debdiff for the Hirsute SRU. ** Patch added: "opencryptoki_hirsute.debdiff" https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/1928780/+attachment/5514578/+files/opencryptoki_hirsute.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928780 Title: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1928780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928780] Re: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid
** Description changed: - The Opencryptoki Soft token does not check if an EC key is valid when an - EC key is created via C_CreateObject, nor when C_DeriveKey is used with - ECDH public data. This may allow one to perform Invalid Curve Attacks. + [Description] + The Opencryptoki Soft token does not check if an EC key is valid when an EC key is created via C_CreateObject, nor when C_DeriveKey is used with ECDH public data. This may allow one to perform Invalid Curve Attacks. Fix: https://github.com/opencryptoki/opencryptoki/commit/4e3b43c3d8844402c04a66b55c6c940f965109f0 (SOFT: Check the EC Key on C_CreateObject and C_DeriveKey) This commit should apply smooth on top of OCK 3.16.0, but also on OCK 3.15.0 or 3.15.1. EC support has been introduced in the Soft token with OCK 3.15.0. So all OCK versions >= 3.15.0 are affected. Earlier OCK releases are not affected. This problem need only to be fixed with 21.04 wherer 3.15.1 is included. + + [Test Plan] + + ?? + + + [Where problems could occur] + + Even assuming the underlying code is perfectly correct, the update + increases the API surface of the library slightly, which could provoke + namespace clashes where none existed before. + + If the EC checking code isn't correct, the soft token implementation + might reject some valid keys that would have previously gone through. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928780 Title: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1928780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928780] Re: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid
The backported package is available at the following PPA: https://launchpad.net/~schopin/+archive/ubuntu/test- ppa/+sourcepub/12592922/+listing-archive-extra The version is 3.15.1+dfsg-0ubuntu1.1~ppa2, but it's the same code otherwise. Waiting for repro before poking someone to upload the SRU package :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928780 Title: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1928780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928780] Re: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid
Attached is a standalone version of the test file. I'm having trouble with my VMs so I won't update the description just yet with steps to confirm the bug and its fix just yet, but it's looking pretty good. Small nit with the patch : there's a typo in the name of the function ;-) ** Attachment added: "test.c" https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/1928780/+attachment/5514907/+files/test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928780 Title: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1928780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1080849] Re: package libchromaprint-tools (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/fpcalc', which is also in package libchromaprint0 0.7-0~ppa1~quantal1
This bug is not in the Ubuntu package but rather in a PPA package, apparently setup by the upstream author, which conflicts with ours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1080849 Title: package libchromaprint-tools (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/fpcalc', which is also in package libchromaprint0 0.7-0~ppa1~quantal1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromaprint/+bug/1080849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086001] Re: package libchromaprint-tools 0.6-2 crashed after wake from suspend
*** This bug is a duplicate of bug 1080849 *** https://bugs.launchpad.net/bugs/1080849 ** This bug has been marked a duplicate of bug 1080849 package libchromaprint-tools (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/fpcalc', which is also in package libchromaprint0 0.7-0~ppa1~quantal1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086001 Title: package libchromaprint-tools 0.6-2 crashed after wake from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromaprint/+bug/1086001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025295] Re: py.test-3 crashed with SIGSEGV in kill()
I've just tried to reproduce this bug on a quantal chroot on my Debian box, but the test run went absolutely fine. Are you sure you used pristine pytest or codespeak packages ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025295 Title: py.test-3 crashed with SIGSEGV in kill() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pytest/+bug/1025295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006709] Re: [MIR] pytest, codespeak-lib
Hi ! I'm the current maintainer of pytest in Debian, and have lend a hand a couple of times with codespeak-lib as well. I haven't looked at codespeaklib testsuite yet, but it would not surprise me that it is intended to be run by pytest, since pytest was originately part of codespeak-lib and upstream is still the same on both projects. I've raised the question of circular build-deps in #debian-mentors, and it seems to be a very bad idea, because unfortunate circumstances would force a manual intervention on the buildds if the maintainers both screw up at approximately the same time. In our case it actually not such a big problem for Debian since the arch:all binary packages are all built by the maintainer, but I assume you guys rebuild every thing, right ? What I would do is run the test suite using the DEP8 stuff, which is NOT run at build time and thus is less likely to cause problem. It seems that you already have some infrastructure in place for it as mentioned in https://lists.debian.org/debian-devel/2012/06/msg00457.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006709 Title: [MIR] pytest, codespeak-lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/codespeak-lib/+bug/1006709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080759] [NEW] pristine-tar autopkgtests fail against glibc 2.40-1ubuntu3
Public bug reported: There are a lot of failures, so here's a link to the full logs instead. https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-oracular/oracular/s390x/p/pristine-tar/20240914_172257_16930@/log.gz ** Affects: glibc (Ubuntu) Importance: Critical Status: New ** Affects: pristine-tar (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Importance: Undecided => Critical ** Changed in: pristine-tar (Ubuntu) Importance: Critical => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080759 Title: pristine-tar autopkgtests fail against glibc 2.40-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2080759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974135] [NEW] Sync libcrypt-openssl-rsa-perl 0.32-2 (main) from Debian unstable (main)
Public bug reported: Please sync libcrypt-openssl-rsa-perl 0.32-2 (main) from Debian unstable (main) The delta is just us being ahead of Debian for the OpenSSL transition, they've since catched up. Changelog entries since current kinetic version 0.32-1ubuntu2: libcrypt-openssl-rsa-perl (0.32-2) unstable; urgency=medium * Team upload. [ Simon Chopin ] * Cherry-pick an OpenSSL fix (LP: #1945798) -- gregor herrmann Thu, 13 Jan 2022 19:55:56 +0100 ** Affects: libcrypt-openssl-rsa-perl (Ubuntu) Importance: Wishlist Status: New ** Changed in: libcrypt-openssl-rsa-perl (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974135 Title: Sync libcrypt-openssl-rsa-perl 0.32-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcrypt-openssl-rsa-perl/+bug/1974135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1947588] Re: Infinite Loop in OpenSSL s_server
Thanks for the follow up! I'll try to fold the fix for this in the next Jammy SRU, I don't know about other releases yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947588 Title: Infinite Loop in OpenSSL s_server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972853] Re: [MIR] lib*-perl
** Description changed: - TBD + [Availability] + The packages libxs-parse-sublike-perl, libobject-pad-perl, libindirect-perl, libunicode-escape-perl, libunicode-string-perl are already in Ubuntu universe and build for the architectures they're designed to work on. - All of those new dependencies are maintained by the Debian Perl Group - (pkg-perl-maintainers). + They currently build and work for the following architectures: - Needed in "main" as new dependencies of licensecheck: - * libxs-parse-sublike-perl - * libobject-pad-perl - * libindirect-perl + libxs-parse-sublike-perl: amd64 arm64 armhf ppc64el riscv64 s390x + libobject-pad-perl: amd64 arm64 armhf ppc64el riscv64 s390x + libindirect-perl: amd64 arm64 armhf ppc64el riscv64 s390x + libunicode-string-perl: amd64 arm64 armhf i386 ppc64el riscv64 s390x + libunicode-escape-perl: all - and sphinx: - * libunicode-escape-perl - * libunicode-string-perl + Links to packages: + https://launchpad.net/ubuntu/+source/libxs-parse-sublike-perl + https://launchpad.net/ubuntu/+source/libobject-pad-perl + https://launchpad.net/ubuntu/+source/libindirect-perl + https://launchpad.net/ubuntu/+source/libunicode-string-perl + https://launchpad.net/ubuntu/+source/libunicode-escape-perl + + [Rationale] + The packages libxs-parse-sublike-perl, libobject-pad-perl and libindirect-perl are required in Ubuntu main as new dependencies of the licensecheck (directly or transitively) + The packages libunicode-escape-perl and libunicode-string-perl are required in Ubuntu main as new dependencies of the sphinx package. + + There are no definite deadlines for this MIR. + + [Security] + libxs-parse-sublike-perl: I couldn't find any security issue for this package in the past. + libobject-pad-perl: I couldn't find any security issue for this package in the past. + libindirect-perl: I couldn't find any security issue for this package in the past. + libunicode-string-perl: I couldn't find any security issue for this package in the past. + libunicode-escape-perl: I couldn't find any security issue for this package in the past. + + All packages only ship Perl binary extensions or source modules, along + with documentation. There are no binaries, services, recurring jobs. + + + [Quality assurance - function/usage] + The packages can be correctly imported in a Perl script after installation. + + [Quality assurance - maintenance] + The packages are maintainted well in Debian, as they are under the umbrella of the Perl team. + Most don't have any open bugs: + + https://bugs.debian.org/src:libindirect-perl + https://bugs.launchpad.net/ubuntu/+source/libindirect-perl/+bug + https://bugs.debian.org/src:libunicode-escape-perl + https://bugs.launchpad.net/ubuntu/+source/libunicode-escape-perl/+bug + https://bugs.debian.org/src:libunicode-string-perl + https://bugs.launchpad.net/ubuntu/+source/libunicode-string-perl/+bug + https://bugs.debian.org/src:libxs-parse-sublike-perl + https://bugs.launchpad.net/ubuntu/+source/libxs-parse-sublike-perl/+bug + + The libobject-pad-perl package has one bug opened: + + https://bugs.launchpad.net/ubuntu/+source/libobject-pad-perl/+bug + https://bugs.debian.org/src:libobject-pad-perl + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006658 + + The issue described in the bug doesn't seem to be triggered by the test + suite anymore. + + [Quality assurance - testing] + + The packages all include a test suite that is run both at runtime and as + autopkgtests. + + [Quality assurance - packaging] + ALl packages has watchfiles that work. + + They appear relatively lintian-clean, with some more warnings to the + libunicode* packages due to the packaging not having been refreshed in a while. + + None of them have any overrides. + + Link to the Lintian runs on Debian (relevant as there are no Ubuntu + delta): + + https://lintian.debian.org/sources/libindirect-perl + https://lintian.debian.org/sources/libxs-parse-sublike-perl + https://lintian.debian.org/sources/libobject-pad-perl + https://lintian.debian.org/sources/libunicode-string-perl + https://lintian.debian.org/sources/libunicode-escape-perl + + These packages do not rely on obsolete or about to be demoted packages. + These packages have no python2 or GTK2 dependencies + + The packages will not be installed by default + + Packaging and build are easy: + https://salsa.debian.org/perl-team/modules/packages/libindirect-perl/-/blob/master/debian/rules + https://salsa.debian.org/perl-team/modules/packages/libxs-parse-sublike-perl/-/blob/master/debian/rules + https://salsa.debian.org/perl-team/modules/packages/libobject-pad-perl/-/blob/master/debian/rules + https://salsa.debian.org/perl-team/modules/packages/libunicode-string-perl/-/blob/master/debian/rules + + The packaging for libunicode-escape-perl is a bit outdated: + https://salsa.debian.org/perl-team/modules/packages/libunicode-escape-perl/-/blob/master/debian/rules + + [UI standards] + These are not applications but r
[Bug 1975347] Re: Backport OPENSSL_strcasecmp fixes from 3.0 branch
I *think* this is a duplicate of https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037 but I'll keep it separate for now as the API used to trigger the issue isn't the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975347 Title: Backport OPENSSL_strcasecmp fixes from 3.0 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1975347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975347] Re: Backport OPENSSL_strcasecmp fixes from 3.0 branch
*** This bug is a duplicate of bug 1974037 *** https://bugs.launchpad.net/bugs/1974037 ** This bug has been marked a duplicate of bug 1974037 openssl: EVP_EC_gen() segfault without init -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975347 Title: Backport OPENSSL_strcasecmp fixes from 3.0 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1975347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971650] Re: wrong check for "server" in libssl3.postinst
FWIW, Debian just scrapped the postinst entirely, advising users to use needrestart or checkrestart instead. In my upcoming merge I'll revert the deletion, but I'd be happy to go back and remove that part of the delta once I understand how all the pieces fit together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971650 Title: wrong check for "server" in libssl3.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974035] Re: openssl: Merge 3.0.3-4 from Debian unstable
Here's a MP using git-ubuntu (well, with a lot of manual fiddling): https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153 I'd appreciate it the upload would be using rich history support: https://lists.ubuntu.com/archives/ubuntu-devel/2021-October/041649.html as the delta is fairly substantial, this would make future merges probably easier. ** Merge proposal linked: https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974035 Title: openssl: Merge 3.0.3-4 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974037] Re: openssl: EVP_EC_gen() segfault without init
** Merge proposal linked: https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974037 Title: openssl: EVP_EC_gen() segfault without init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973041] Re: llvm-toolchain-13: please backport Risc-V .insn directive support
Here's a merge of llvm-toolchain-13 that includes this patch, along with another one for https://bugs.launchpad.net/ubuntu/+source/llvm- toolchain-13/+bug/1973041 Build in progress there: https://launchpad.net/~schopin/+archive/ubuntu/rustc-1.59/+sourcepub/13636485/+listing- archive-extra ** Patch added: "llvm-13.debdiff" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973041/+attachment/5592302/+files/llvm-13.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973041 Title: llvm-toolchain-13: please backport Risc-V .insn directive support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974037] Re: openssl: EVP_EC_gen() segfault without init
** Changed in: openssl (Ubuntu Kinetic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974037 Title: openssl: EVP_EC_gen() segfault without init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974037] Re: openssl: EVP_EC_gen() segfault without init
Attached is a debdiff for the Jammy changes. I'm still working on Kinetic as this will be folded into the merge, but I still need to do some more work as some new patches have surfaced upstream since then, as well as a new Debian revision. I feel the Jammy SRU should still move forward. Note that the patchset is consequent as upstream has changed their approach to the issue a couple of times, now settling into reimplementing the string comparison functions entirely rather than relying on a C locale. This last approach has the benefit of not requiring initialization, which seems to have been the cause of all the regressions observed so far with the first solution. The patches for that last approach haven't made their way to Debian yet, AFAICT. ** Patch added: "openssl.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+attachment/5592652/+files/openssl.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974037 Title: openssl: EVP_EC_gen() segfault without init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974037] Re: openssl: EVP_EC_gen() segfault without init
** Description changed:
- Imported from Debian bug http://bugs.debian.org/1010958:
+ [Impact]
+
+ The fix for
+ https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997 has
+ broken some code paths as the new string comparison functions now need
+ initialization, triggering segafults.
+
+ The provided debdiff fixes the immediate issue and also settles on a new
+ implementation not requiring the initialization in the first place.
+
+ [Test Plan]
+
+ Since this is a regression fix, we first need to check that the original
+ bug hasn't cropped up again:
+
+ sudo locale-gen tr_TR.UTF-8
+ LANG=C curl https://ubuntu.com/ > /dev/null # This work
+ LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This should work as
well
+
+ For the regression itself:
+
+ sudo apt install libssl-dev
+ cat < openssl_test.c
+ #include
+ int main()
+ {
+ EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
+ }
+ EOF
+ gcc openssl_test.c -lcrypto -lssl -o openssl_test
+ ./openssl_test
+
+
+ [Where problems could occur]
+
+ This new patch set is relatively massive, on top of another massive one.
+ Some new regressions could crop up of a similar kind. Furthermore, the
+ homegrown string comparison function could be buggy, leading to algorithm
name mismatches.
+
+ [Other info]
+
+ The patches all come from upstream and have been merged on their 3.0
+ maintenance branch.
+
+ [Original report]
Source: sscg
Version: 3.0.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=sscg&ver=3.0.2-1%2Bb1
...
1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11
SIGSEGV
04:32:21 MALLOC_PERTURB_=87
/<>/obj-x86_64-linux-gnu/generate_rsa_key_test
...
Summary of Failures:
1/10 generate_rsa_key_test FAIL 0.01s killed by signal
11 SIGSEGV
Ok: 9
Expected Fail: 0
Fail: 1
Unexpected Pass:0
Skipped:0
Timeout:0
dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8
MESON_TESTTHREADS=4 ninja test returned exit code 1
make: *** [debian/rules:6: binary-arch] Error 25
This has also been reported on the openssl-users mailing list:
https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974037
Title:
openssl: EVP_EC_gen() segfault without init
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973041] Re: llvm-toolchain-13: please backport Risc-V .insn directive support
Refreshed version of the same thing, with the merge fixed, adding Replaces/Breaks fields due to the Ubuntu/Debian divergence on which package ships the new static libraries. I used the dh-exec mechanism for the i386 exception as it is what is used in the current Salsa 13 branch for their grpc-unable architectures, thus it'll eventually reduce the delta. The .insn patch has been forwarded to Debian: https://salsa.debian.org/pkg-llvm-team/llvm- toolchain/-/merge_requests/89 ** Patch added: "llvm-13.debdiff" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973041/+attachment/5592872/+files/llvm-13.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973041 Title: llvm-toolchain-13: please backport Risc-V .insn directive support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971128] Re: z3 is incorrectly marked as a MIR candidate
** Summary changed: - [MIR] z3 + z3 is incorrectly marked as a MIR candidate ** Description changed: - TDB by foundations. + rustc pulls llvm-13 into main (the llvm-toolchain-13 being already + partially seeded, it doesn't raise any issue), and z3 is a dependency of + it. ** Also affects: rustc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971128 Title: z3 is incorrectly marked as a MIR candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1971128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971128] Re: z3 is incorrectly marked as a MIR candidate
Since we're shipping rustc primarily as a packaging tool, we can simply
demote the llvm-13 Recommends to a Suggests, and instead add it to rust-
all (which is in universe)
** Also affects: z3 (Ubuntu Kinetic)
Importance: Undecided
Status: Incomplete
** Also affects: rustc (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: z3 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: rustc (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: z3 (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: rustc (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: rustc (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: z3 (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: z3 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: z3 (Ubuntu Kinetic)
Status: Incomplete => Invalid
** Changed in: rustc (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: rustc (Ubuntu Kinetic)
Status: New => Confirmed
** Changed in: rustc (Ubuntu Jammy)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971128
Title:
z3 is incorrectly marked as a MIR candidate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1971128/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level
** Description changed: - openssl.cnf as provided misses some directive, which make it a bit - difficult to change security level, which since openssl 3 disables SHA1 - signatures. + [Impact] + + The OpenSSL 3.0 lead to a lot of broken setups. Some of them are + regressions, but others are simply broken due to the use of outdated + algorithms, such as SHA-1 signature on certificates. Changing the + security level is a common action to identify and work around such + cases, and as such the user should be able to change it easily in the + default config file. + + The fix is to partially revert our delta that ignored a Debian patch: + instead of ignoring the patch entirely, we modify it to only affect the + default configuration file, and in a way that matches our patchset. + Using this approach will allow us to pick up on Debian's changes more + easily during subsequent merges. + + [Test Plan] + + To easily check that the setting is taken into account, one can use + 'openssl ciphers -s' + + $ openssl ciphers -v -s | wc -l # Uses the default value + 30 + $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=2' | wc -l + 30 + $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=3' | wc -l + 24 + $ vim /etc/ssl/openssl.cf # edit the config file to bump the seclevel to 3 + $ openssl ciphers -v -s | wc -l # Uses the new value from the config file + 24 + + [Where problems could occur] + + The changes could break the overall configuration of OpenSSL! + + [Origin report] + openssl.cnf as provided misses some directive, which make it a bit difficult to change security level, which since openssl 3 disables SHA1 signatures. See also this Debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1010360 and the committed fix: https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4 Can you please sync this change in Ubuntu openssl? This way one should just add a single directive to change the security level. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972056 Title: [openssl3] please sync openssl.cnf to ease changing security level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971128] Re: z3 is incorrectly marked as a MIR candidate
** Patch added: "rustc.debdiff" https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1971128/+attachment/5593815/+files/rustc.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971128 Title: z3 is incorrectly marked as a MIR candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1971128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947588] Re: Infinite Loop in OpenSSL s_server
** Description changed: + [Impact] + + The TLS test server `openssl s_server` can very easily be led into an + infinite loop if configured with incompatible settings and used via + DTLS. This makes it harder to test one's TLS configuration. + + [Test plan] + + In one session: + $ openssl s_server -nocert -psk 01020304 -dtls1 + In parallel: + $ openssl s_client -dtls1 -psk 01020304 + + The server session will enter an infinite loop: + Using default temp DH parameters + ACCEPT + ERROR + 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: + ERROR + 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: + ERROR + ... etc... + + [Where problems could occur] + + The patch is fairly self-contained, so regressions should only occur in + the `openssl s_server` application, and not in the libssl or libcrypto + libraries. + However, the patch could break said server, which might be used in e.g. + autopkgtests. + + [Original report] Launching openssl s_server as follows: $ openssl s_server -nocert -psk 01020304 -dtls1 And using openssl s_client to connect to it like this: $ openssl s_client -dtls1 -psk 01020304 Results in s_server entering an infinite loop: - Using default temp DH parameters ACCEPT ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR ...and so on... I have confirmed that upstream OpenSSL does not have this issue in a default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug with these commands (https://github.com/openssl/openssl/issues/16707) and it was while working on the fix for that issue (https://github.com/openssl/openssl/pull/16838) that I noticed this problem in the Ubuntu packages. $ lsb_release -rd - Description: Ubuntu 21.04 - Release: 21.04 + Description: Ubuntu 21.04 + Release: 21.04 $ apt-cache policy openssl openssl: Installed: 1.1.1j-1ubuntu3.5 Candidate: 1.1.1j-1ubuntu3.5 Version table: *** 1.1.1j-1ubuntu3.5 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1j-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages $ openssl version -a - OpenSSL 1.1.1j 16 Feb 2021 + OpenSSL 1.1.1j 16 Feb 2021 built on: Mon Aug 23 17:02:39 2021 UTC platform: debian-amd64 - options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr) + options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr) compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 OPENSSLDIR: "/usr/lib/ssl" ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1" Seeding source: os-specific -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947588 Title: Infinite Loop in OpenSSL s_server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976295] [NEW] astroquery: Autopkgtests failure due to trying to write to /usr/lib
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1012125:
Source: astroquery
Version: 0.4.6+dfsg-2
Severity: serious
Justification: RT
X-Debbugs-Cc: simon.cho...@canonical.com
Hi,
The autopkgtests for 0.4.6+dfsg-2 fail with attempts to write to
locations in /usr/lib, preventing the package from migrating to testing.
From
https://ci.debian.net/data/autopkgtest/unstable/amd64/a/astroquery/21778465/log.gz
:
=== short test summary info
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_download_product_by_calibration
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_download_product_by_product_type
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_get_postcard
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_cone_search
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_cone_search_coords
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_get_artifact
= 6 failed, 973 passed, 588 skipped, 2 xfailed, 150 warnings in 53.54s =
Details of the first failure:
__ TestESAHubble.test_download_product_by_calibration
__
self =
def test_download_product_by_calibration(self):
parameters = {'observation_id': "J6FL25S4Q",
'cal_level': "RAW",
'filename': "J6FL25S4Q.vot",
'verbose': True}
ehst = ESAHubbleClass(self.get_dummy_tap_handler())
> ehst.download_product(observation_id=parameters['observation_id'],
calibration_level=parameters['cal_level'],
filename=parameters['filename'],
verbose=parameters['verbose'])
/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py:101:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/astroquery/esa/hubble/core.py:106: in
download_product
response = self._request('GET', self.data_url, save=True, cache=True,
/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py:39:
in get_mockreturn
shutil.copy(response + '.test', response)
/usr/lib/python3.10/shutil.py:417: in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
src =
'/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/data/J6FL25S4Q.vot.test'
dst =
'/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/data/J6FL25S4Q.vot'
[snip]
with open(src, 'rb') as fsrc:
try:
> with open(dst, 'wb') as fdst:
E PermissionError: [Errno 13] Permission denied:
'/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/data/J6FL25S4Q.vot'
/usr/lib/python3.10/shutil.py:256: PermissionError
** Affects: astroquery (Ubuntu)
Importance: Undecided
Status: New
** Affects: astroquery (Debian)
Importance: Undecided
Status: New
** Tags: update-excuse
** Bug watch added: Debian Bug tracker #1012125
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012125
** Changed in: astroquery (Debian)
Remote watch: None => Debian Bug tracker #1012125
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976295
Title:
astroquery: Autopkgtests failure due to trying to write to /usr/lib
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/astroquery/+bug/1976295/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976299] Re: hashlib.algorithms_available lists algorithms that cannot be used
** Tags added: transition-openssl3-jj -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976299 Title: hashlib.algorithms_available lists algorithms that cannot be used To manage notifications about this bug go to: https://bugs.launchpad.net/python3/+bug/1976299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976464] [NEW] ruby-tty-screen: Autopkgtests fail on s390x
Public bug reported: Imported from Debian bug http://bugs.debian.org/1012204: Source: ruby-tty-screen Version: 0.7.1-2 Severity: normal X-Debbugs-Cc: scho...@ubuntu.com Hi, The autopkgtests for this package fail on s390x, apparently due to an endianness issue. See https://ci.debian.net/data/autopkgtest/unstable/armhf/r/racket-mode/21881667/log.gz There's a patch available upstream: https://github.com/piotrmurach/tty- screen/commit/dba351b178ae06b56985cc77a291918a0fc4aff4 I intend to post a Salsa MR to fix the issue. ** Affects: ruby-tty-screen (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-tty-screen (Debian) Importance: Undecided Status: New ** Tags: update-excuse ** Bug watch added: Debian Bug tracker #1012204 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012204 ** Changed in: ruby-tty-screen (Debian) Remote watch: None => Debian Bug tracker #1012204 ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976464 Title: ruby-tty-screen: Autopkgtests fail on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-tty-screen/+bug/1976464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976464] Re: ruby-tty-screen: Autopkgtests fail on s390x
*** This bug is a duplicate of bug 1968831 *** https://bugs.launchpad.net/bugs/1968831 ** This bug has been marked a duplicate of bug 1968831 ruby-tty-screen: endianness bug detected by autopkgtest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976464 Title: ruby-tty-screen: Autopkgtests fail on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-tty-screen/+bug/1976464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976610] [NEW] ruby-gitlab-fog-azure-rm: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block
Public bug reported: Imported from Debian bug http://bugs.debian.org/996235: [, ] ** Affects: ruby-gitlab-fog-azure-rm (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-gitlab-fog-azure-rm (Debian) Importance: Undecided Status: New ** Tags: update-excuse ** Bug watch added: Debian Bug tracker #996235 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996235 ** Changed in: ruby-gitlab-fog-azure-rm (Debian) Remote watch: None => Debian Bug tracker #996235 ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976610 Title: ruby-gitlab-fog-azure-rm: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-gitlab-fog-azure-rm/+bug/1976610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976622] [NEW] libisal: FTBFS on big-endian architectures
Public bug reported: Imported from Debian bug http://bugs.debian.org/1012262: Source: libisal Version: 2.30.0-4 Severity: normal X-Debbugs-Cc: scho...@ubuntu.com This package fails to build on big-endian architectures, notably s390x. There's a fix available upstream: https://github.com/intel/isa-l/commit/d3cfb2fb772e375cf2007e484e0a6ec0c6a7c993 ** Affects: fastp (Ubuntu) Importance: Undecided Status: Invalid ** Affects: libisal (Ubuntu) Importance: Undecided Status: New ** Affects: libisal (Debian) Importance: Undecided Status: New ** Tags: update-excuse ** Bug watch added: Debian Bug tracker #1012262 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012262 ** Changed in: libisal (Debian) Remote watch: None => Debian Bug tracker #1012262 ** Also affects: fastp (Ubuntu) Importance: Undecided Status: New ** Changed in: fastp (Ubuntu) Status: New => Invalid ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976622 Title: libisal: FTBFS on big-endian architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fastp/+bug/1976622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976622] Re: libisal: FTBFS on big-endian architectures
Adding fastp to the affected packages as this blocks its transition from -proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976622 Title: libisal: FTBFS on big-endian architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fastp/+bug/1976622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971128] Re: z3 is incorrectly marked as a MIR candidate
The chain is rustc -> llvm-13 -> llvm-13-dev -> z3, so that's still an issue with Jammy, I think. Reopening :) ** Changed in: rustc (Ubuntu Jammy) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971128 Title: z3 is incorrectly marked as a MIR candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1971128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071789] [NEW] rust-reqwest: some tests fail when a proxy is set
Public bug reported: The following tests started failing in the Ubuntu autopkgtest environment, most likely due to the proxy. 30927s overridden_dns_resolution_with_gai 30927s overridden_dns_resolution_with_gai_multiple 30927s overridden_dns_resolution_with_hickory_dns 30927s overridden_dns_resolution_with_hickory_dns_multiple It's presumably an upstream regression, and/or a proxy bug, but coming up with an upstream fix is probably too involved for me to handle, so I'll just skip the tests instead. ** Affects: rust-reqwest (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Description changed: - The following tests fail in the Ubuntu autopkgtest environment, due to - the proxy. + The following tests started failing in the Ubuntu autopkgtest + environment, most likely due to the proxy. 30927s overridden_dns_resolution_with_gai 30927s overridden_dns_resolution_with_gai_multiple 30927s overridden_dns_resolution_with_hickory_dns 30927s overridden_dns_resolution_with_hickory_dns_multiple - It's presumably an upstream bug, and/or a proxy bug, but coming up with - an upstream fix is probably too involved for me to handle, so I'll just - skip the tests instead. + It's presumably an upstream regression, and/or a proxy bug, but coming + up with an upstream fix is probably too involved for me to handle, so + I'll just skip the tests instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071789 Title: rust-reqwest: some tests fail when a proxy is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-reqwest/+bug/2071789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071789] Re: rust-reqwest: some tests fail when a proxy is set
After a bit more investigation, the tests actually *always* failed, except once, maybe because the random port chosen happened to match some whitelist or something? In any case, the tests are likely *not* supposed to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071789 Title: rust-reqwest: some tests fail when a proxy is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-reqwest/+bug/2071789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068543] Re: Config variable $nrconf{restart} is no longer accurate: it always restarts
** Changed in: needrestart (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068543
Title:
Config variable $nrconf{restart} is no longer accurate: it always
restarts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2068543/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067800] Re: needrestart should avoid restarting runner-provisioner.service
This fix will wait until the current SRU gets through the door. ** Changed in: needrestart (Ubuntu Noble) Status: New => In Progress ** Changed in: needrestart (Ubuntu Noble) Status: In Progress => Triaged ** Changed in: needrestart (Ubuntu Noble) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067800 Title: needrestart should avoid restarting runner-provisioner.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2067800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
Reverting the tag while waiting for verification from the Core team (pinged out of band) ** Tags removed: verification-done-noble ** Tags added: verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072342] [NEW] giada FTBFS with RtAudio 6
Public bug reported: Imported from Debian bug http://bugs.debian.org/1073997: Source: giada Version: 0.22.0-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=giada&ver=0.22.0-4%2Bb2 ... /<>/src/core/kernelAudio.cpp: In member function ‘int giada::m::KernelAudio::openDevice(const giada::m::Conf::Data&)’: /<>/src/core/kernelAudio.cpp:182:16: error: ‘RtAudioError’ does not name a type; did you mean ‘RtAudioErrorType’? 182 | catch (RtAudioError& e) |^~~~ |RtAudioErrorType ... ** Affects: giada (Ubuntu) Importance: Undecided Status: New ** Affects: giada (Debian) Importance: Undecided Status: New ** Tags: ftbfs update-excuse ** Bug watch added: Debian Bug tracker #1073997 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073997 ** Changed in: giada (Debian) Remote watch: None => Debian Bug tracker #1073997 ** Tags added: ftbfs update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072342 Title: giada FTBFS with RtAudio 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giada/+bug/2072342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072342] Re: giada FTBFS with RtAudio 6
I'll have to stop the investigation on this, but with the attached debdiff I managed to move the build forward, it now fails with: /usr/bin/ld: CMakeFiles/giada.dir/src/deps/juce/modules/juce_core/juce_core.cpp.o: warning: relocation against `_ZN4juce20juce_compilationTimeE' in read-only section `.text' /usr/bin/ld: CMakeFiles/giada.dir/src/deps/juce/modules/juce_core/juce_core.cpp.o: in function `juce::StringArray::addTokens(juce::StringRef, bool)': /usr/src/giada-0.22.0-4build3/src/deps/juce/modules/juce_core/text/juce_StringArray.cpp:343:(.text+0xa9dc0): undefined reference to `juce::juce_compilationDate' /usr/bin/ld: CMakeFiles/giada.dir/src/deps/juce/modules/juce_core/juce_core.cpp.o: in function `juce::Time::getCompilationDate()': /usr/src/giada-0.22.0-4build3/src/deps/juce/modules/juce_core/time/juce_Time.cpp:616:(.text+0xa9e13): undefined reference to `juce::juce_compilationTime' /usr/bin/ld: warning: creating DT_TEXTREL in a PIE ** Patch added: "giada.debdiff" https://bugs.launchpad.net/ubuntu/+source/giada/+bug/2072342/+attachment/5795390/+files/giada.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072342 Title: giada FTBFS with RtAudio 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giada/+bug/2072342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072472] [NEW] mescc-tools FTBFS on ppc64el
Public bug reported: mescc-tools fails to build on ppc64el with the following error: test/test13/hello.sh + ./bin/M1 --little-endian --architecture ppc64le -f test/test13/hello.M1 -o test/test13/hello.hex2 + ./bin/hex2 --little-endian --architecture ppc64le --base-address 0x1 -f elf_headers/elf64-PPC64LE.hex2 -f test/test13/hello.hex2 -o test/results/test13-binary + ./bin/get_machine + [ ppc64le = ppc64le ] + ./bin/get_machine --os + [ Linux = Linux ] + ./test/results/test13-binary Illegal instruction (core dumped) + [ 132 = 42 ] + exit 3 make[1]: *** [makefile:145: test13-binary] Error 3 The package builds fine in Debian on the same arch. ** Affects: mescc-tools (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072472 Title: mescc-tools FTBFS on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mescc-tools/+bug/2072472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072472] Re: mescc-tools FTBFS on ppc64el
** Description changed: mescc-tools fails to build on ppc64el with the following error: test/test13/hello.sh + ./bin/M1 --little-endian --architecture ppc64le -f test/test13/hello.M1 -o test/test13/hello.hex2 + ./bin/hex2 --little-endian --architecture ppc64le --base-address 0x1 -f elf_headers/elf64-PPC64LE.hex2 -f test/test13/hello.hex2 -o test/results/test13-binary + ./bin/get_machine + [ ppc64le = ppc64le ] + ./bin/get_machine --os + [ Linux = Linux ] + ./test/results/test13-binary Illegal instruction (core dumped) + [ 132 = 42 ] + exit 3 make[1]: *** [makefile:145: test13-binary] Error 3 + + The package builds fine in Debian on the same arch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072472 Title: mescc-tools FTBFS on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mescc-tools/+bug/2072472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072649] [NEW] glibc 2.39-3.1ubuntu2 breaks i386 feature detection (isa-support)
Public bug reported: This is showed by the isa-support autopkgtest regression. It is solved on the glibc maintenance branch. ** Affects: glibc (Ubuntu) Importance: Medium Status: In Progress ** Tags: update-excuse ** Tags added: update-excuse ** Changed in: glibc (Ubuntu) Status: New => Triaged ** Changed in: glibc (Ubuntu) Status: Triaged => In Progress ** Changed in: glibc (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072649 Title: glibc 2.39-3.1ubuntu2 breaks i386 feature detection (isa-support) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2072649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072657] [NEW] glibc Breaks: statement on libdkim needs to be adapted to Ubuntu
Public bug reported: In the last glibc merge, I dropped this piece of delta (pasting only the commit as the diff is a bit massive): commit 2c85e22ed40f15047fd290e8203fdc3ecbd2b6a4 Author: Simon Chopin Date: Fri Aug 11 14:40:30 2023 +0200 Adjust libc6-dev Breaks to account for binNMU vs no-change uploads This delta is Ubuntu-specific and can be dropped after 24.04 It turns out my analysis back then was completely wrong. This should be added back (but could be adjusted to remove the packages whose versions have since been superseded) ** Affects: glibc (Ubuntu) Importance: Medium Assignee: Simon Chopin (schopin) Status: Triaged ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072657 Title: glibc Breaks: statement on libdkim needs to be adapted to Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2072657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067482] Re: needrestart terminates itself on updates
Hi, verification done in a fresh Noble container: root@needrestart-self:~# dpkg -l needrestart | tail -n 1 ii needrestart3.6-7ubuntu4.1 all check which daemons need to be restarted after library upgrades root@needrestart-self:~# sudo systemd-run -u no-self-restart sh -c 'set -e; apt update; apt reinstall -y libc6; sleep 5; touch /tmp/did-not-self-restart' Running as unit: no-self-restart.service; invocation ID: d833631b9b1443f4b68fd3c7ab4877a1 root@needrestart-self:~# ls -lh /tmp/did-not-self-restart -rw-r--r-- 1 root root 0 Jul 11 09:24 /tmp/did-not-self-restart root@needrestart-self:~# date Thu Jul 11 09:24:20 UTC 2024 root@needrestart-self:~# systemctl status no-self-restart Unit no-self-restart.service could not be found. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067482 Title: needrestart terminates itself on updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2067482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065863] Re: needrestart causes kernel upgrade messages in motd
Verified in a fresh VM: root@needrestart-motd:~/needrestart-3.6# dpkg -l needrestart | tail -n 1 ii needrestart3.6-7ubuntu4.1 all check which daemons need to be restarted after library upgrades root@needrestart-motd:~/needrestart-3.6# systemd-detect-virt kvm root@needrestart-motd:~/needrestart-3.6# ls /run/reboot-required ls: cannot access '/run/reboot-required': No such file or directory root@needrestart-motd:~/needrestart-3.6# gcc -shared -fPIC -ldl debian/tests/mockuname.c -o mockuname.so root@needrestart-motd:~/needrestart-3.6# LD_PRELOAD=$PWD/mockuname.so apt install hello Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: hello 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 26.0 kB of archives. After this operation, 106 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu noble/main amd64 hello amd64 2.10-3build1 [26.0 kB] Fetched 26.0 kB in 0s (309 kB/s) Selecting previously unselected package hello. (Reading database ... 105648 files and directories currently installed.) Preparing to unpack .../hello_2.10-3build1_amd64.deb ... Unpacking hello (2.10-3build1) ... Setting up hello (2.10-3build1) ... Processing triggers for man-db (2.12.0-4build2) ... ERROR: ld.so: object '/root/needrestart-3.6/mockuname.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. Processing triggers for install-info (7.1-3build2) ... Scanning processes... Scanning linux images... Pending kernel upgrade! Running kernel version: 6.8.0-37-generic Diagnostics: The currently running kernel version is not the expected kernel version 6.8.0-38-generic. Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. root@needrestart-motd:~/needrestart-3.6# test ! -x /run/reboot-required || echo test failed root@needrestart-motd:~/needrestart-3.6# ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065863 Title: needrestart causes kernel upgrade messages in motd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2065863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068573] Re: needrestart: better document Ubuntu-specific behaviours
Verified in a fresh container: root@needrestart-nrconf:~# dpkg -l needrestart | tail -n 1 ii needrestart3.6-7ubuntu4.1 all check which daemons need to be restarted after library upgrades root@needrestart-nrconf:~# man needrestart root@needrestart-nrconf:~# man needrestart | grep -i ubuntu u (u)buntu mode, used to customized the behaviour in the APT hook. See /usr/share/doc/README.Ubuntu. root@needrestart-nrconf:~# needrestart --help | grep -i ubuntu u (u)buntu mode for the APT hook, see /usr/share/doc/needrestart/README.Ubuntu root@needrestart-nrconf:~# cat /usr/share/doc/needrestart/README.Ubuntu Starting from Ubuntu 24.04, needrestart in the default configuration will by default not show the Debconf prompt, and restart automatically the affected services. This includes when run as part of `unattended-upgrades` to ensure that the security updates it brings are actually applied to running services rather than leaving the system vulnerable. For more details, see the following Discourse post: https://discourse.ubuntu.com/t/needrestart-changes-in-ubuntu-24-04-service-restarts/44671 root@needrestart-nrconf:~# ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068573 Title: needrestart: better document Ubuntu-specific behaviours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2068573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068543] Re: Config variable $nrconf{restart} is no longer accurate: it always restarts
Verified on a fresh container (with the conf then removed to show the
difference):
root@needrestart-nrconf:~# dpkg -l needrestart | tail -n 1
ii needrestart3.6-7ubuntu4.1 all check which daemons need to be
restarted after library upgrades
root@needrestart-nrconf:~# e^C
root@needrestart-nrconf:~# echo '$nrconf{restart} = "l";' >
/etc/needrestart/conf.d/listmode.conf
root@needrestart-nrconf:~# apt reinstall libc6
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 3263 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 libc6 amd64
2.39-0ubuntu8.2 [3263 kB]
Fetched 3263 kB in 0s (20.3 MB/s)
Preconfiguring packages ...
(Reading database ... 34412 files and directories currently installed.)
Preparing to unpack .../libc6_2.39-0ubuntu8.2_amd64.deb ...
Unpacking libc6:amd64 (2.39-0ubuntu8.2) over (2.39-0ubuntu8.2) ...
Setting up libc6:amd64 (2.39-0ubuntu8.2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.2) ...
Disabling Ubuntu mode, explicit restart mode configuredScanning processes... [
Scanning processes...
Scanning candidates...
Services to be restarted:
systemctl restart console-getty.service
systemctl restart cron.service
systemctl restart packagekit.service
systemctl restart polkit.service
systemctl restart rsyslog.service
systemctl restart systemd-journald.service
systemctl restart systemd-networkd.service
systemctl restart systemd-resolved.service
systemctl restart systemd-udevd.service
systemctl restart udisks2.service
Service restarts being deferred:
/etc/needrestart/restart.d/dbus.service
systemctl restart systemd-logind.service
systemctl restart unattended-upgrades.service
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
root@needrestart-nrconf:~# rm /etc/needrestart/conf.d/listmode.conf
root@needrestart-nrconf:~# apt reinstall libc6
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 3263 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 libc6 amd64
2.39-0ubuntu8.2 [3263 kB]
Fetched 3263 kB in 0s (17.3 MB/s)
Preconfiguring packages ...
(Reading database ... 34412 files and directories currently installed.)
Preparing to unpack .../libc6_2.39-0ubuntu8.2_amd64.deb ...
Unpacking libc6:amd64 (2.39-0ubuntu8.2) over (2.39-0ubuntu8.2) ...
Setting up libc6:amd64 (2.39-0ubuntu8.2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.2) ...
Scanning processes...
Scanning candidates...
Restarting services...
systemctl restart console-getty.service cron.service packagekit.service
polkit.service rsyslog.service systemd-journald.service
systemd-networkd.service systemd-resolved.service systemd-udevd.service
udisks2.service
Service restarts being deferred:
/etc/needrestart/restart.d/dbus.service
systemctl restart systemd-logind.service
systemctl restart unattended-upgrades.service
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
root@needrestart-nrconf:~#
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068543
Title:
Config variable $nrconf{restart} is no longer accurate: it always
restarts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2068543/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072766] [NEW] glibc: drop the nanosleep fallback delta
Public bug reported: We have shipped a patch for glibc since groovy that adds a fallback path for clock_nanosleep_time64 to use CLOCK_MONOTONIC, to work around a bug in WSL1 (see bug 1871240). This has since been fixed in the WSL1 implementation (WSL2 is out of scope as they use a full-blown Linux kernel). A glibc version without that patch has been tested by @cnihelton on modern WSL1 without encountering the original issues, let's drop it moving forward. ** Affects: glibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072766 Title: glibc: drop the nanosleep fallback delta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2072766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set
** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044104 Title: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2044104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069875] Re: [needs-packaging] cmocka-mocks
Hi Alexandre! I did a first review of the package. My first question is a bit global: what's the use case for this? Is it supposed to be used at build time? I think for now it would be easier to have just a -dev package that provides the headers and static libraries, and not bother with shared libraries, as those tend to just make things harder. Notably, there's an expectation of ABI stability with a libfoo0 package, which I'm guessing isn't very high on upstream's list of priorities. After that, the rest of my remarks are pretty trivial in comparison ;) d/changelog: We usually don't mention all the steps in the initial package. Maybe use dh_installdocs for the docs? Bonus exercise: don't build the docs when using the nodocs profile (and don't pull in the dependencies for it) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069875 Title: [needs-packaging] cmocka-mocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063442] Re: needrestart on Ubuntu 24.04 is restarting google-guest-agent startup and shutdown scrips on reinstall but they should not be restarted
** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063442 Title: needrestart on Ubuntu 24.04 is restarting google-guest-agent startup and shutdown scrips on reinstall but they should not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2063442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071609] Re: [SRU exception] backport 5.37 to Jammy and Noble
** Description changed: Please be advised that some part of the changes only apply to the Jammy SRU. Current versions: Jammy: 5.32ubuntu3~22.04.1 Noble: 5.34ubuntu2 + + This SRU follows the exception process as outlined at + https://wiki.ubuntu.com/StableReleaseUpdates#autopkgtest rather than the + standard SRU rules. [Impact] This release contains both bug fixes and new features and we would like to make sure all of our developers have access to these improvements. Some notable ones are: 5.36: * Changes in source package selection: - Truly honor pinning when looking for the source package to download - find_source_version_to_download: always check the src package name (LP: #2066290) * setup-testbed: prevent /tmp from getting a tmpfs mount (LP: #2069834) * t/a-buildvm-ubuntu-cloud: use minimal image where possible * setup-testbed: Add support for netplan.io networking (Closes: #960729) (LP: #2060187) 5.35: * Resolve and install test dependencies using apt-get satisfy * autopkgtest-build-lxd: Extract lxc client version correctly. (LP: #2069274, LP: #2069283) The following only applies for the Jammy SRU: 5.34: * add support for deb822 sources (LP: #2052639) 5.33: * qemu: use device-tree for booting riscv64 (LP: #2056764) * qemu: boot riscv64 via EFI (LP: #2056764) See the changelog entry below for a full list of changes and bugs. [Test Plan] autopkgtest contains a test suite that is run using the SRU package for each release. This test suite's results are available here: Noble: * amd64: PASS https://autopkgtest.ubuntu.com/results/autopkgtest-noble-hyask-autopkgtest5.37-noble/noble/amd64/a/autopkgtest/20240701_200428_1869c@/log.gz * arm64: PASS https://autopkgtest.ubuntu.com/results/autopkgtest-noble-hyask-autopkgtest5.37-noble/noble/arm64/a/autopkgtest/20240702_124958_c97ec@/log.gz * armhf: SKIP https://autopkgtest.ubuntu.com/results/autopkgtest-noble-hyask-autopkgtest5.37-noble/noble/armhf/a/autopkgtest/20240702_094504_0e512@/log.gz * i386: FAIL (expected, main tests are green) https://autopkgtest.ubuntu.com/results/autopkgtest-noble-hyask-autopkgtest5.37-noble/noble/i386/a/autopkgtest/20240703_000615_861eb@/log.gz * ppc64el: FAIL (expected, main tests are green) https://autopkgtest.ubuntu.com/results/autopkgtest-noble-hyask-autopkgtest5.37-noble/noble/ppc64el/a/autopkgtest/20240702_130714_dc1b8@/log.gz * s390x: FAIL (expected, main tests are green) https://autopkgtest.ubuntu.com/results/autopkgtest-noble-hyask-autopkgtest5.37-noble/noble/s390x/a/autopkgtest/20240702_112706_c6126@/log.gz Jammy: * amd64: PASS https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest5.37-jammy/jammy/amd64/a/autopkgtest/20240702_094650_78193@/log.gz * arm64: PASS https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest5.37-jammy/jammy/arm64/a/autopkgtest/20240702_150636_4fc1c@/log.gz * armhf: SKIP https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest5.37-jammy/jammy/armhf/a/autopkgtest/20240702_094639_aefba@/log.gz * i386: FAIL (expected) https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest5.37-jammy/jammy/i386/a/autopkgtest/20240702_104537_6950b@/log.gz * ppc64el: FAIL (expected, main tests are green) https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest5.37-jammy/jammy/ppc64el/a/autopkgtest/20240702_112026_f1778@/log.gz * s390x: FAIL (expected, main tests are green) https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest5.37-jammy/jammy/s390x/a/autopkgtest/20240702_104356_32b4a@/log.gz We don't expect them to pass fully, but at least on amd64 and arm64 they are green. Additionally, the following PPAs should be tested manually at least under normal development conditions to ensure users will only be impacted by corner-case issues, should they arise: * https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest5.37-noble * https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest5.37-jammy Note that the `jammy` PPA is already under daily test by our auto- upgrade testing infrastructure. Please take a particular attention to test the cross-arch feature, as there is no automated tests for this. Here is the documentation on this feature: https://wiki.ubuntu.com/ProposedMigration#How_to_run_cross-architecture_autopkgtest_locally_using_QEMU Be knowledgeable that the `mawk` is particularly well suited for these kind of tests. [Where problems could occur] As always with those big updates, there might be corner-case issues not covered by the automated test suite. Also, with the differences in Python version, some library interfaces could have changed in untested code, leading to crashes. Given that this tool is mainly used by developers, users are likely to find workarounds or report bugs when t
[Bug 2068933] Re: all reports with LaunchpadPrivate in them are tagged need-$arch-retrace
It's on my board for this pulse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068933 Title: all reports with LaunchpadPrivate in them are tagged need-$arch- retrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2068933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068933] Re: all reports with LaunchpadPrivate in them are tagged need-$arch-retrace
I've looked a bit into it. It seems this has been going on for more than a decade, it might just be that so far most explicitly private reports we were getting were for crashes. Just so that I'm clear, adding `apport` as a subscriber is needed for the retrace/duplicate bit, but not for the generic private case, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068933 Title: all reports with LaunchpadPrivate in them are tagged need-$arch- retrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2068933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068933] Re: all reports with LaunchpadPrivate in them are tagged need-$arch-retrace
Ongoing work at https://github.com/canonical/apport/pull/367 ** Changed in: apport (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068933 Title: all reports with LaunchpadPrivate in them are tagged need-$arch- retrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2068933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004203] Re: With needrestart, apt-get does not respect non-interactive instruction when upgrading services
Can someone please modify the bug to adhere to the SRU template? https://canonical-sru-docs.readthedocs- hosted.com/en/latest/reference/bug-template/ It's a requisite condition for the fix to be uploaded and eventually released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004203 Title: With needrestart, apt-get does not respect non-interactive instruction when upgrading services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2004203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set
** Changed in: systemd (Ubuntu Oracular) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044104 Title: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2044104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080346] Re: autopkg test timeouts on arm64
Note that while it's a bit curious that the infra suddenly started routing those IPs, here I think rust-reqwest is wrong in the end. If you want an IP that's not routed, you should use one from an IP range from RFC 5735, as those should be treated by reasonable admins as follow: > Network operators SHOULD add these address blocks to the list of non- > routeable address spaces, and if packet filters are deployed, then > this address block SHOULD be added to packet filters. https://www.rfc-editor.org/rfc/rfc5737.html Duct-taping the infra to work around this is fine as a short-term solution but we really ought to work with upstream to fix this more durably. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080346 Title: autopkg test timeouts on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-reqwest/+bug/2080346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
** Description changed: [ Impact ] On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. [ Test Plan ] Part of the upload is adding an autopkgtest script testing useradd and usermod in the extrausers+readonly-etc case. In addition, the following commands should be run as root in a fresh container: ``` # Install prerequisites apt install libnss-extrausers sed -i -r -e'/^(passwd|group|shadow|gshadow)/ s/$/ extrausers/' /etc/nsswitch.conf # enable extrausers in group, passwd, shadow and gshadow # Sanity checks of "normal" path groupadd etcgroup useradd --groups etcgroup etcuser id etcuser | grep etcgroup groupadd etcgroup2 usermod --groups etcgroup2 etcuser id etcuser | grep etcgroup2 useradd --groups nullgroup etcuser || echo Successfully rejected invalid group ls /var/lib/extrausers/ # should be empty # Sanity checks of "extrausers" path in rw context groupadd --extrausers extragroup useradd --extrausers --groups extragroup extrauser # currently fails id extrauser | grep extragroup useradd --extrausers extrauser2 id extrauser2 - usermod --extrausers --groups extragroup extrauser2 + usermod --groups extragroup extrauser2 id extrauser2 | grep extragroup # Sanity checks of "extrausers" path in ro context mv /etc /etc-rw mkdir /etc mount -o bind,ro /etc-rw /etc groupadd --extrausers extragroup2 useradd --extrausers --groups etcgroup extrauser3 id extrauser4 | grep etcgroup - usermod --extrausers --groups extragroup2 extrauser3 + usermod --groups extragroup2 extrauser3 id extrauser4 | grep extragroup2 ``` Furthermore, validation from the Ubuntu Core team that this actually fixes their use case is required. [ Where problems could occur ] Regression potential is in the group validation stage of the `usermod` and `useradd` tools. Besides the usual risks related to C code, the various failure scenarios that come to mind are: * try to add the user to an non-existing local group, which would fail further down with a different error message * actually fail to identify a valid local group * Fail to either add the user to the system, or the user to the group * Update the wrong file (/var/lib/extrausers/* vs /etc/*) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
Thanks for testing and catching that regression! I've found and fixed the issue in an oracular upload. Once it clears -proposed I'll amend the noble-proposed version. ** Changed in: shadow (Ubuntu Noble) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063200 Title: useradd --extrausers --groups tries to lock /etc/group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065863] Re: needrestart causes kernel upgrade messages in motd
This is a new feature that I implemented based on what I had understood were your requirements: integrating needrestart with /run/reboot- required. Apparently, MOTD picks up whatever we write in that file. Shall I walk that part back and not write to that file in the case of kernel updates? I suppose needrestart could also go through update- notifier and mimick the kernel postinst code somehow? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065863 Title: needrestart causes kernel upgrade messages in motd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2065863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065863] Re: needrestart causes kernel upgrade messages in motd
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065863 Title: needrestart causes kernel upgrade messages in motd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2065863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061637] Re: [SRU] xx-svn-review crashed with ModuleNotFoundError
Hi Sudip, I've uploaded the Mantic and Jammy packages to the SRU queue. Thanks for your work :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061637 Title: [SRU] xx-svn-review crashed with ModuleNotFoundError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xxdiff/+bug/2061637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067482] [NEW] needrestart terminates itself on updates
Public bug reported: This is an expansion on bug 2059337. There's likely a fair number of custom services out there that are similar in nature to cloud-init, unattended-upgrade and the likes. Rather than forcing every user to track down and debug this issue, needrestart should instead have some sort of "self-preservation instinct" and exclude itself from the default restart list. While this issue isn't particularly new, it has become much more urgent in Noble onwards as we've modified it to default to silently restarting services. ** Affects: needrestart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067482 Title: needrestart terminates itself on updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2067482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 244250] Re: Spurious reboot notifications caused by libssl upgrades.
Well, we're not in the world of needrestart just yet, it's only seeded in Server. On Thu, 30 May 2024, 04:20 Seth Arnold, <244...@bugs.launchpad.net> wrote: > Adrien, thanks so much for digging into this again. > > This is so very complicated, why does openssl need special handling in > the world of needrestart? My inclination is to remove all this > complexity and address any shortcomings of needrestart in the > needrestart package. Am I off base? > > Thanks > > -- > You received this bug notification because you are subscribed to openssl > in Ubuntu. > https://bugs.launchpad.net/bugs/244250 > > Title: > Spurious reboot notifications caused by libssl upgrades. > > Status in openssl package in Ubuntu: > Fix Released > > Bug description: > The postinst script for libssl0.9.8 currently has a bug where it sends > a reboot notifcation whenever libssl is configured. So reconfiguring > libssl0.9.8 or even just installing libssl0.9.8 will result in a > reboot notification. Sending of the reboot notification should > definitely be moved inside the upgrading guard. The correct fix is > likely to move it inside a version comparison guard for particular > important updates like Colin suggests below -- this is what every > other standard package using notify-reboot-required does. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/244250/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=openssl; component=main; > status=Fix Released; importance=Undecided; assignee= > marc.deslauri...@canonical.com; > Launchpad-Bug-Tags: glucid lucid > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: adrien andersk cjwatson > iamnotwhatiam-deactivatedaccount janitor khaled-blah mdeslaur > nutznboltz-deactivatedaccount seth-arnold tabbott tbushnell tepples > Launchpad-Bug-Reporter: i am not what i am > (iamnotwhatiam-deactivatedaccount) > Launchpad-Bug-Modifier: Seth Arnold (seth-arnold) > Launchpad-Message-Rationale: Subscriber (openssl in Ubuntu) > Launchpad-Message-For: schopin > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/244250 Title: Spurious reboot notifications caused by libssl upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/244250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066995] Re: apport-gtk keeps prompting to report crashes in a loop
Steve, do you still have the crash file on your system? If so, could you give us its mod and owner? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066995] Re: apport-gtk keeps prompting to report crashes in a loop
Interestingly, I see the same "could not be opened" patter in my recent logs, all for crashes within Python executables. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
