Sorry about that.
There are not failures on Focal, but there were a bunch of old passes,
so I've retriggered them.
I'm investigating what's happening with the Impish one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Verifying the bug for Impish.
First, make sure that the bug is reproduceable:
# apt policy snmpd
snmpd:
Installed: 5.9+dfsg-3ubuntu2
Candidate: 5.9+dfsg-3ubuntu2
Version table:
*** 5.9+dfsg-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /va
Thanks for the followup, Jeff.
I tried to reproduce the bug locally but failed. Here are the steps I
did:
1) Inside a Focal test environment, installed all the libvirt packages
mentioned by you.
2) Verified that the iptables rules added by libvirt are also present,
as in your case.
3) Edited (
Interesting. I did a quick search here and found many reports of other
people having this problem (or at least something very similar) in other
distros. Eventually they all led to
https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/586.
Either way, I agree that seeing these apparmor denials is n
Hi Owen,
I could not find a libzip4 package whose version is
1:1.0.1-0+16.04+xenial+build6 anywhere in the Ubuntu official archive,
so I'm assuming that this is a third-party package you have installed in
your system (and as such, we don't provide support for it).
But just to reply to your questi
Thank you for the extra information.
Looking at the PNG file you've attached, I see a bunch of I/O error
messages being displayed while trying to access the device. I'm not an
expert here, but it looks to me like there may be a hardware problem
involved? Why are you seeing so many I/O errors? A
Thank you for taking the time to file a bug report.
From DpkgTerminalLog.txt I see the following error:
Setting up samba-common-bin (2:4.15.5~dfsg-0ubuntu5) ...
Checking smb.conf with testparm
Load smb config files from /etc/samba/smb.conf
lpcfg_do_global_parameter: WARNING: The "idmap backend" o
Thanks for taking the time to test the patch, Kamal :-).
As Athos already mentioned above, we will need a reproducer in order to
move forward with the SRU. Unfortunately this means that the bug will
be put in our queue until someone has the time to work more on it and
come up with a way to reprod
Good catch, Seth :-).
Apparently this topic has been discussed in the past in bug #1822370 and
https://lists.debian.org/debian-devel/2019/04/msg00010.html. Those
discussions resulted in the decision to revert the IPQoS default values
from openssh, which is something we're still doing. The defaul
Thank you for the followup, Lars.
Based on your comment (and if I understood it correctly), the issue was
caused because of a local configuration choice instead of a bug in the
package itself. Therefore, I'm closing this bug as Invalid. Feel free
to reopen it and provide more details if you don'
I've added a task for Focal, but if this proves to be a real bug we
might need to add tasks for the other series targeted by the initial bug
(I/J/K).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19696
Thank you for taking the time to report the bug and make Ubuntu better.
The latest version of samba in Focal (2:4.13.17~dfsg-0ubuntu0.21.04.2)
was uploaded exactly because of a printing issue related to the Windows
2021-10 Monthly Rollup patch. You can see more details about the issue
in the bug
** Tags removed: server-todo 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/1970264
Title:
autofs fails to mount nfs4 shares with "error 0x3 getting portmap
client"
To manage n
** Changed in: backuppc (Ubuntu)
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/1971262
Title:
Merge backuppc from Debian unstable
** Changed in: openipmi (Ubuntu)
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/1971303
Title:
Merge openipmi from Debian unstable
** Changed in: nmap (Ubuntu)
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/1971298
Title:
Merge nmap from Debian unstable for kine
** Changed in: bind9 (Ubuntu)
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/1971250
Title:
Merge bind9 from Debian unstable
** Changed in: net-snmp (Ubuntu)
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/1971295
Title:
Merge net-snmp from Debian unstable
** Changed in: openldap (Ubuntu)
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/1971305
Title:
Merge openldap from Debian unstable
** Changed in: rsync (Ubuntu)
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/1971319
Title:
Merge rsync from Debian unstable
** Changed in: sssd (Ubuntu)
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/1971327
Title:
Merge sssd from Debian unstable for kine
** Changed in: squid (Ubuntu)
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/1971325
Title:
Merge squid from Debian unstable
On Wednesday, May 04 2022, Michael Kiermaier wrote:
> Thanks you for the detailed response.
>
> I have to say that this was the first time that I was confronted with
> the 'proposed'-repository. I followed the instructions at
> https://wiki.ubuntu.com/Testing/EnableProposed without too much
> inve
On Wednesday, May 04 2022, Michael Kiermaier wrote:
> @Brian Murray
> In the process, I see the following:
>
> apt-get install autofs/jammy-proposed
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Selected version '5.1.8-1ubuntu1.1' (Ubuntu:
** 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/1970940
Title:
apparmor is preventing access to user copied files in
/var/lib/libvirt/images/ thus resulting in
Thanks for taking the time to report a bug and help improving Ubuntu.
I will try to reproduce it locally first, and will get back when I have
more info.
Thanks.
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Thank you for taking the time to report the bug and make Ubuntu better.
I am trying to obtain access to a setup where I can attempt to reproduce
the issue as described in the bug description (thanks for the detailed
instructions, by the way!). I'll let you know when I have more info,
but meanwhil
Added tasks for B/F/J/K, and marked B/F as Triaged according to Athos'
comment above. We should verify if the bug still applies to J/K (it
probably does) and set the tasks accordingly.
** Also affects: postgresql-common (Ubuntu Kinetic)
Importance: Medium
Status: Triaged
** Also affect
** Changed in: net-snmp (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806421
Title:
perl_bulk_gets patch breaks some scripts
To manage notifications
** Changed in: screen (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466992
Title:
screen crashed with SIGABRT
To manage notifications about this bug
From the description this bug affects Jammy and Kinetic, so I added
explicit tasks for each series.
** Also affects: qemu (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Kinetic)
Importance: Undecided
Status: Triaged
** Changed in: qemu (Ubuntu
Thank you for taking the time to file a bug report.
I'm afraid we will need more information in order to investigate this.
Could you please provide steps to reproduce the problem? Can you
reliably reproduce it? Is there any coredump file available after the
crash?
Since there is not enough info
I'm marking this bug as Triaged and subscribing ubuntu-server to it just
to follow our triaging procedure.
** Changed in: krb5 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Description changed:
[ Impact ]
NFSv4-only shares cannot be automounted if the server isn't running (or
is blocking) rpcbind, even though NFSv4 doesn't require rpcbind anymore.
[ Test Plan ]
You will two Jammy VMs (unfortunately lxd VMs won't work, so you will
likely need t
** Description changed:
+ [ Impact ]
+
+ NFSv4-only shares cannot be automounted if the server isn't running (or
+ is blocking) rpcbind, even though NFSv4 doesn't require rpcbind anymore.
+
+ [ Test Plan ]
+
+ You will two Jammy VMs (unfortunately lxd VMs won't work, so you will
+ likely need t
Thanks for the further info, Michael.
I was able to reproduce the problem here. The trick was to mount the
share from another VM. I was able to backport the upstream patch, build
autofs with it and verify that it indeed fixes the problem.
Unfortunately, it seems that upstream hasn't pushed the p
Thanks for taking the time to report this bug, Sebastian.
I'm adding it to the Ubuntu Server queue; as you mentioned, this is a
relatively old issue and IIUC there's been some pushback to implement
this. As Christian mentioned in the Debian bug, enabling write access
via the apparmor profile by d
affects: autofs (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: server-todo
** Changed in: autofs (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: autofs (Ubuntu Kinetic)
Assignee: (unassigned) => Sergio Durigan Junior (
On Wednesday, April 27 2022, Fedon Kadifeli wrote:
> I have a Google Cloud instance (x86_64), a local VirtualBox virtual
> desktop instance (x86_64), and an Oracle Cloud (aarch64) instance, as I
> mentioned above. I haven't upgraded my physical notebook yet.
>
> I can test your PPA on any or all o
** Bug watch added: Debian Bug tracker #915147
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915147
** Also affects: strongswan (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915147
Importance: Unknown
Status: Unknown
--
You received this bug notification beca
While Lucas works on obtaining access to a similar setup, do you think
you can provide us with any useful log? For example, you mentioned that
the system crashed; is there any interesting log related to the crash?
Thanks in advance.
--
You received this bug notification because you are a member
No problem and thanks for the feedback, Andrea.
Since the bug seems have been fixed in the version currently available,
I am marking this bug as Fix Released. Feel free to reopen it if you
think the bug is still valid.
Thanks.
** Changed in: samba (Ubuntu)
Status: Incomplete => Fix Relea
FWIW, I've verified that the Impish ruby2.7 package still fails on
ppc64el when built using GCC 11. We don't ship ruby2.7 on Jammy
anymore, so I'm targetting this bug to Impish.
** Also affects: ruby2.7 (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: ruby2.7 (Ubuntu Im
** Also affects: run-one
Importance: Undecided
Status: New
** Changed in: run-one (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400197
Title:
* Changed in: bind9 (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: bind9 (Ubuntu Kinetic)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: bind9 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu Jammy)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197025
https://bz.apache.org/bugzilla/show_bug.cgi?id=65731
This bug was fixed and backported to v2.4.52:
https://github.com/apache/httpd/pull/281
Any chance that this fix get backported to the Bionic and Focal Package?
** Changed in: apache2 (Ubuntu Bionic)
Assignee: (unassigned) =>
** Changed in: freeipmi (Ubuntu Focal)
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/1962743
Title:
[BPO] freeipmi/1.6.9-2 from Jammy to Focal
To manage noti
** Description changed:
[ Impact ]
When creating a SNMPv3 user, the net-snmp-create-v3-user script fails to
write the generated configuration file with the following error:
# net-snmp-create-v3-user -ro -A MD5 -a XX -x Y -X DES Z
adding the following line to /var/lib/sn
** Description changed:
+ [ Impact ]
+
+ When creating a SNMPv3 user, the net-snmp-create-v3-user script fails to
+ write the generated configuration file with the following error:
+
+ # net-snmp-create-v3-user -ro -A MD5 -a XX -x Y -X DES Z
+ adding the following line to /var/lib/sn
)
Importance: Undecided
Status: New
** Changed in: net-snmp (Ubuntu Impish)
Importance: Undecided => High
** Changed in: net-snmp (Ubuntu Impish)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: net-snmp (Ubuntu Jammy)
Assignee: (unassigned) => Sergi
On Tuesday, April 19 2022, Fantu wrote:
> done a fast rebuild of rdeps in another ppa:
> https://launchpad.net/~fantonifabio/+archive/ubuntu/freeipmi-backports
> all uploaded after freeipmi build was published in the ppa
Thanks, Fabio.
I've just uploaded the package to focal-backports. It's no
On Tuesday, April 19 2022, Fantu wrote:
> Hi, thanks for reply, 1.6.9-2~bpo10+1~bpo20.04.1 was a mistake and some days
> ago I fixed removing ~bpo10+1, where you still view
> 1.6.9-2~bpo10+1~bpo20.04.1?
> When I'll have time I'll try to do rdeps build in a ppa
Hey Fabio,
Thanks. I was reviewi
Ah, there's actually something else: as Andreas mentioned before, one of
the things we have to check is whether the reverse-depends of the
package will build fine with the new version. I looked at your
backports PPA linked above but couldn't find the rdeps there.
Here's the list:
$ reverse-depen
Thanks for the bug report, Fabio.
I reviewed the branch where you put the backport patch and it seems
mostly good to me. The only comment I have is about the version string
you chose:
1.6.9-2~bpo10+1~bpo20.04.1
I understand that this is probably because you based your work on top of
the backpor
I was also able to confirm this by using a Jammy VM (launched with lxd)
and then launching a Focal container inside it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969247
Title:
mysql-server inst
Thanks, Łukasz. FWIW it was a bit confusing to choose a proper version
number and there was some discussion about it in the MPs.
Either way, the verification for both uploads, as explained in the SRU
template, is to make sure that the autopkgtests are passing. I have now
verified that everything
Verification for Focal:
First, verifying that the bug manifests with the current package:
# apt policy openssh-client
openssh-client:
Installed: 1:8.2p1-4ubuntu0.4
Candidate: 1:8.2p1-4ubuntu0.4
Version table:
*** 1:8.2p1-4ubuntu0.4 500
500 http://archive.ubuntu.com/ubuntu focal-upd
I still haven't been able to sit down and work on this issue. My
comment #31 still applies, though.
I think I have deleted the PPA by mistake. I can recreate it and
reupload the package, but I'm not making any promises to maintain the
PPA nor to backport security fixes; it's just a workaround.
Thanks for confirming the Ubuntu release where this is happening,
sascha.
I spent a few minutes trying to understand what may be happening here
(and reading the Lucas mentioned above), but so far I have to confess
that I am still a bit lost.
Would it be possible for you to provide a step-by-step
Thank you for providing further info, Marcus. This is exactly what we
needed in order to continue the investigation.
The following line from the Jammy log file caught my attention:
Apr 13 00:50:01 slim nm-openvpn[3337388]: OpenSSL: error:0A00018E:SSL
routines::ca md too weak
This is the reason
Ubuntu Xenial has reached end of standard support, so I marked its task
as Won't Fix.
** Changed in: openconnect (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.launch
Thanks for the thorough investigation, Athos.
After reading the bug description, the github issue, the PR, and also
taking a detour trying to figure out why sbcl doesn't build on all
architectures in Ubuntu, I'm a +1 for the changes.
Uploaded:
$ dput pgloader_3.6.3-1ubuntu1_source.changes
Trying
Impish)
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/1968387
Title:
ubuntu-fan fails to set https_proxy when running the "docker&q
docker.io is blocked on focal-proposed due to an unrelated failure with
ubuntu-fan, described in bug #1968387. I found a fix for the problem
and uploaded the package to Focal; now we have to wait for the SRU team
to review and approve it.
--
You received this bug notification because you are a m
This is a low priority bug, and I believe it should be addressed in
Debian first. For that reason, we're still waiting to see what Debian
replies. On top of this, we have to consider that this bug is part of a
much bigger discussion on how to properly implement network ordering
when starting syst
The Focal package has been uploaded.
I'm waiting on apw's reply to upload the Jammy package.
** Description changed:
+ [Impact]
+
ubuntu-fan currently fails to properly set the $https_proxy variable
when running the "docker" dep8 test on autopkgtest.u.c.
At the time of this writing thi
:44:06]: test docker: ---]
autopkgtest [03:44:06]: test docker: - - - - - - - - - - results - - - - - - -
- - -
docker FAIL non-zero exit status 1
** Affects: ubuntu-fan (Ubuntu)
Importance: High
Assignee: Sergio Durigan Junior (sergiodj)
Status: In
On Thursday, April 07 2022, Lena Voytek wrote:
> From testing it seems this shows up due to swtpm_setup using the openssl
> config for key setup information. I managed to fix the issue by adding
>
> #include
>
> to the TEMPLATE.qemu file in the apparmor directory. I tested with the
> ppa:
>
> ppa
Thanks for the patches, Lucas.
I built the packages locally using them and everything succeeded.
LGTM, +1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960449
Title:
Backport container stack in
A bit more info because this bug came up again for me.
It was mentioned that this was working OK in Trusty, so I assume that
openssh 6.6 was being used there, and that when the upgrade to openssh
7.x happened this issue started happening. I agree that the tool itself
could be more helpful in its
Hi,
I'm trying to reproduce this bug to see if it's still valid, but so far
I haven't had much success. I tried crafting a /etc/sssd/sssd.conf
using Jens' diff, but after using sss_obfuscate on it I only see a small
excerpt being added to the end of the config file, and no lines being
removed.
I
Still present in Jammy; also confirmed in Bionic and Focal.
Unfortunately, there hasn't been any movement upstream regarding this
bug.
** Also affects: spamassassin (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: spamassassin (Ubuntu Focal)
Importance: Undecided
** Description changed:
+ [Impact]
+
+ When using "ssh-keygen -R" to remove a host from "known_hosts" the
+ command changes permissions on the file. This can cause problems
+ particularly when used on the global "known_hosts" file
+ (/etc/ssh/ssh_known_hosts), because then only root can read it.
purpose, as can be seen on this
excerpt (from ssh-keygen.c:do_known_hosts):
...
fchmod(fd, sb.st_mode & 0644);
...
I have already backported & tested the patch on Bionic, and it works. I will
start filing MPs tomorrow.
** Changed in: openssh (Ubuntu Bionic)
Assignee: (unassigned)
** Bug watch added: OpenSSH Portable Bugzilla #3146
https://bugzilla.mindrot.org/show_bug.cgi?id=3146
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=3146
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Thank you for taking the time to file a bug report.
I don't know if I fully understand the issue here. I installed dropbear
inside a container, started it, and then ran ssh-copy-id on the host in
order to copy my public key to the dropbear server. It got copied
successfully and I was able to log
** 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/1966923
Title:
exiqgrep -r and -f options match all messages if no
To manage notifications about this bug go to:
https://bug
: New => Triaged
** Changed in: exim4 (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Bug watch added: Debian Bug tracker #1006661
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006661
** Also affects: exim4 (Debian) via
https://bugs.debian.org/cgi-bin/bu
Thanks for the follow-up, Lena and EOLE team.
Unfortunately the fix for the bug is not present in the samba 4.13
series, which is what we ship on Focal/Impish (4.13.17, to be more
specific). So, although I haven't tried to reproduce the bug in F/I, I
believe it will still be present there.
We wi
** Changed in: bind9 (Ubuntu Jammy)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965981
Title:
[FFe] Update bind9 to 9.18.1
** Changed in: bind9 (Ubuntu Jammy)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965981
Title:
[FFe] Update bind9 to 9.18.1
To manage notifications about this bug
** 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 fix
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.
https://bugs.launchpad.net
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 ni
op, but
it never 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 (atho
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.
https://bugs.launchp
** 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 fault
** 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:
https://bugs.launchpad
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 --o
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 becau
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
se
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.
ht
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 a
** 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:
https
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
301 - 400 of 1104 matches
Mail list logo
