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.
** 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
** 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
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
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
)
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 (sergiodj)
--
You received th
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
** 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
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
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
** 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:
tu 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 Ubuntu.
https://bugs.laun
** 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.
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) => Sergio D
** 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
** 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
** 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
)
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
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
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:
$
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
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
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
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
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.
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
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 "docke
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
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
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
: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:
>
>
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.
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
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) => Ser
** 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
** 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:
=> 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/bugrepo
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
** 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.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
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
201 - 300 of 1010 matches
Mail list logo
