To be more precise: I can't reproduce it using gcc or clang, no matter
the fortify level, and the upstream fix
https://sourceware.org/git/?p=glibc.git;a=commit;h=5a5f94af0542f9a35aaa7992c18eb4e2403a29b9
mentions that you can only trigger it on older releases that aren't
available in Jammy.
As a
Hi, thanks for reporting the issue.
could you provide us with a reproducer for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056751
Title:
Error compiling with glibc2.35 in Ubuntu22.04.3
This bug is actually in gcc-14, more specifically libquadmath, as they
do a misaligned read from args to a float128, which produces the
segfault.
It was hidden so far because args was allocated using alloca() which I
guess must be naturally aligned, but in 2.39 they removed that in favor
of
** Tags added: foundations-todo
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: glibc (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It turns out the fix was already in the upstream repo as a PR for a
while (couple of years?). I've submitted a Salsa MR to proactively
address the issue before it shows up there:
https://salsa.debian.org/perl-team/modules/packages/liblocale-gettext-
perl/-/merge_requests/1
and I've uploaded the
Unless I'm missing something, the issue you're linking is about glib,
not glibc. Reassigning the bug accordingly.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification
After a bit more reflexion, I'd even argue that this 'built tree'
exception shouldn't exist in the first place as it seems like a nice
footgun, but I'm guessing it's not that simple, so in the mean time I'll
just go and amend my wrapper script to not use `autopkgtest .` but
rather
I'll be damned. That's the issue, indeed. I tried to reproduce with a
fresh `hello` but couldn't so I wrongly concluded that it was because it
wasn't on the image.
I'd argue it's still a bug, as in *this should be documented*! I'd never
consider that an unpackage source package would be in a
Confirmed on salsa, and yes I'm using noble, 5.32ubuntu3, sorry about
that.
One solution I could think of is to go through the list of dependencies
and add a strict version if it's a binary generated by the tested source
package (lib/adt_testbed.py, install_apt)
--
You received this bug
Public bug reported:
While working on needrestart autopkgtests, I've run into issues testing
it using my standard invocation:
autopkgtest . -U -- lxd autopkgtest/ubuntu/noble/amd64
The runner wouldn't install the built package but would just keep
whichever version is in the archive, while still
Public bug reported:
Release of Ubuntu: Noble
Package Version: 5.72-0ubuntu1
My headset changed profile from A2DP to HSP as I received a phone call on my
phone (the headset can connect to multiple BT devices).
I'd expect the system to adapt to the new profile (add a new source, change the
To be clear, this appeared right after you selected the english
keyboard?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054193
Title:
locale-gen crashed with SIGABRT in __GI___wait4()
To manage
Public bug reported:
As a header to all .conf files in systemd there's a comment saying
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by
** Summary changed:
- needrestart should integrate with /run/reboot-required
+ needrestart should integrate with /run/reboot-needed
** Description changed:
We have a standard mechanism to notify users that their machine should
- be rebooted through /run/reboot-required, needrestart should use
Public bug reported:
To quote vorlon in bug 2049208
> The debconf frontend is always non interactive when running under
unattended-upgrades; failing to restart affected services when auto
applying security updates is critically BROKEN BY DESIGN
While a bit hyperbolic, the point still stands.
Public bug reported:
We have a standard mechanism to notify users that their machine should
be rebooted through /run/reboot-required, needrestart should use that
instead of debconf prompts.
** Affects: needrestart (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Hi, thanks for reporting this issue.
Could you please specify which version of Ubuntu you're using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051766
Title:
needrestart should priorize and
We had a mitigation for this in glibc but the latest change from simply
denying the unshare() call to allowing it but then denying anything
requiring capabilities *presumably* broke the glibc test suite again.
I'm only basing this from looking at the test logs, as I'm temporarily
unable to run
Uploaded, thanks for the debdiff, and thanks Frank for the review.
For the record, `update-maintainer` is usually not mentioned in the
changelog, we sort of consider it par for the course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1968334
Title:
Fix CVE-2019-13115
To manage notifications about this bug go to:
** Also affects: libssh2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: libssh2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: libssh2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you
** Summary changed:
- libssh2 upgrade
+ Fix CVE-2019-13115 in Focal
** Changed in: libssh2 (Ubuntu)
Status: New => Triaged
** Changed in: libssh2 (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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.
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:
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
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
*** 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
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
** 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
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,
** 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
** 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:
** 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
(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 rec
** 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:
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
** 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.
+
+
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
** 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
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
**
** 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:
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
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
*** 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
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.
** 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
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
) 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
Uploaded to Kinetic, I'll review and upload the others tomorrow.
** Changed in: opencryptoki (Ubuntu Focal)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: opencryptoki (Ubuntu Impish)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: opencryptoki (
This issue has been introduced in 3.0.3 upstream but we've backported
the patch set to Jammy as well. The cherry-picked fix is in Debian in
3.0.3-4.
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
** Also affects: openssl (Ubuntu Kinetic)
Importance: Undecided
Status:
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1010958:
Source: sscg
Version: 3.0.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1
...
1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11
SIGSEGV
Also, does tinc work in a purely Jammy context? :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972939
Title:
Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes
To manage
Could you give more details about what happens when using the legacy
providers?
** Changed in: tinc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972939
Public bug reported:
The version 3.0.3-4 from Debian unstable should be merged in Kinetic.
** Affects: openssl (Ubuntu)
Importance: High
Assignee: Simon Chopin (schopin)
Status: Confirmed
** Tags: fr-2393
** Tags added: fr-2393
--
You received this bug notification
Hi!
You want to add -traditional to your openssl rsa command to get the
previous behaviour:
❯ openssl rsa -in key.pem | grep BEGIN
writing RSA key
-BEGIN PRIVATE KEY-
❯ openssl rsa -in key.pem -traditional | grep BEGIN
writing RSA key
-BEGIN RSA PRIVATE KEY-
** Changed in:
I'm guessing there are some SSL certificates involved? If so, this issue
is mentioned in the release notes: certificates that use e.g. SHA1 as
the digest algorithm should be re-issued by your provider with a
stronger hash algorithm.
Would you be able to check that it is the correct diagnostic?
If
Currently blocked on Kinetic and Jammy by those bugs:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973037
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973041
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
See https://github.com/rust-lang/llvm-project/pull/121
This is required for rustc 1.59, which in turn is required for Firefox
100 and related tunderbird.
** Affects: llvm-toolchain-13 (Ubuntu)
Importance: Undecided
Status: New
** Affects: llvm-toolchain-13
** Tags added: rls-jj-incoming rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973037
Title:
llvm-toolchain-13: please backport upstream D115098 for rust
To manage notifications
This is necessary for rustc 1.59, which in turn is needed for Firefox
100.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973037
Title:
llvm-toolchain-13: please backport upstream D115098 for rust
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1010150:
Source: llvm-toolchain-13
Version: 1:13.0.1-3
Severity: normal
Tags: patch upstream
Control: affects + rustc
Dear Maintainer,
Please backport upstream https://reviews.llvm.org/D115098
It is needed for rust 1.59,
Update of the patch to add additional dep-3 Bug-Ubuntu field.
** Patch added: "libnet-ssleay-perl.kinetic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libnet-ssleay-perl/+bug/1972795/+attachment/5588508/+files/libnet-ssleay-perl.kinetic.debdiff
--
You received this bug notification
Attached is a debdiff for this change, as reviewed by the Debian
maintainer. As indicated on the bug there, this will not be uploaded to
Debian until their 3.0 transition starts, hence the need to introduce a
delta in Ubuntu.
You can find a built version of the package in my PPA:
Hi,
The libssl1.1 package was provided by the 1.1.1 branch of OpenSSL, which
is obsolete and will cease to receive security support from upstream in
2023. We chose to migrate the archive to the new 3.0 version. See this
ML thread for more details: https://lists.ubuntu.com/archives/ubuntu-
** Tags added: rls-kk-incoming
** 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/1972056
Title:
[openssl3] please sync openssl.cnf to ease changing security level
To
** 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
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1010795:
Hi!
In Ubuntu, we've noticed that when using OpenSSL 3.0, the autopkgtests
for this package systematically fail on new upstream revisions, needing
a package rebuild every time. This patch should address this issue
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
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:
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: 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
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
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:
101 - 200 of 668 matches
Mail list logo
