This issue arises because the container is running on top of a FIPS-
enabled kernel which provides the /proc/sys/crypto/fips_enabled = 1
flag.
On Noble, openssl sees this flag and expects therefore to be operating
in FIPS mode, but at this point the Noble container is not in FIPS mode
- we haven't
Thanks for pointing me in the right direction. It looks like this is not
a valid bug report after all then.
** Changed in: pinta (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Public bug reported:
Using a Daily build installation of Noble from 10/04/2024, updated on
11/04/2024, I can't install pinta using apt.
henry@pc2:~$ sudo apt update
[sudo] password for henry:
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run
Public bug reported:
Using Noble, installed from Daily build on 10/4/2024, I updated the
system on 11/4/2024 using `sudo apt update; sudo apt -y upgrade`
The following warning was printed in the `apt upgrade` output:
Processing triggers for initramfs-tools (0.142ubuntu24) ...
update-initramfs: G
I've observed the same behaviour with Noble installer, and it does
appear to be very counter-intuitive for a user to select "Don't send"
and then be told that their send request failed.
On a related point, the UI appears to block on this network request -
which is probably not necessary - and when
** Changed in: mysql-8.0 (Ubuntu)
Assignee: (unassigned) => Henry Coggill (henrycoggill)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971788
Title:
Failure to enable SSL out of the box w
