** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1973642
Title:
[REGRESSION] Unable to
** Changed in: openssl (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1971992
Title:
openssl rmd160 digest broken
Status
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1971992
Title:
openssl rmd160 digest broken
Status in
Hey Jan, thanks for the report. This has been discussed upstream at
https://github.com/openssl/openssl/issues/16994.
OpenSSL 3 has deprecated RIPEMD160 and thus moved them to the legacy provider
according to the official openssl migration guide at
I don't know much about dropbear but from your explanation it does
indeed sound like this is an upstream OpenSSH bug that should be
reported at https://bugzilla.mindrot.org/.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
[ Impact ]
- * On kernels with page size > 4K xorg (and presumably other applications
-relying on libunwind) crashes on startup. This affects anyone
-running the official arm64 generic-64k kernel or custom non 4k kernels
-(as used by e.g. apple silicon).
New diff as requested by @tsimonq2. I changed the version to
1.6.2-0ubuntu1.1 and added a DEP-3 header instead of taking the
unmodified patch from lunar as I did previously.
** Patch removed: "kinetic-fix"
** Also affects: libunwind (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: libunwind (Ubuntu Jammy)
** Also affects: libunwind (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Attached is a debdiff with the backported fix from lunar
** Patch added: "kinetic-fix"
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+attachment/5643674/+files/libunwind_1.6.2-0ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
The libunwind version we ship in kinetic crahes on arm64 platforms with page
sizes > 4k.
This was fixed in libunwind upstream. The fix made it into the debian version
synced to lunar.
Debian bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217
Upstream
** Description changed:
- The libunwind version we ship in kinetic crahes on arm64 platforms with page
sizes > 4k.
- This was fixed in libunwind upstream. The fix made it into the debian version
synced to lunar.
+ [ Impact ]
- Debian bug report at
The detected regression looks like a false-positive caused by another
dependency. The reported error is `/bin/sh: 1: python: not found` which
does not seem to be caused by the changes in libunwind.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I have installed libunwind=1.6.2-0ubuntu1.1 on my 16K page arm machine
and verified that the xorg crash is indeed fixed with this version. To
make sure it also does not negatively affect other hardware
configurations I also tested on my amd64 desktop and found that
everything still works without
I don't think that's enough since it also gets pulled in by ubuntu-
desktop and ubuntu-desktop-minimal as recommends. It would also be nice
if we found a solution that fixes the issue on existing installations
since upgrades from mantic to noble will trigger the bug.
--
You received this bug
> Was it it more than a red line in systemctl status output? Does it
have annoying logging behaviour or break some other service if it isn't
running?
Red lines and an avoidable boot delay while trying to restart and
failing a bunch of times.
--
You received this bug notification because you are
Public bug reported:
After upgrading to noble apparmor.service fails on my machine with the
following log message:
Apr 30 14:28:42 shodan apparmor.systemd[1739]: Restarting AppArmor
Apr 30 14:28:42 shodan apparmor.systemd[1739]: Reloading AppArmor profiles
Apr 30 14:28:42 shodan
Looking at the diff between mantic and noble I think the regression was
cause by a change to pd-mapper.service.in for
https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2054296
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Can confirm that this is was a major annoyance on my m2 air after
upgrading to noble. it seems like this worked better in previous
releases. Looking at my logs it seems like it was already installed on
mantic but didn't cause startup problems. I think it gets pulled in by
being in Recommends for
Public bug reported:
We have an open MR with a handful of FIPS compatibilty changes we wore hoping
to get into 24.04. The main purpose of the changes is to detect whether the
kernel is running in FIPS mode and adjust the behavior of the library
accordingly by loading the correct provider backend
** Attachment added: "apt install log from fresh noble lxd container"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2056593/+attachment/5754146/+files/openssl_3.0.13-1ubuntu2_install.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
As promised, here are some more details on how I tested:
- been running autopkgtest locally and made sure they pass (log attached)
- installed it on my local development machine to see if anything breaks
- tested the upgrade in a lxd container, made sure openssl speed works and does
the right
Public bug reported:
Since I upgraded to Noble the lxd vga console doesn't work anymore. I am
using the lxd latest/stable snap (5.20-f3dd836). When trying to attach a
vga console to an lxd vm I get:
unshare: write failed /proc/self/uid_map: Operation not permitted
It seems to be related to
The reason for the crash is that ntp uses an outdated OpenSSL API to use MD5
despite it normally being blocked in FIPS mode. This particular API has been
deprecated with OpenSSL 3 which we ship in Jammy.
This could be mitigated by switching to a newer OpenSSL API, but ntp also seems
to be on
Adding a few more details as requested by Adrien.
I used lxd to run the autopkgtest, in particular:
# Build lxd image
/usr/bin/autopkgtest-build-lxd ubuntu-daily:noble
# Run
autopkgtest -s --apt-pocket=proposed ./openssl_3.0.13-1ubuntu2.dsc -- lxd
autopkgtest/ubuntu/noble/amd64
It is
24 matches
Mail list logo
