** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968997
Title:
openssl has catastrophic issues when locale set to TR_UTF8
To manage notifications about this bug
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1010698:
Package: stunnel4
Version: 3:5.63-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
The debci testsuite failed for all architectures after the recent
openssl upload
moving forward.
Thanks for considering the patch.
Simon
** Affects: libnet-ssleay-perl (Ubuntu)
Importance: Undecided
Status: New
** Affects: libnet-ssleay-perl (Debian)
Importance: Undecided
Status: New
** Tags: update-excuse
** Bug watch added: Debian Bug tracker
> Separately i'm failing to get even as far as the bug description gets
> as i get failures on missing newuidmap binary and what not:
The log looks exactly like what you should see. The error about missing
newuidmap/newgidmap is expected as LXD writes the uidmap for the
container directly and
i still see this in jammy
Window manager warning: Log level 8: g_main_loop_is_running: assertion 'loop !=
NULL' failed
Window manager warning: Log level 128: unsetenv() is not thread-safe and should
not be used after threads are created
Window manager warning: Screen 0 on display ":0" already
I've been using 3.0.2-0ubuntu1.2 on jammy for a couple of days without
any noticeable regression, and have confirmed that the bug has been
fixed using the curl method outlined above.
Marking as verified on jammy.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
And the *release* version of Jammy has a 5.15 kernel that boots on the
machine in question, so I've managed a successful upgrade, and this
doesn't seem to be a problem for me any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The LXD snap itself isn't the problem. It only includes the nvidia-
container-cli utility (see https://github.com/NVIDIA/libnvidia-
container) which works as expected but fails to map to the driver
binaries from the host into the container environment due to the
incompatible symbols. This way you
Public bug reported:
On a fresh arm64 system I failed to start LXD containers with NVIDIA
GPUs attached. The error message LXD / nvidia-container-cli fails with
is:
lxc t0 20220506112123.475 DEBUGconf - conf.c:run_buffer:310 - Script exec
/snap/lxd/current/lxc/hooks/nvidia produced output:
Uploaded, thanks!
** Changed in: doodle (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: doodle (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: ftbfs
** Summary changed:
- doodle 0.7.2-3 does not build against Jammy
+ doodle 0.7.2-3 does not build against Kinetic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970410
Title:
Since the issue has been reported to Debian, let's wait a few days for
their feedback. Hopefully it'll be applied there and we'll simply sync
it back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/1971469
Title:
FTBFS against openssl 3
To manage notifications about this bug go to:
** Description changed:
- Upstream still does not support OpenSSL 3, and due to that a bunch of
- tests are failing. Fedora has been seeing the same problem and they
- filed a bug upstream:
+ [Impact]
+
+ The ruby-net-ssh package in jammy fails most operations due to its
+ incompatibility with
** Changed in: openssl (Ubuntu Jammy)
Importance: Undecided => Critical
** Changed in: openssl (Ubuntu Jammy)
Status: In Progress => Confirmed
** Changed in: openssl (Ubuntu Kinetic)
Status: In Progress => Confirmed
--
You received this bug notification because you are a
** Patch added: "openssl.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+attachment/5586942/+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/1968997
Here's the debdiff for kinetic, which is the whole 3.0.3 upstream
release.
You'll find a build for it in my PPA:
https://launchpad.net/~schopin/+archive/ubuntu/test-
ppa/+sourcepub/13495883/+listing-archive-extra
(just pop the extra changelog entry)
--
You received this bug notification
Attached is the patch for the Jammy SRU
** Patch added: "openssl_jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+attachment/5586889/+files/openssl_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: openssl (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: openssl (Ubuntu Jammy)
Status: Confirmed => In Progress
** Description changed:
- I noticed this when I checked "ua status". It alerted me that I should
- check my openssl configuration.
+ [Impact]
+
+
My bad, this should have been DEFAULT@SECLEVEL=0. I'll edit my comment.
Thank you all for your tests, it's 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/1958267
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1970744/+attachment/5584899/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Wallpapers unneccessarily scales along with the rest of the interface, which
causes the wallpaper to appear blurry. In other words, the wallpaper is
essentially being displayed at 1920x1080 instead of 3840x2160,
For those for whom the steps in #22 didn't work, does adding the
following line in /etc/wpa_supplicant/openssl.cnf right below the
"Options = UnsafeLegacyRenegotiation" line work?
CipherString = DEFAULT@SECLEVEL=1
(that's in addition of the other steps outlined in #22)
--
You received this bug
** Changed in: calamares (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: calamares (Ubuntu)
Importance: Undecided => Medium
** Changed in: calamares (Ubuntu)
Milestone: ubuntu-22.04 => jammy-updates
** Also affects: calamares (Ubuntu Jammy)
I
@Jan, indeed before replying to you I opened
https://bugs.launchpad.net/ubuntu/+source/wordpress/+bug/1970440 ;)
@Paul, I am assuming you are referring to the "not well maintained" part
of my comment so let me clarify. Ubuntu being a "frozen distro" (package
versions are normally set in stone at
Hello Holbok,
It looks like your system is booted with `ipv6.disable=1`:
Apr 26 08:28:53 kvmf kernel: [0.00] Command line:
BOOT_IMAGE=/vmlinuz-5.4.0-109-generic
root=UUID=a5928baa-1a87-4f79-88a2-eab3489fdea1 ro net.ifnames=0
biosdevname=0 ipv6.disable=1 maybe-ubiquity ipv6.disable=1
@Jan, while I understand the convenience of `apt install`, Wordpress is
unfortunately not well maintained in Ubuntu so I would recommend doing a
manual installation of an upstream supported version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@ubuntu-archive, would it be possible to add `wordpress` the sync
blocklist/blacklist, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970440
Title:
wordpress should be removed from the
Public bug reported:
The just released Ubuntu 22.04 ships with wordpress 5.8.3 which is
already outdated as 5.8.4 was released addressing 1 bug and 3 security
problems, see https://wordpress.org/support/wordpress-
version/version-5-8-4/#maintenance-updates
It seems that nobody from the community
Update: linux-image-5.14.0-1034-oem appeared in my normal apt upgrade
today and has booted successfully, so perhaps whatever the problem was
has been fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: doodle (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/1970410
Title:
doodle 0.7.2-3 does not build against Ja
, but
apparently *not* on the 3.0 branch)
I'll prepare an SRU for it ASAP.
** Changed in: openssl (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: openssl (Ubuntu)
Assignee: Steve Langasek (vorlon) => Simon Chopin (schopin)
--
You received this bug notification becau
All good points there, just one thing:
Quoting Batwam (2022-04-22 17:34:37)
> Alternatively, could it be as simple as copying
> /etc/grub.d/bin/grubcfg_proxy as part of the package install/update?
You still have a broken system on package removal.
--
You received this bug notification because
Actually, it *is* an issue with the VPN provider. The OpenSSL developers
have made a deliberate decision not to enable unsecure renegotiation
anymore, see this commit for more details:
https://github.com/openssl/openssl/commit/72d2670bd21becfa6a64bb03fa55ad82d6d0c0f3
Note that this change is
*** This bug is a duplicate of bug 1951399 ***
https://bugs.launchpad.net/bugs/1951399
Don't believe this to be a duplicate of the bug listed. This is after
successful installation.
I have same if not similar problem. Can install Ubuntu 22.04 OK but on
reboot "no operating system found" Dell
I just realized that my workaround only worked as long as the grub-
customizer was in the archive. Since we've removed it due to the above
issues, the workaround would probably be something like this (completely
untested):
orig_dir=/etc/grub.d/proxifiedScripts
main_dir=/etc/grub.d
I've spent more time than expected on cargo, with slow but steady
progress (merge done, with infra in place to easily enable/disable
bundling of libgit2 for future releases). I still have a few testsuite
regressions to figure out, but sadly part of my attention has been
diverted by release-related
*** This bug is a security vulnerability ***
Public security bug reported:
From https://github.com/python/cpython/issues/90471 :
PR bpo-25309 (#25309) changed OpenSSL behavior so that it ignores
unexpected EOFs by default. This was detected by the test suites of both
trio and AnyIO
** Description changed:
Hi,
Please remove the grub-customizer from Jammy. The package doesn't have
any reverse dependencies, and is basically broken regarding upgrades and
removals. It should also be added to the sync blacklist.
See
Public bug reported:
Hi,
Please remove the grub-customizer from Jammy. The package doesn't have
any reverse dependencies, and is basically broken regarding upgrades and
removals. It should also be added to the sync blacklist.
See https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
** Also affects: grub-customizer (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: grub-customizer (Ubuntu Focal)
Importance: Undecided
Status: New
** Also
** Tags added: fr-2262
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969353
Title:
Apt/Grub issue with 22.04 Upgrade (Missing libcrypto.so.1.1)
To manage notifications about this bug go to:
In the meantime, you can do this to fix your system:
sudo cp /usr/lib/grub-customizer/grubcfg-proxy
/etc/grub.d/bin/grubcfg_proxy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969353
Title:
I looked into the details, and my conclusions are that the grub-
customizer package has a completely broken removal/upgrade story.
The package only installs some binaries, without any custom maintainer
scripts or fancy things. Once you run the main program, it goes and
modifies the /etc/grub.d
@suoko please contact your VPN provider, as their client might not be
compatible with OpenSSL 3.0. There isn't much we can do on our end.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960268
Title:
@tallagrand, the certificate looks correct. I think your issue might be
with the smartcard support, so either in opensc or openvpn.
Either way, could you open a new issue? This is not the same problem as
OP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Looks like the missing bits were re-added in Bionic HWE kernel version
5.4.0-108.122~18.04.1. This allowed confirming with the recently
released -109 version:
root@bionic-vm:~# lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04
root@bionic-vm:~# uname -a
Linux bionic-vm
My first guess, just the askubuntu link, was that it was a leftover from
an old version of the grub-customizer package that hasn't been removed
as it is in /etc and subject to conffile handling, but I'm not so sure
that's entirely right, as I'd gathered that the old version was from
before Disco
I have a first rustc build up in a PPA, haven't merged cargo yet, nor
figured out the LLVM situation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968345
Title:
rustc 1.59 and cargo 0.60 required
** Changed in: rustc (Ubuntu Jammy)
Status: New => In Progress
** Changed in: rustc (Ubuntu Jammy)
Assignee: Canonical Foundations Team (canonical-foundations) => Simon
Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: fr-2255
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968997
Title:
openssl has catastrophic issues when locale set to TR_UTF8
To manage notifications about this bug go to:
Public bug reported:
# Steps to reproduce
1) Install Chromium's snap
snap install chromium
2) Monitor logs
journalctl -o cat -f --grep chromium
3) Start Chromium
journalctl will be filled with errors due to some syscalls not permitted
by the seccomp policy, like those:
Apr 14 11:18:14
Here is the syscall number => name mapping on amd64:
312: sys_kcmp
314: sys_sched_setattr (so also covered in LP: #1900679)
330: pkey_alloc
** Description changed:
# Steps to reproduce
1) Install Chromium's snap
snap install chromium
2) Monitor logs
journalctl -o cat -f --grep
Hi!
Could you run the follwoing command on your server certificate?
openssl x509 -in $SERVER_CRT -text | grep -i algorithm
With the new OpenSSL version, older certificates with SHA1 digests are
now invalid by default.
--
You received this bug notification because you are a member of Ubuntu
Thanks Athos, I can confirm the fix from you PPA deals with the problem!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968200
Title:
squid (GnuTLS flavour) links with OpenSSL libs
To manage
Looks like this was fixed as it now (rsync 3.2.3-8ubuntu3 from 22.04
dev) says:
man rsyncd.conf:
> A chroot-enabled module should not have this parameter set to false unless
> you're using a "name converter" program or you've taken steps to ensure that
> the module has the necessary resources
Identified this issue in Focal starting with the update to 105 kernel.
Constant soft lockups then freezing when kauditd/auditd exceeded backlog
limit. Due to DoD requirements, all systems set to audit=1 in kernel
boot options and have stringent list of syscalls/binaries/files that are
audited.
`yelp man:rsync` works fine on Ubuntu 20.04 with rsync version
3.1.3-8ubuntu0.3 so marking as fix released, thanks!
** Changed in: rsync (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello David, Ubuntu 14.10 was released a long time ago and is long end
of life. Are you still able to reproduce the issue on a supported
release? I'll mark the bug as Incomplete until you can report back.
Thank you!
** Changed in: rsync (Ubuntu)
Status: New => Incomplete
--
You received
*** This bug is a duplicate of bug 279557 ***
https://bugs.launchpad.net/bugs/279557
This bug was filled a long time ago so it is probably fixed. Also, as
Hans noted, this looks like a dup of LP: #279557 so I'll mark it as
such. Please re-open if that is still a problem, thanks!
** This bug
The error message is now clearer (IMHO of course):
$ rsync
rsync://cdimage.ubuntu.com/cdimage/releases/hardy/alpha-6/hardy-desktop-i386.iso
rsync: change_dir "/releases/hardy/alpha-6" (in cdimage) failed: No such file
or directory (2)
rsync error: some files/attrs were not transferred (see
Ubuntu Natty (11.04) was a long time ago and since it was reported as
fixed in that release, it means all still supported releases should be
good.
** Changed in: rsync (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Looks like rsync got that option in the end as this is what I get from
18.04's version:
# rsync --help | grep copy-devices
--copy-devices copy device contents as regular file
# dpkg -l| grep rsync
ii rsync3.1.2-2.1ubuntu1.4
amd64
The seed has been updated, we now need an AA to promote the following
binaries: libstd-rust-1.58 libstd-rust-dev rustc
** Changed in: rustc (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Our TLS libraries in Ubuntu default to disabling TLS < 1.2 since 20.04,
see https://discourse.ubuntu.com/t/default-to-tls-v1-2-in-all-tls-
libraries-in-20-04-lts/12464/4
You can enable TLS 1.0 by lowering the security level, see
** Tags added: fr-2238
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967084
Title:
netplan dbus returns "false" in io.netplan.Netplan.Config.Set with
networkd
To manage notifications about this
I am getting this problem with a commercial DVD that plays OK on a Linux Mint
PC. I have tried my PC's internal DVD drive and a USB DVD drive and multiple
DVDs and get:
Error
GStreamer backend error
Could not read DVD. This may be because the DBVD is encrypted and a DVD
decryption library is
In case the information is of any use: Fedora 35 installed without issue
with the same BIOS settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963769
Title:
Installer fails on Lenovo ThinkPad
I'd need to ask slyon as to why we're having an upper bound to the
timeout value, it's oddly specific, but in the mean time it's worth
trying out a version where we can get the full 30s as specified by the
snapd code.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: fr-2234
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968345
Title:
rustc 1.59 and cargo 0.60 required by firefox 101
To manage notifications about this bug go to:
Martin, let me do some more indepth testing next week and revert on this
question. Its a pitty my mainboard just blew. But I can confidently say
that the behaviour is predictable rather than random
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
Something in Ubuntu's squid build causes it to link with OpenSSL's
libssl.so.3:
root@jammy:~# apt-get install -y squid
root@jammy:~# dpkg -l| grep -w squid | grep GnuTLS
ii squid 5.2-1ubuntu3
amd64
Public bug reported:
Something in Ubuntu's squid build causes it to link with OpenSSL's
libssl.so.3:
root@jammy:~# apt-get install -y squid
root@jammy:~# dpkg -l| grep -w squid | grep GnuTLS
ii squid 5.2-1ubuntu3amd64
Full featured
Hi,
The issue is that OpenSSL 3.0 changed the API, which breaks older code.
However, we chose not to ship OpenSSL 1.1 in parallel to 3.0 as that
would carry the expectation of having security support for 1.1.1, which
is EOL upstream in 2023.
Marking as Won't Fix, however it should be relatively
Your comment #13 is what hinted me. I've been messing with openssl
lately and noticed an annoying message about .rnd but only on Bionic
machines ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@paelzer, upstream OpenSSL stopped using RANDFILE a while ago, I've
linked a MR to drop that directive from swtpm's patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968131
Title:
Starting VM
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/swtpm/+git/swtpm/+merge/418865
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968131
Title:
Starting VM with UEFI
** Description changed:
# Overview
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r-xp 00:51 14509
Changing back the status to New, as it is actually a display bug in
apport as found out in this Twitter thread:
https://twitter.com/NoraDotCodes/status/1511763913418891267
I couldn't reproduce on my system (Gnome-based)
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
**
Public bug reported:
After leaving the system for a while and it turning the screen off the
kernel crashes in the NVIDIA driver with the following:
Apr 06 17:24:56 kore kernel: BUG: kernel NULL pointer dereference, address:
0070
Apr 06 17:24:56 kore kernel: #PF: supervisor read
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968047
Title:
Ubuntu 22.04 Beta - Unable to compile ruby version 2.7.5, 3.0.3 and
3.3.3 problem with the openssl-dev
@paelzer, you made me revisit this and I can confirm that Focal+ is
fixed, only Bionic is still affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581864
Title:
nginx.service: Failed to read
** Description changed:
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r-xp 00:51 14509
Attached is the newest version of the patch, which solves all failures
mentioned above except for the EVP_PKEY_derive_set_peer diffie-hellman
group 14 one:
1504 runs, 5067 assertions, 4 failures, 3 errors, 0 skips
Next steps are
* split the patch into smaller patches to ease upstream inclusion
Hi Martin, I have an AMD RX6600 (which since 5.13 is quite well
supported). But as far as I remember I get the same issue with Intel
UHD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967507
Title:
Hi Rashid,
It seems to be a local config issue as hinted in the logs:
Elb 06 12:02:07 rashid-pc nginx[6538]: nginx: [emerg] could not build
server_names_hash, you should increase server_names_hash_bucket_size: 64
Elb 06 12:02:07 rashid-pc nginx[6538]: nginx: configuration file
Attaching logs fails when `apport-collect 1968027` wants to authorized
with my LP with an "Not allowed error".
** Description changed:
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000
Public bug reported:
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r-xp 00:51 14509
Here's my WIP patch, building upon Lucas' patch. If I run the tests with
OPENSSL_CONF pointing to the ssl.conf file in this patch (which has the
legacy provider enabled) I get
1504 runs, 4940 assertions, 4 failures, 23 errors, 0 skips
Deduplicating the errors, there are 4 types of failures that
Thanks Jeremy!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966127
Title:
ubuntu-desktop-minimal pulls gnome-session which is in universe
To manage notifications about this bug go to:
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/squid/+git/squid/+merge/418482
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967807
Title:
Apparmor doesn't let
Public bug reported:
After installing squid in a Jammy container:
audit: type=1400 audit(1649103012.819:218): apparmor="STATUS"
operation="profile_replace"
label="lxd-squid_//&:lxd-squid_:unconfined"
name="/usr/sbin/squid" pid=1003733 comm="apparmor_parser"
audit: type=1400
** Tags added: fr-2166
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964025
Title:
Do not support OpenSSL 3
To manage notifications about this bug go to:
I had a look at what's going on there. My understanding (with the caveat
that the code of s_server is quite hard to follow, even within GDB) is
that when the socket receives the packet, the server goes on and try to
establish a connection, only to find out that it cannot because it has
an
@alexmurray, totally random observation that is not related to this bug
but might save you/others some times. The following 4 steps:
# use a LXD VM for testing
lxc launch --vm images:ubuntu/jammy sec-jammy-amd64
# stop the VM and disable UEFI secure boot
lxc stop sec-jammy-amd64
# ensure
This also happens with the kernel in xubuntu-22.04-beta-desktop-
amd64.iso, so it will block me upgrading that machine to Jammy when it's
released.
Is there anything I can do to help? I'm not familiar with debugging
kernel drivers, but I'm a competent general developer, and I'm prepared
to put in
** Also affects: tomcat9 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: tomcat9 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Now that the new rustc has migrated from -proposed, I'd like to move
forward with the rustc MIR, as I believe all the issues raised during
its review (#3) have been addressed one way or the other, see #7 and
subsequent updates since.
We also have a provisional ACK from the security team (I'll
** Changed in: dh-cargo (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/1957932
Title:
[MIR] rustc, cargo, dh-cargo
To manage notifications about this bug
** Description changed:
[Availability]
The packages rustc and cargo are already in Ubuntu universe.
The packages build for the architectures they are designed to work on,
and are also built on platform with lesser upstream support, see
501 - 600 of 18197 matches
Mail list logo
