** Description changed:
Bind9 released version 9.18.1 recently, and we should have it in Jammy.
This new release is already availble in Debian unstable, and contains a
sizeable list of bugfixes. It is the first point release after bind9
9.18.0, and the project has a track record of
at the same time. [GL #3141]
The last 2 changes seem trivial; the first one seems to aim at a specific
scenario and I find it unlikely that it will affect most users.
** Affects: bind9 (Ubuntu)
Importance: High
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
Hello Thomas,
I still cannot reproduce this issue, so I would like to know if you
could test the bind9 package from the following PPA and let me know if
it fixes your problem:
https://launchpad.net/~sergiodj/+archive/ubuntu/bind9-bugfix
It contains the backported patches from the upstream Merge
** Changed in: bind9 (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: server-todo
** Changed in: bind9 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Friday, March 18 2022, Romain Geissler wrote:
> I could successfully validate that the fix works. I initially installed
> the current official jammy package, it was hanging again, then I
> installed your ppa repo and upgraded the packages, and it worked. See
> the following relevant part of my
Thanks for the reply, Romain.
I have prepared a PPA with the current bind9 package in Ubuntu Jammy +
the patches from the MR you linked. You can find it here:
https://launchpad.net/~sergiodj/+archive/ubuntu/bind9-lp1964686
Let me know if this solves the problem for you.
Although it would be
ever seems to crash.
Anyway, I've talked to Athos and reassigned the bug to myself. I will
prepare an MP for it soon, but I'd like to be able to reproduce the bug
first. I will keep investigating here.
** Changed in: bind9 (Ubuntu)
Assignee: Athos Ribeiro (athos-ribeiro) => Sergio D
Verified that the patch provided by:
https://github.com/strongswan/strongswan/commit/3eecd40cec6415fc033f8d9141ab652047e71524
fixes the issue. I'm preparing an MP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: strongswan (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964977
Title:
pki segmentation fa
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964977
Title:
pki segmentation fault on openssl plugin
To manage notifications about this bug go to:
Thanks for taking the time to report the bug.
I can easily verify it here. Here's a step-by-step reproducer:
$ lxc launch ubuntu-daily:jammy ipsec-bug1964977
$ lxc shell ipsec-bug1964977
# apt update && apt full-upgrade -y
# apt install strongswan strongswan-pki
# ipsec pki --gen --size 4096
As it turns out, the "dig" failure I mentioned in comment 2 may not be
entirely related to bug #1964400. I took the liberty of repurposing one
of bind9's old bugs to make sure we're also tracking those failures.
It's bug #1258003, if you're interested.
--
You received this bug notification
I tested on Focal and Bionic; both are OK. This is a Jammy issue.
** Also affects: bind9 (Ubuntu Jammy)
Importance: High
Status: Triaged
** Bug watch added: gitlab.isc.org/isc-projects/bind9/-/issues #3144
https://gitlab.isc.org/isc-projects/bind9/-/issues/3144
** Bug watch added:
I'm repurposing this bug because dig +nssearch is crashing again in
bind9 9.18:
# dig +nssearch isc.org.
SOA ns-int.isc.org. hostmaster.isc.org. 2022031252 7200 3600 24796800 3600 from
server 149.20.1.73 in 59 ms.
SOA ns-int.isc.org. hostmaster.isc.org. 2022031252 7200 3600 24796800 3600 from
Upstream bugs:
https://gitlab.isc.org/isc-projects/bind9/-/issues/3144
https://gitlab.isc.org/isc-projects/bind9/-/issues/3207 (somewhat
related; the crash happens at the same place)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Couldn't reproduce this on Jammy.
** Changed in: bind9 (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/1085593
Title:
bind 9.8.1-P1 crashes with an
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668474
Title:
AH00526 when using long ProxyPass worker name
To manage notifications about this bug go to:
Thanks for reporting this bug.
As Seth said, it seems unlikely that this is ssh's fault. I don't have
an easy way to use virtualbox/packer here, so I'm wondering if you could
either provide more info (as Seth also requested) or an out-of-the-box
way to reproduce what you're seeing (i.e., without
I've opened
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1964829 to track
the AH02808 warning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668474
Title:
AH00526 when using long
For the 2.4.x series, upstream fixed this bug here:
https://github.com/apache/httpd/pull/288
https://github.com/apache/httpd/commit/d05b8b921997930f1f75b42be4cb27f94859e3a0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Note: This is related to
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1668474
When using a ProxyPass worker name whose length is greater than 96
chars, one will see the following warning on apache2's logs:
Mar 14 21:27:49 test-apache2 systemd[1]: Starting The
Trusty has reached EOL and Xenial has reached end of standard support,
so I'm marking their tasks as Won't Fix.
I've verified this bug on Focal and Jammy and found that apache2 on both
systems accepts a worker name whose length is 256 chars, which, although
not great, is the fix provided by
** Changed in: apache2 (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668474
Title:
AH00526 when using long ProxyPass worker name
To manage
Thank you for taking the time to file a bug report.
Based on the attached logs, we can see the following message:
dpkg-deb (sottoprocesso): estrazione componente dell'archivio: errore di lzma:
i dati compressi sono rovinati
dpkg-deb: errore: il sottoprocesso ha restituito lo stato di
errore 2
Thank you for your bug report.
I could indeed reproduce the problem here by following your instructions
from the upstream bug. For those coming after me:
$ lxc launch ubuntu-daily:impish php-bug1964687
$ lxc shell php-bug1964687
# apt update && apt install -y php
# cat > 1.php << EOF
";
include
Also, please provide the version of the bind9 package you're using for
tests. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964686
Title:
Command "host non-existent-host-name" hangs
I'm marking this bug as Incomplete for now because I can't reproduce it.
Feel free to set its status back to New when you provide more info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964686
Athos just told me that there is already a bug filed for the problem I
reported above:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1964400
So now we're left to trying to reproduce the hang that Romain is seeing
when using the "host" command.
** Changed in: bind9 (Ubuntu)
Status:
Thanks for the bug report, Romain.
I cannot seem to be able to reproduce it here. Here's what I'm doing:
$ docker run --rm ubuntu:jammy /bin/sh -c 'apt update && apt install dnsutils
-y && host -v non-existent-host-name'
...
Trying "non-existent-host-name.localdomain"
Trying
Thank you for taking the time to file a bug report.
Unfortunately there is not enough information here to determine the root
cause of the failure you're seeing. Some things caught my attention,
though:
- The following line (from DpkgTerminalLog.txt):
info: Executing deferred 'a2enmod php7.4'
Given upstream's reply, I am closing this as Won't Fix.
** Changed in: qemu (Ubuntu Impish)
Status: Confirmed => Won't Fix
** Changed in: qemu (Ubuntu Jammy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As usual with non-security updates, we use the results of autopkgtest in
order to perform the verification. In this case, all tests succeeded
for postgresql-13 in Impish. Therefore, tagging as verification-done-
impish.
** Tags removed: server-next verification-needed verification-needed-impish
Thanks for the feedback, Michael.
First of all, let me say that we appreciate the help you've been
providing here. Given that we are not able to reproduce the bug here,
we depend on your reports in order to make progress and take decisions
regarding it.
Unfortunately, I think it will be hard
Thanks for the bug report and sorry for the delay; this apparently fell
through the cracks.
The upstream bug you pointed as being a possible match still hasn't
received any replies in all these years. Can you confirm whether you're
still experiencing this bug, and if yes, could you provide steps
Thanks for writing this bug report and help making Ubuntu better.
I'd like to take a step back here and ask a few questions regarding the
bug description. The errors you mentioned seem to be related to the
$stopcond variable that gets created on line 884, like this:
my $stopcond =
This bug was fixed in the package upower - 0.99.16-2
Sponsored for Rik Mills (rikmills)
---
upower (0.99.16-2) unstable; urgency=medium
* Cherry-pick FD handling fixes from upstream (Closes: #1006368)
-- Michael Biebl Sat, 26 Feb 2022 10:43:19 +0100
** Changed in: upower
Filed a bug against upstream backuppc as well.
** Bug watch added: github.com/backuppc/backuppc/issues #461
https://github.com/backuppc/backuppc/issues/461
** Also affects: backuppc via
https://github.com/backuppc/backuppc/issues/461
Importance: Unknown
Status: Unknown
--
You
I investigated this bug and found that it's possibly a regression
introduced in the 4.15.x series of Samba.
In a nutshell, Samba offers guest authentications (i.e., when
username/password are provided but are ignored by libsmbclient, which
will map the request to the Guest user configured on
** Changed in: samba (Ubuntu)
Status: New => Triaged
** Changed in: backuppc (Ubuntu)
Assignee: Andreas Hasenack (ahasenack) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All packages have been uploaded and are now waiting for review/approval.
** Changed in: postgresql-10 (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: postgresql-12 (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: postgresql-13 (Ubuntu Impish)
** Changed in: sssd (Ubuntu)
Status: In Progress => 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/1946904
Title:
Merge sssd from Debian unstable for 22.04
To manage
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/openvpn/+git/openvpn/+merge/415977
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946884
Title:
Merge openvpn from
** Changed in: openvpn (Ubuntu)
Status: Incomplete => 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/1946884
Title:
Merge openvpn from Debian unstable for 22.04
To manage
I coordinated with Bryce and will be doing the merge of openvpn in the
next few hours.
** Changed in: openvpn (Ubuntu)
Assignee: Bryce Harrington (bryce) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
*** This bug is a duplicate of bug 1946884 ***
https://bugs.launchpad.net/bugs/1946884
I'm working on this one.
** This bug has been marked a duplicate of bug 1946884
Merge openvpn from Debian unstable for 22.04
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1946884 ***
https://bugs.launchpad.net/bugs/1946884
Thanks for the report. I've marked this bug as a dupe of bug #1946884,
because that's where we're keeping track of our merges for this cycle.
I should put an MP up for the new openvpn in the next few
** Changed in: osk-sdl (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/1956534
Title:
dep8 tests fail with libsdl >= 2.0.18
To manage notifications
** Changed in: guile-3.0 (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/1956636
Title:
FTBFS with glibc 2.34
To manage notifications about this bug
** Changed in: squid (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/1946903
Title:
Merge squid from Debian unstable for 22.04
To manage notifications
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/postgresql-13/+git/postgresql-13/+merge/415812
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961127
Title:
New
On Friday, February 18 2022, Christian Ehrhardt wrote:
> Thanks - That is good as a sniff test, but as I've mentioned the real
> test is when the hundreds of autopkgtest-enabled dependencies of
> postgres run in autopkgtest. Since currently the queues are rather full
> we agreed to do this
autopkgtest results for postgresql-13 are good:
Results from
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4785/?format=plain:
postgresql-13 @ amd64:
17.02.22 17:03:57Log ️ ✅ Triggers:
['postgresql-13/13.6-0ubuntu0.21.10.1~ppa1']
postgresql-13
There's a new upstream version of telegraf, so I'm working on merging it
now.
** Changed in: telegraf (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
: Undecided
Assignee: Athos Ribeiro (athos-ribeiro)
Status: New
** Affects: postgresql-13 (Ubuntu Impish)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: In Progress
** Affects: postgresql-14 (Ubuntu Jammy)
Importance: Undecided
Thanks for reporting the bug.
I'm wondering here if we can get a step-by-step reproducer for this
issue focusing on MySQL. This seems to be a somewhat complex scenario
which demands a non-trivial amount of work to set up. Thanks.
--
You received this bug notification because you are a member
Thank you for this bug report.
It seems that it affects only Xenial installations, is that correct?
Would you be able to confirm whether this still applies for
Bionic/Focal/Jammy?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for the follow up, Andrea. Can you confirm the version of
Samba you have installed there? We want to make sure whether this bug
is present in the latest Samba version or not. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: sssd (Ubuntu)
Status: Incomplete => 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/1946904
Title:
Merge sssd from Debian unstable for 22.04
To manage notifications
The fixed package is now in jammy-proposed.
** Changed in: lbzip2 (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/1926092
Title:
lbzip2 package is
Hirsute has reached EOL, but there is a fixed package in jammy-proposed
now.
** Changed in: lbzip2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Xenial has reached end of standard support.
** Changed in: dnsmasq (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531184
Title:
[SRU] dnsmasq
Xenial has reached end of standard support.
** Changed in: open-iscsi (Ubuntu Xenial)
Status: Triaged => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Xenial has reached end of standard support.
** Changed in: mysql-5.7 (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877442
Title:
Broken SQL
Xenial has reached its end of standard support.
** Changed in: apache2 (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload
Trusty has reached its end of standard support.
** Changed in: krb5 (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817955
Title:
Getting new "DN
Trusty has reached its end of standard support.
** Changed in: ocfs2-tools (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584629
Title:
Failed
Trusty has reached its end of standard support.
** Changed in: mysql-5.6 (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633485
Title:
Backport
Xenial has reached its end of standard support.
** Changed in: mysql-5.7 (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745185
Title:
If apt-get
Xenial has reached its end of standard support.
** Changed in: resource-agents (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789527
Title:
Xenial has reached its end of standard support.
** Changed in: haproxy (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828496
Title:
service
Trusty has reached its end of standard support, so this bug will not be
fixed for that release.
** Changed in: pacemaker (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Xenial has reached its end of standard support.
** Changed in: resource-agents (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589531
Title:
Trusty has reached its end of standard support, so this bug won't be
fixed for that release.
** Changed in: pacemaker (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Xenial and Trusty have reached end of standard support.
** Changed in: unbound (Ubuntu Trusty)
Status: Triaged => Won't Fix
** Changed in: unbound (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bionic, which is the latest Ubuntu release where nagios3 can be found,
ships nagios3 3.5.1.dfsg-2.1ubuntu8. This means that the fix is already
present there. Therefore, closing this as Fix Released.
** Changed in: nagios3 (Ubuntu)
Status: Triaged => Fix Released
--
You received this
I double checked the errors.u.c URL
(https://errors.ubuntu.com/problem/e10ccfadbdf98b7b2db8b873073f4f33b27e7179)
and verified that the vast majority (if not all) reports have come from
Ubuntu Xenial users. Since Ubuntu Xenial has reached its end of
standard support, I'm therefore marking this bug
Sorry about the delay in replying to this bug.
From the bug description, it seems to me that this issue happened while
using Ubuntu Xenial (16.04); is that correct? I know it has been a
while, but can you still reproduce the issue? If yes, are you able to
describe the steps necessary to trigger
** Tags added: network-online-ordering
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894190
Title:
snmpd starts before the network stack is fully online (network.target
vs network-online.target)
Xenial has reached end of standard support, so I'm marking this bug as
Won't Fix.
** Changed in: sssd (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: squid (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/1946205
Title:
squid: Fail to build against OpenSSL 3.0
To manage notifications
Dimitri,
I don't know if this will suffice. With glibc's decision to remove
libpthread, I believe we will need to explicitly copy libpthread.so, at
least temporarily until everything else doesn't explicitly link against
it.
Taking the stub binary your MP is generating as an example (running on
Yes, that's my take as well. I was going to proposed a patch to do just
that but I decided to see if there was another way to just selectively
copy lib{gcc_s,pthread}. I don't think it's worth the hassle, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
On Wednesday, February 02 2022, Andreas Hasenack wrote:
> Sync requested, I'll wait for the package to migrate before closing the
> bug.
You can also invoke "syncpackage" using the "--bug" option, FWIW.
--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14
--
You received
Thanks for the bug report, Norbert.
First of all, I noticed that the ocfs2-tools package contains a delta
relative to the Debian package. The delta is trivial, though, and is
there just to make sure the package is built only on support
architectures (see bug #1745155 for more details). I don't
This is impacting ruby-tilt, whose autopkgtest is failing on ppc64el
right now. It's important to mention that Debian apparently isn't
impacted by this, which probably means that the error might be happen
somewhere else.
Note to self: glibc 2.34 doesn't ship with a separate libpthread
anymore,
I debugged this a little bit and found that the difference manifests on
ruby3.0's load.c:require_internal, more specifically this part here:
1118 if (found) {
1119 if (!path || !(ftptr = load_lock(th->vm, RSTRING_PTR(path),
warn))) {
1120 result = 0;
1121
Public bug reported:
I have verified that under specific circumstances, 'require' can behave
differently between ppc64el and other architectures.
Simple reproducer:
$ cat > foo.rb << __EOF__
begin
require 'bar'
rescue LoadError
puts "Caught first LoadError. Continuing..."
end
puts require
docker.io is also affected:
https://git.launchpad.net/ubuntu/+source/docker.io/tree/debian/rules?h=ubuntu/jammy=18b9d33de2adcb7ec361e4789f1f96223e80d607#n109
** Also affects: docker.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Changed in: openldap (Ubuntu)
Status: New => 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/1946883
Title:
Merge openldap from Debian unstable for 22.04
To manage
As it turns out, the situation is a bit more complex. Although ufw does
provide the ufw-directoryserver profile, for some reason we don't
install ufw profiles on Ubuntu:
https://git.launchpad.net/ufw/tree/debian/rules?h=ubuntu/master#n90
I'm not sure why that is the case, and git-blame isn't
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958594
Title:
Boot error: libgcc_s.so.1 must be installed for
** 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/1958594
Title:
Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
To manage notifications about this
This has migrated.
** Changed in: kronosnet (Ubuntu)
Status: Fix Committed => 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/1945796
Title:
kronosnet: Fail to build against
Thanks Wido for reporting the bug and Fantu for finding the underlying
reason why it's not working.
As Fantu said, this code is disabled on Ubuntu Focal. It is extremely
unlikely that we will re-enable it given that the code has been disabled
because the upstream maintainer doesn't feel
Thank you for taking the time to file a bug report.
Unfortunately I didn't understand the problem very well. It seems to me
that this could be a local configuration issue, although you mentioned
that this was working before Impish. Also, I noticed that you marked
the bug as Invalid for bind9.
Hello Claude,
It should be straightforward to downgrade the package on Focal, because
the previous version is still in the -release pocket. You can simply:
# apt install rsync=3.1.3-8
and it should do the trick.
While at it, would it be possible for you to provide a step-by-step
reproducer
*** This bug is a duplicate of bug 1955588 ***
https://bugs.launchpad.net/bugs/1955588
Thank you for taking the time to file a bug report.
I appreciate the fact that you attached the stack trace and tried to
provide more information about the segfault, but I would like to take a
step back
Thank you for taking the time to file a bug report.
Looking at your DpkgTerminalLog.txt file, I see the following excerpt:
Setting up mysql-server-8.0 (8.0.27-0ubuntu0.20.04.1) ...
update-alternatives: warning: alternative /etc/mysql/mariadb.cnf (part of link
group my.cnf) doesn't exist;
Although the package is still in -proposed, I'm marking this bug as Fix
Released. This was fixed in version 1:16.16.1~dfsg+~2.10-2.
Thanks.
** Changed in: asterisk (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Today, the OpenLDAP project announced that they're changing their
release process in order to have LTS and Feature releases:
https://lists.openldap.org/hyperkitty/list/openldap-
annou...@openldap.org/thread/2QQNVWPUUG54JM7FGQHMMF3H4KS2PPKQ/
They've also announced that OpenLDAP 2.5 will be their
301 - 400 of 1060 matches
Mail list logo
