AfAIK this isn't an issue anymore.
** Changed in: strace (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484083
Title:
strace doesn't decode stat() arguments on
I don't similar issues nowadays. Considering the issue is very old and
involves openoffice (my fingers even typed "libr" by habit now), I'm
going to close this as Incomplete.
** Changed in: strace (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a m
*** This bug is a duplicate of bug 1062412 ***
https://bugs.launchpad.net/bugs/1062412
** This bug is no longer a duplicate of private bug 755619
** This bug has been marked a duplicate of bug 1062412
strace crashed with SIGSEGV in __GI_raise()
--
You received this bug notification becaus
I think this doesn't apply anymore: the code in the patch isn't there
anymore and printing is done through dedicated functions.
** Changed in: strace (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think that if this has not been fixed, this is not relevant anymore as
people would instead strace from the 64-bit side. Moreover, these cross-
world operations can be very difficult and are unlikely to change
further in the future even if this still happens.
** Changed in: strace (Ubuntu)
Hi, can you give more details about what happened to termius-beta and
why you were stracing it? In particular, was termius-beta itself
crashing?
** Changed in: strace (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I cannot reproduce the issue so I assume the fix has been merged and
released.
** Changed in: strace (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766060
I think this would be very difficult to try to reproduce 16 years later
and probably not worth it considering that we were seeing this issue
from several people but we don't anymore. As such, I assume that the
issue existed but has been fixed.
** Changed in: strace (Ubuntu)
Status: Triaged
*** This bug is a duplicate of bug 1062412 ***
https://bugs.launchpad.net/bugs/1062412
Marking as duplicate of #1062412 ; it appears that strace mimics the
exit of the straced program.
** This bug has been marked a duplicate of bug 1062412
strace crashed with SIGSEGV in __GI_raise()
--
Y
I think that if this has not been fixed, this is not relevant anymore as
people would instead strace from the 64-bit side. Moreover, these cross-
world operations can be very difficult and are unlikely to change
further in the future even if this still happens.
** Changed in: strace (Ubuntu)
AFAIU this has been fixed and is now in the released versions of Ubuntu
so closing as fix released.
** Changed in: strace (Ubuntu)
Status: New => Triaged
** Changed in: strace (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member o
There has indeed been a behaviour change a while ago. AFAIK this has
been relaxed to allow ptracing processes of the same user so this
shouldn't be an issue anymore.
** Changed in: strace (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubu
Made a mistake: it's not actually a duplicate of that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/324553
Title:
strace crashed with SIGSEGV in free()
To manage notifications about this bug go to
Marking as Invalid as that seems expected: strace uses ptrace which does
not work across setuid/setgid binaries which crontab is.
-rwxr-sr-x 1 root crontab 43K Jun 6 2024 /usr/bin/crontab
This is intended for security (otherwise it would be trivial to hijack
`su`).
** Changed in: strace (Ubunt
** Changed in: strace (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426635
Title:
strace stack buffer overflow
To manage notifications about this
*** This bug is a duplicate of bug 1062412 ***
https://bugs.launchpad.net/bugs/1062412
** This bug is no longer a duplicate of private bug 755619
** This bug has been marked a duplicate of bug 1062412
strace crashed with SIGSEGV in __GI_raise()
--
You received this bug notification becaus
Couldn't find the traces (anymore?). The bug doesn't happen anymore
according to the tracker. Closing as Incomplete.
** Changed in: strace (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
*** This bug is a duplicate of bug 1062412 ***
https://bugs.launchpad.net/bugs/1062412
** This bug has been marked a duplicate of bug 1062412
strace crashed with SIGSEGV in __GI_raise()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to t
** Changed in: strace (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062412
Title:
strace crashed with SIGSEGV in __GI_raise()
To manage notifications a
*** This bug is a duplicate of bug 1062412 ***
https://bugs.launchpad.net/bugs/1062412
Thanks a lot yzp15, this is very helpful. I'm going to mark these bugs
as duplicate and close them as Invalid since it's made on purpose.
** This bug has been marked a duplicate of bug 1062412
strace cra
I'm going to close this bug. I agree there is an expected limitation
there as Ortwin pointed out. Strace is powerful but also very invasive
(well, the first thing that is invasive is ptrace).
** Changed in: strace (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification
*** This bug is a duplicate of bug 1062412 ***
https://bugs.launchpad.net/bugs/1062412
** This bug is no longer a duplicate of bug 324553
strace crashed with SIGSEGV in free()
** This bug has been marked a duplicate of bug 1062412
strace crashed with SIGSEGV in __GI_raise()
--
You rece
Marking as duplicate of #1062412 ; it appears that strace mimics the
exit of the straced program.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/324553
Title:
strace crashed with SIGSEGV in free()
T
AFAIU, this has been fixed, but maybe not backported to released
versions. Since this was 15 years ago and all these versions are now out
of support anyway, I'm closing this as Fix Released.
** Changed in: strace (Ubuntu)
Status: New => Fix Released
--
You received this bug notification b
I'm closing this as the issue is not present anymore and this was for an
ancient version.
** Changed in: strace (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I've been following that topic from a distance since it's linked to
openssl.
I've just seen https://github.com/curl/curl/wiki/curl-distro-
discussion-2025 which mentions "HTTP/3 - updates on status and
discussions on how to (possibly) enable this in curl for distros going
forward". The curl Debian
I remembered seeing aircrack-ng in merges.ubuntu.com and it looks like
the latest upload in Debian is actually related to that issue so a merge
should help: https://tracker.debian.org/news/1561207/accepted-aircrack-
ng-117git202308074bf83f1a-2-source-into-unstable/
Changes:
aircrack-ng (1:1.7+git
Hi Gauthier, I'm pasting below relevant entries in the changelog. As
you'll see, using pkg-config has been suggested after Jammy and the
script has been removed after Noble. What is requiring libgcrypt-config
and can we work on updating that instead maybe?
libgcrypt20 (1.11.0~beta450-1) experiment
Thanks for the kind words and thanks a lot for your great review.
All your comments look appropriate. I've mentioned a few things on
mattermost but for completeness:
* d/changelog, thanks for doing that
* d/crypto-config-docs.*, I probably inherited that from dh-make and I don't
remember really
** Description changed:
This is a new package for which Canonical is the upstream. The purpose
is to create profiles of cryptography configuration that will be used
across software in the distribution.
I'd like to have it uploaded to universe.
There is a pretty complete specificati
** Description changed:
This is a new package for which Canonical is the upstream. The purpose
is to create profiles of cryptography configuration that will be used
across software in the distribution.
I'd like to have it uploaded to universe.
URL: https://github.com/canonical/cryp
** Changed in: ubuntu
Importance: High => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098879
Title:
[needs-packaging] crypto-config in universe
To manage notifications about this bug
** Description changed:
This is a new package for which Canonical is the upstream. The purpose
is to create profiles of cryptography configuration that will be used
across software in the distribution.
I'd like to have it uploaded to universe.
There is a pretty complete specificati
I've seen the following in the linked discussions:
> Hey Everyone 👋 Thanks for your patience with the checkout errors and
random failures. We discovered it was an issue with the underlying
hardware and have migrated all the runners to a different arm sku
(dpdsv5) and this should solve the errors y
** Also affects: p11-kit (Ubuntu)
Importance: Undecided
Status: New
** Changed in: p11-kit (Ubuntu)
Status: New => Fix Released
** Changed in: p11-kit (Ubuntu)
Importance: Undecided => High
** Changed in: p11-kit (Ubuntu)
Assignee: (unassigned) => Adrien Nade
on in main.
I think the packaging looks good overall but forgive me if I've missed
something as there are so many different things to pay attention to with
new packages.
** Affects: ubuntu
Importance: High
Assignee: Adrien Nader (adrien)
Status: In Progress
--
You received
** Changed in: gnutls28 (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/2098424
Title:
gnutls28 fails to build from source in plucky
To manage notificat
** Changed in: gnutls28 (Ubuntu)
Importance: Undecided => High
** Changed in: gnutls28 (Ubuntu)
Status: New => Triaged
** Changed in: gnutls28 (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien)
--
You received this bug notification because you are a member of Ub
** 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/2098424
Title:
gnutls28 fails to build from source in plucky
To manage notifications about this bug go to:
https://bugs
Thanks for the update. I've looked more at the logs and I'm very
surprised to see the following:
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w 11 Sep 2023
I guess that's from some binary install of rust
My point is that you linked to six different bug reports on github
which, when taken together, point to an issue being elsewhere. If there
are unrelated reports in that list, can you remove them? It's difficult
for me to read through so much stuff if it's only loosely correlated.
Also, if the issu
Hi and thanks for your report.
I can't find a direct link between all these reports, or at least not
one that points towards openssl. In particular, GCC does not use openssl
which means that crashes in GCC cannot be explained by problems in
openssl.
Since it looks like there may be a single issue
** Changed in: openssl (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/2096810
Title:
[25.04 FEAT] openSSL MSA 10 XTS support
To manage notifications ab
Public bug reported:
Please sync m2crypto 0.42.0-2.1 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
  * d/p/openssl-3.4-ftbfs.patch:
Remove as this was leading to a whack-a-mole game trying to have
SWIG parse properly all system headers
I
Public bug reported:
There is a new version in Debian (1.8.11-2) and merging it fixes tests
failures for the new libnftnl.
** Affects: iptables (Ubuntu)
Importance: High
Assignee: Adrien Nader (adrien)
Status: In Progress
** Tags: update-excuse
--
You received this bug
Public bug reported:
libunwind 1.7.2 fails to build from source on arm64 and i386 and
introduces bugs in some programs. Version 1.8.1 fixes these issues but
hasn't been uploaded in Debian yet.
I don't think we need the update so I would simply wait for a change in
Debian rather than introduce a d
** Changed in: openssl (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059101
Title:
Automatic EST certificate retrieval does not work on Ubuntu 22.04
To ma
I'm going to switch this to Won't fix since only on person seems to be
affected and they had a solution for them. I never found out who is the
other user affected on 2024-05-17. We can re-consider if I get
information from that user (it's really unfortunate that LP didn't
provide more insights)
**
Glad that you found a solution for your issue and thanks for the update.
** Summary changed:
- Openssl can't find libs and finally crashes on "missing shared library
libssl.so.1.0.0"
+ With splunk, openssl can't find libs and finally crashes on "missing shared
library libssl.so.1.0.0"
--
You
Hmm, I was perplexed with breezy and took another look at the report
above. I may have to re-open it but I'll see later on (maybe a few
days).
The issue in the logs is still maybe present but there are also fixes
for two FTBFS on python 3.13 waiting I think the effect of the new
openssl version sh
Breezy is not compatible with python 3.13; this is not related to
openssl 3.4. I'm preparing a PR for breezy on github right now.
** Changed in: breezy (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
* Changed in: python3.12 (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092298
Title:
python3.12/3.13: incompatibility with openssl
I believe it has been fixed for python3.13 by 3.13.1-3 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092298
Title:
python3.12/3.13: incompatibility with openssl 3.4
To manage notifications about
I've added specific affects entries for noble and oracular so that I
could mark
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2092609 as
duplicate.
Fixing this for Noble would require an SRU obviously, which would have
to be staged to be picked up with some security update when that
happe
lar)
Assignee: (unassigned) => Adrien Nader (adrien)
** Changed in: openssl (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: openssl (Ubuntu Noble)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
*** This bug is a duplicate of bug 1297025 ***
https://bugs.launchpad.net/bugs/1297025
** This bug has been marked a duplicate of bug 1297025
Either the changelog.gz is missing or there is an erroneous link in the
libssl1.0.0 package
--
You received this bug notification because you are
** 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/2092298
Title:
python3.12/3.13: incompatibility with openssl 3.4
To manage notifications about this bug go to:
https://
** Also affects: python3.13 (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/2092298
Title:
python3.12/3.13: incompatibility with openssl 3.4
To ma
Public bug reported:
Python3.12 (and 3.13?) probably need to include the patches given through
https://github.com/python/cpython/pull/127361:
- python3.12: https://github.com/python/cpython/pull/127905
- python3.13: https://github.com/python/cpython/pull/127812
The upstream changes address repor
freedombox 24.25 has been uploaded with the fix that Julian linked to
but it currently FTBFS probably due to python-django.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074186
Title:
pyopenssl: re
Public bug reported:
Changed exception.
** Affects: m2crypto (Ubuntu)
Importance: High
Assignee: Adrien Nader (adrien)
Status: In Progress
** Changed in: m2crypto (Ubuntu)
Status: New => Incomplete
** Changed in: m2crypto (Ubuntu)
Status: Incomplete =&
** Summary changed:
- m2crypto: FTBFS with openssl 3.4
+ m2crypto: FTBFS with openssl 3.4 as swig and gcc use different feature flags
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091883
Title:
m2
** Description changed:
- Testsuite fails with openssl 3.4.
+ Openssl 3.4 has started returning an error for when calling
+ X509_REQ_set_version() with "1" which is not specified. However,
+ m2crypto was using that in its testsuite which now fails due to that.
** Summary changed:
- Testsuite fai
High
Assignee: Adrien Nader (adrien)
Status: In Progress
** 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/2091883
Title:
m2crypto: FTBFS with openssl 3.4
To m
Public bug reported:
Testsuite fails with openssl 3.4.
** Affects: m2crypto (Ubuntu)
Importance: High
Assignee: Adrien Nader (adrien)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
AFAIU the API issues for freedombox and python-oauth2client were not the
same. I can imagine having a single bug for these API removals in
pyopenssl since it looks like they're going to be pretty common but we
should have a separate diary entry in the bug description for each
removal that's problem
** 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/2089065
Title:
rust-cargo-c: FTBFS on Plucky
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
I've prepared an MR+debdiff for rust-libgit2-sys :
https://code.launchpad.net/~adrien/ubuntu/+source/rust-
libgit2-sys/+git/rust-libgit2-sys/+merge/477805
Note that I've tested the build in a PPA to ensure there isn't an FTBFS.
--
You received this bug notification because you are a member of Ub
*** This bug is a duplicate of bug 2091023 ***
https://bugs.launchpad.net/bugs/2091023
** This bug has been marked a duplicate of bug 2091023
Please remove ruby3.1 and add to blocklist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: plr (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087739
Title:
plr: Please RM armhf binaries
To manage notifications about this bug go t
** Changed in: openssl (Ubuntu)
Status: Confirmed => In Progress
** Changed in: openssl (Ubuntu)
Milestone: None => ubuntu-25.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066990
Title
** Changed in: openssl (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087955
Title:
openssl: merge 3.4.0-1 from Debian unstable
To manage notifi
** Changed in: pgauditlogtofile (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088006
Title:
Remove NBS 32-bit postgresql extension packages, part 4
To man
I guess that splunk is shipping its own libraries somewhere in
/opt/splunk but somehow they're not being used. I'm not familiar with
splunk at all and I don't know how they integrate with the system:
LD_LIBRARY_PATH, some other ld.so config, or maybe there's a special
environment to run? I can only
Hi,
libssl.so.1.0.0 points towards openssl 1 while Ubuntu has been shipping
openssl 3 and libssl.so.3 for several years now.
It seems you're using splunk as can be seen in the output of strace:
/opt/splunk/bin/openssl . I think the issue is that your splunk
installation is either out-of-date, or
I had a look at the packages.
I addressed pgl-ddl-deploy and pglogical-ticker in
https://bugs.launchpad.net/ubuntu/+source/pgrouting/+bug/2089236/comments/8
.
I checked the reverse runtime and build dependencies of all other
packages.
- pgsphere has a reverse depend from gavodachs2-server which
Note that pglogical-ticker and pgl-ddl-deploy are listed in
https://bugs.launchpad.net/ubuntu/+source/pgrouting/+bug/2088006 so I'm
not touching the bug here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Hmm, duh, thanks for pointing out the bad -a and -b combination. I need
to get the habit of avoiding -b completely.
I checked the packages which depend upon pglogical:
- pglogical-ticker: source, restricted to 64-bit arches
- postgresql-17-pglogical-ticker: binary missing in proposed, sole pack
For reference, during a build, the testsuite now says the following:
# Subtest: ../../test/fips_auto_enable_test
1..1
While loading "fips" provider: error:07880025:common libcrypto
routines::reason(37)
While loading "fips" provider: error:07880025:common libcrypto
routines::reaso
My plan is to make the library write the following error message when
failing to load a provider (it will apply to any provider):
While loading "fips" provider: error:07880025:common libcrypto
routines::reason(37)
There was already an error but it was silent until it reached the
application w
I and others have re-triggered the tests on focal but there are
infrastructure issues. Considering the number of retries so far, it
seems unlikely that further attempt will help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Tags added: ftbfs plucky 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/2089286
Title:
mayavi2: remove from armhf due to Build-Depends: architecture-
is-64-bit
To manage notificat
** Tags added: ftbfs plucky 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/2089285
Title:
Remove from armhf due to Build-Depends: architecture-is-64-bit
To manage notifications about t
** Tags added: ftbfs plucky 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/2089236
Title:
Remove NBS 32-bit postgresql extension packages, part 5
To manage notifications about this bu
Public bug reported:
mayavi2 now Build-Depends on architecture-is-64-bit
The following returned only python3-surfer which is an "all" package.
reverse-depends -a armhf -r plucky -R -l src:mayavi2
reverse-depends -a armhf -r plucky -R -l -b src:mayavi2
** Affects: ubuntu
Importance: Und
Public bug reported:
Adios2 does not support 32-bit builds and Build-Depends on architecture-
is-64-bit.
The package currently FTBFS but that doesn't change the need to remove
it.
I recursively ran the following, stopping at branches with no "armhf"
binary package (I did not do the same check fo
Public bug reported:
This is a follow-up to #208800{3,4,5,6} as I've identified a few more
affected packages.
I'm copying Jeremy's original description at the end of this
description.
The affected packages are:
- pgpointcloud
- pgnodemx
- pgmemcache
- pglogical
- pgfincore
- pgextwlist
- mobili
I had actually re-tried them but they failed the same way (which I don't
believe was related to the upload). I've triggered them again, and
hopefully the runners will behave better this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I've found more packages which are affected:
pgpointcloud
pgnodemx
pgmemcache
pglogical
pgfincore
pgextwlist
mobilitydb
I've also noticed the following non-postgres packages which B-D on
architecture-is-64-bit
r-bioc-alabaster.base
adios2
mayavi2
pmix
purify
icu-ext
rocr-runtime (but there are o
I've retriggered the tests on oracular and they all passed. Britney has
also updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083490
Title:
[SRU] 2.66.1
To manage notifications about this bu
I hadn't re-triggered the tests on jammy and focal though (they had
already passed on noble) and I've done so now. The infra issues are
still present however so the tests may need an unknown number of
retriggers to pass.
--
You received this bug notification because you are a member of Ubuntu
Bug
estone: None => ubuntu-25.04
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087955
Title:
openssl: merge
Public bug reported:
Openssl 3.4.0-1 has been uploaded to unstable and it's now possible to
merge it.
I'm creating a bug report too because I encountered an issue while
preparing the merge and it actually landed with 3.3 but somehow wasn't
triggered which is odd.
This was caused by the addition
I've marked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084802
as duplicate of this issue because it is solved the same way and I also
edited the title here to make it more generic (don't hesitate to change
it further).
The issue in that other bug report has a different setup however.
Qu
*** This bug is a duplicate of bug 2084251 ***
https://bugs.launchpad.net/bugs/2084251
** This bug has been marked a duplicate of bug 2084251
LUKS not detected or prompted for on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I ended up installing the package because systemctl status indicated my
system was in "maintenance" and that was probably the start of a chain
of issues (e.g. no audio). It fixed the issue for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
It looks like I'm facing the issue too on an upgrade from Noble to
Oracular. I haven't changed anything yet on purpose. Let me know if you
want me to try something. (meanwhile I'm going to debug pcscd's new use
of polkit to get my yubikey working again...)
--
You received this bug notification be
The SRU process is dedicated work that is specific to non-security
updates to a package in a released Ubuntu version: no such thing has
been done for libssh2 in 22.04. It has to be done for every change
anyway as the goal is to avoid behavior differences from the
corresponding changes.
But I was w
** Changed in: openssl (Ubuntu)
Importance: Undecided => High
** Changed in: ca-certificates (Ubuntu)
Status: Confirmed => Invalid
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien)
--
You received this bug notification because you are a
NB: we can only SRU that to Noble if it first goes in a development
version of Ubuntu which will only be possible when development for 25.04
begins.
** Summary changed:
- high memory consumption in Ubuntu Noble
+ openssl fails with out of memory messages while trying to load the FIPS
provider in
1 - 100 of 236 matches
Mail list logo
