Attach file ec2-sru-20.2.45.txt.
** Attachment added: "ec2-sru-20.2.45.txt"
https://bugs.launchpad.net/bugs/1881018/+attachment/5383085/+files/ec2-sru-20.2.45.txt
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would
** Changed in: postfix (Ubuntu Focal)
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/1868955
Title:
[SRU] after upgrade to 20.04: posttls cannot connect to
I'm also experiencing this problem.
Linux nblucas 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
[44262.937772] GpuWatchdog[1602155]: segfault at 0 ip 5616ee370587 sp
7f75ed8b64d0 error 6 in mqtt-explorer.bin[5616eb195000+53d8000]
Hi Robie,
With the proposed change users will not get the error mentioned in the
description while trying to reload the service and get a better error
(reload not supported). The current status is:
1 - User tries to reload the service
2 - Reload fails
3 - User gets an error
The problem here is
** Changed in: postfix (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868955
Title:
[SRU] after upgrade to 20
** Description changed:
+ [Impact]
+
+ Users cannot send emails using dane-only policy in Focal.
+
+ In this SRU we are proposing a microrelease update from version 3.4.10
+ to 3.4.11 since the changes are minimal (and also seems there is an
+ authorization from the Tech Board to do that). Here
Good to hear that Jan. I might have messed up my local setup. I'll
proceed with the SRU process to make this fix land in Focal.
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@seb128, yes. It is still in issue on 20.04 (focal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766230
Title:
Strange window matching behaviour between Slack and Chrome
To manage notifications
probably just an packaging issue? pyvenv is officially removed in
python-3.8[1], so the symlink pyvenv should no longer be created?
[1] https://docs.python.org/dev/whatsnew/3.8.html#api-and-feature-
removals
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Nick and @Jan: could you please try postfix 3.4.11 available in the PPA
I mentioned above and give us some feedback? I'd like to confirm that
before asking for help on postfix-users mailing list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: postfix (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868955
Title:
after upgrade to 20.04: posttls cannot connect to private/tlsmgr
Thank you for taking the time to file a bug report.
I tried to reproduce the error you mentioned in a brand new Focal
container and I failed. It works as expected. My attempt was installing
the freeradius package and run the commands you described (check the
config and restart the service).
Are
As you mentioned it is not fixed yet, so I am changing the status to
Triaged. I tried to find a way to link the Github issue to this bug
report but I failed.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you
That was my initial thought. So I am not sure if just a postfix update
to version 3.4.11 (or 3.5.2 in Groovy) fixes the mentioned issue.
FWIW, I have a PPA here with the version 3.4.11 built in Focal and the
behavior is the same as version 3.5.2 in Groovy:
After Scott's comment about updating postfix to 3.4.11 I checked the
changelog of this version and I noticed the only change from 3.4.10 is:
20200416
Workaround for broken builds after an incompatible change
in GCC 10. Files: makedefs, Makefile.in.
Workaround for broken
/7
** Changed in: postfix (Ubuntu)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
** Changed in: postfix (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ntu Focal)
Status: New => Triaged
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: postfix (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Also affects: postfix (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: postfix (Ubuntu Focal)
Status: New => Triaged
** Changed in: postfix (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Released
** Changed in: neutron
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/1881771
Title:
neutron-ipset-cleanup fails with Traceback: Unhandled error:
As Bryce mentioned the bug was fixed in version 5.7.29. The security
team already made available version 5.7.30 in Xenial (and also Bionic).
So the fix is already available if you have the security pocket enabled
in your system.
** Changed in: mysql-5.7 (Ubuntu)
Status: Triaged => Fix
Thank you for taking the time to file a bug report.
Unfortunately, I am not able to reproduce the bug, and I also did not
find any insightful information from your log files. Are you trying to
upgrade from Ubuntu 17.10 "Artful Aardvark" to 20.04 "Focal Fossa"?
Could you please provide some
Thank you for taking the time to file a bug report.
The mysql-server-8.0 package Pre-Depends on mysql-common package which
contains the missing script:
/var/lib/dpkg/info/mysql-server-8.0.postinst: line 191: /usr/share
/mysql-common/configure-symlinks: No such file or directory
Checking the
The piuparts test failures is fixed now. Up to the SRU team to review
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875231
Title:
[SRU] [20.04] Update NGINX version string to 1.18.0
To manage
** Changed in: monitoring-plugins (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881208
Title:
check_disk should look at /proc/mounts, not mtab
To
Thanks for taking the time to report this bug and try to make Ubuntu
better.
Checking the logs I noticed those errors:
2020-05-29T16:59:19.347285Z 1 [ERROR] [MY-012209] [InnoDB] Multiple files found
for the same tablespace ID:
2020-05-29T16:59:19.347488Z 1 [ERROR] [MY-012202] [InnoDB]
Thank you for taking the time to file a bug report.
Even with the information you provided I cannot reproduce the bug you
mentioned. It'd be great to have detailed steps on how to reproduce it.
Moreover, if you believe this bug is related to kernel you also need to
attach some kernel logs.
Since
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
As you mentioned in Trusty /etc/mtab is not
** Also affects: monitoring-plugins (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881208
Title:
check_disk should look at /proc/mounts,
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
Title:
postfix tls deploy-server-cert fails with "can't shift that many"
To manage notifications about this bug go
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
** Changed in: openssh (Ubuntu Focal)
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/1876320
The Debian maintainer suggested to also add a WantedBy= entry in the
Install section:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774970#32
** Also affects: dnsmasq (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu Xenial)
Importance:
** Changed in: mysql-5.7 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881053
Title:
package mysql-server-5.7 5.7.30-0ubuntu0.16.04.1 failed to
Public bug reported:
In version 1.3.4-0ubuntu4 we changed the name of the binary package
containing the dev files to actually match what we have upstream. Some
other packages are currently blocked in proposed because they expect
golang-github-containerd-containerd-dev and the binary does not
I got patches accepted in all the mentioned projects (some of them were
already fixed when I checked). Now we need to wait for a release of
those packages in Debian to sync them.
https://salsa.debian.org/go-team/packages/prometheus-haproxy-exporter/-/merge_requests/1
Actually the new binary package provides the old transitional package:
https://sources.debian.org/src/golang-github-prometheus-client-
golang/1.2.1-3/debian/control/#L36
Yet, I submitted merge requests on salsa for all the mentioned packages
which still build/runtime depend on the old
** Description changed:
[Impact]
The command 'systemctl reload openvpn @ $ foo' is broken for a while and
no one have reported that. Users should not be using it a lot. After
some investigation we notice the restart command does basically the same
thing, and users should be using
** Description changed:
+ [Impact]
+
+ The command 'systemctl reload openvpn @ $ foo' is broken for a while and
+ no one have reported that. Users should not be using it a lot. After
+ some investigation we notice the restart command does basically the same
+ thing, and users should be using
** Changed in: openvpn (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: openvpn (Ubuntu Eoan)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: openvpn (Ubuntu Focal)
Assignee: (unassigned) => Lucas
I brought more people into this discussion and we decided to drop the
reload support from the stable/supported releases since it is already
broken and the restart does basically the same thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: docker.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: docker.io (Ubuntu Disco)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to file a bug report.
Could you please provide some information on how to reproduce this bug?
Which packages you have installed on your system (like mariadb-server)?
Since there is not enough information in your report to begin triage or to
differentiate between a
** Changed in: libseccomp (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: libseccomp (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: libseccomp (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: libseccomp (Ubuntu Xenial)
Importance: Undecided
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: openssh (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Focal)
Status: New => Triaged
** Changed in: openssh (Ubuntu Focal)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Thanks for taking the time to file this bug and try to make Ubuntu
better.
The ruby2.7-dev and libruby2.7 need to be at the same version to work as
expected. So you need to update your libruby2.7 to version
2.7.0-5ubuntu1.1 to make it work with ruby2.7-dev 2.7.0-5ubuntu1.1.
Notice that both
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878887
Title:
[SRU] No
After a discussion with a colleague I think we should leave it as is in
the supported/stable releases (I already fixed it in Groovy, it should
land in the archive soon). The rationale is: even if the reload command
fails the service keeps active and running, the proposed solutions would
not fix
quot; for this to the supported releases.
** Changed in: openvpn (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: openvpn (Ubuntu)
Status: Triaged => In Progress
** Changed in: openvpn (Ubuntu)
Importance: Undecided => Medium
** Changed in:
Executing the ExecReload= command with full privileges (adding '+')
indeed fixes the reload failure (I ran my tests in a Bionic and Focal
VMs but it should apply to the other releases):
May 26 10:01:41 openvpn-reload kill[1764]: kill: (1738): Operation not
permitted
I mean the command 'systemctl
** Also affects: openvpn (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: openvpn (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: openvpn (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: openvpn (Ubuntu Bionic)
Thanks for taking the time to file this bug!
This bug was reported against openvpn in Ubuntu 17.10 which is not
supported anymore. I was not able to reproduce this issue in 18.04 (LTS
version after 17.10), so I am marking it as Invalid.
** Changed in: openvpn (Ubuntu)
Status: Confirmed =>
Thanks for filing this bug and try to make Ubuntu better!
Since there is no response from the reporter for a while and this bug is
reported against Disco (not supported anymore), I am marking it as
Incomplete.
If you still face this issue please reopen (change the Status to New
again) the bug
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878887
Title:
[SRU] No EAP-PEAP support anymore
To manage notifications about this bug go
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879692
Title:
[SRU] Strongswan pki creates CA certificates with invalid Key Usage
flags
To
The proposed package is available here:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/focal-strongswan-
bug-fixes
I performed the test above to check if the CA certificate is generated
correctly:
[in the same container I was using to describe the Test Case section in the
description]
$
** Changed in: strongswan (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: strongswan (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The proposed package is available here:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/focal-strongswan-
bug-fixes
I performed the test above to check if both plugins are installed again
and also if the old conf files were removed:
[in the same container I was using to describe the Test
As @Paride mentioned this issue requires 5 upstream commits because it
does not affect only the pki module. This issue is affecting some
chunk_from_chars calls throughout the code base.
I am working to backport the 5 upstream commits to Focal.
--
You received this bug notification because you
signee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: strongswan (Ubuntu Focal)
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/1879692
Title:
St
** Changed in: cloud-init
Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456277
Title:
cloud-init searches for
** Changed in: gpsd (Ubuntu Focal)
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/1879272
Title:
corrupted json payload when adding a device
To manage
** Changed in: strongswan (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: strongswan (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: strongswan (Ubuntu Focal)
Importance: Undecided => High
*
Public bug reported:
libdbd-mariadb-perl/1.11-3ubuntu2 regressed in all architectures when
tests are executed with mysql-8.0/8.0.20-0ubuntu1, blocking mysql-8.0
migration. For instance this is the amd64 test log:
Thank you for taking the time to file a bug report.
There is not enough information to reproduce this bug. I simply tried to
install mysql-server-8.0 in a clean Focal LXD container and it works
(from the apport log this is a fresh install).
Since there is not enough information in your report to
** Changed in: libvirt (Ubuntu)
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/1879325
Title:
Unable to remove disk metadata on vm
To manage notifications about this
Thanks for reporting this bug and also the provided upstream patch. Just
to make it clear this is the mentioned patch:
https://gitlab.com/gpsd/gpsd/-/commit/733495192307d43c9e3bdd9e1b202045e66d998b
** Also affects: gpsd (Ubuntu Focal)
Importance: Undecided
Status: New
** Tags added:
** Also affects: memcached (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: memcached (Ubuntu Eoan)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for reporting this bug and also the provided patch.
** Tags added: server-next
** Changed in: memcached (Ubuntu)
Importance: Undecided => High
** Also affects: memcached (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: memcached (Ubuntu Focal)
Status:
@Christian the plan you presented looks good to me.
I'd like to take advantage of this discussion and ask @Tobias his
opinion about all the plugins that were removed since 18.04 (the list of
plugins is the same in 20.10 and 20.04):
libstrongswan-eap-aka-3gpp2.so
libstrongswan-eap-dynamic.so
** Also affects: strongswan (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: strongswan (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Alex,
Could you please provide some insight about your use case? The EAP-PEAP
plugin was disabled in Debian and the Debian maintainer prefers to keep
the package simple and not enable too complicated stuff like EAP plugins
[1]. For us to convince them to accept its inclusion back we need some
I confirm the EAP-PEAP plugin is missing, check below.
Bionic:
$ dpkg -c libcharon-extra-plugins_5.6.2-1ubuntu2.5_amd64.deb | grep eap-peap
-rw-r--r-- root/root 777 2019-11-12 08:32
./etc/strongswan.d/charon/eap-peap.conf
-rw-r--r-- root/root 18616 2019-11-12 08:32
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876912
Title:
[SRU] libruby2.7
Now the build on riscv64 was fixed. I tested the package in focal-
proposed and it works as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876912
Title:
[SRU] libruby2.7 provides
The autopkgtest failures were related to some flaky tests, I re-
triggered them and all of them are green now. However, ruby2.7 FTBFS on
riscv64, after a discussion on #ubuntu-devel IRC channel wgrant will
investigate it tomorrow (it might be an issue after upgrading the
riscv64 builders after
*** This bug is a duplicate of bug 1878049 ***
https://bugs.launchpad.net/bugs/1878049
** This bug has been marked a duplicate of bug 1878049
Upgrade rabbitmq-server to v3.8.3 from upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878291
Title:
rabbitmq-server/3.8.2-0ubuntu2 FTBFS in Groovy
To manage notifications about this bug go to:
Public bug reported:
It FTBFS in the same way in all architectures in Groovy, for instance
this the amd64 build log:
https://launchpadlibrarian.net/478890255/buildlog_ubuntu-groovy-amd64
.rabbitmq-server_3.8.2-0ubuntu2_BUILDING.txt.gz
The important part of the log is:
==> rabbitmqctl
** (Mix)
** Changed in: rabbitmq-server (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/1878049
Title:
Update debian/watch file to download from GitHub
To manage
Thank you for taking the time to file a bug report.
I was not able to reproduce the error your reported installing just
mysql-server-8.0 in an Ubuntu Eoan container. Could you provide any
information on how you installed DBeaver?
Since there is not enough information in your report to begin
Thank you for taking the time to file a bug report.
The version 11.1.0 is still not available either in Ubuntu nor in
Debian. Since the Debian maintainer is considering/reviewing your patch
and currently we have no delta on top of the package coming from Debian,
I'd prefer to get it accepted in
Hi Robert,
Sorry if you felt ignored here but it was not the case, we are just
trying to make sure your bug report is actionable.
I did not quite understand your problem considering you mentioned in
Comment #3 it was an issue due to a manual intervention in your mailbox.
Are you talking about a
** Also affects: samba (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827041
Title:
Regression in smbclient, username required for
** Changed in: memcached (Ubuntu)
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/1877623
Title:
ftbfs s390x, riscv
To manage notifications about this bug go to:
Public bug reported:
I recently upgraded from Ubuntu 18.04 to Ubuntu 20.04. Since the
upgrade, Discord is using way more CPU than before when in vocal chat
(>50% now, was <10% before on 18.04). I tried reinstalling it or using
the web version but it's the same.
Output of lsb_release -rd:
Public bug reported:
The chef source package included in Focal actually contains the Cinc
project [1] which is a community fork trying to comply with the Chef
Trademark Policy [2].
A Cinc project member approached Debian to raise a concern about the
Trademark issues regarding the chef package in
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876912
Title:
[SRU] libruby2.7 provides ruby-bundler library but its binary is
missing
To
Version 2.7.0-7 (with the fix for this bug) was already synced from
Debian to Groovy:
https://launchpad.net/ubuntu/+source/ruby2.7/2.7.0-7
** Changed in: ruby2.7 (Ubuntu)
Status: In Progress => Fix Released
** Merge proposal unlinked:
** Changed in: vlan (Ubuntu)
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/1876781
Title:
ifupdown scripts have no execute rights!
To manage notifications about this
** Changed in: dovecot (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876537
Title:
dovecot eating mail indexes /var/dovecot-index/user
To manage
** Merge proposal unlinked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/strongswan/+git/strongswan/+merge/383258
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863749
Title:
[FFe]
Hi Philipp,
Thank you for taking the time to file a bug report.
I was not able to reproduce the issue reported by you using the default
configuration provided by the packages. Could you please provide your
configuration files? They should live in:
- /etc/strongswan.d/
- /etc/swanctl/
-
Hi Philipp,
Thank you for taking the time to file a bug report.
I was not able to reproduce the issue reported by you using the default
configuration provided by the packages. Could you please provide your
configuration files? They should live in:
- /etc/strongswan.d/
- /etc/swanctl/
-
Here is a PPA with the proposed solution for Focal:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/focal-
ruby2.7-lp1876912/+packages
Verifying if the test case mentioned in the description has the expected
behavior:
$ lxc launch ubuntu-daily:focal ruby-does-not-provide-bundler
$ lxc
** Description changed:
+ [ Impact ]
+
+ Users who are used to call 'bundle' are not able to do it installing
+ just libruby2.7. ruby-bundler was marked as provided by libruby2.7 in
+ version 2.7.0-5.
+
+ ruby2.7 binary package provides 'bundle2.7' executable which could be
+ symlinked to
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/ruby2.7/+git/ruby2.7/+merge/383424
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876912
Title:
libruby2.7
** Also affects: ruby2.7 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: ruby2.7 (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: ruby2.7 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: ruby2.7 (Ubuntu
ruby-bundler for now.
This fix should be synced into Groovy and SRUed to Focal.
** Affects: ruby2.7 (Ubuntu)
Importance: High
Assignee: Lucas Kanashiro (lucaskanashiro)
Status: In Progress
** Changed in: ruby2.7 (Ubuntu)
Assignee: (unassigned) => Lucas Kanash
Thank you for taking the time to file a bug report.
Could you please provide more information on how to reproduce this bug?
Like your sssd config and what else you think could help us. If you
upgraded sssd from version 1.16.1-1ubuntu1.4 to 1.16.1-1ubuntu1.5 I do
not see any reason for this
** Changed in: sssd (Ubuntu)
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/1867688
Title:
Vague error message: sss_ssh_authorizedkeys: Error looking up public
keys
1201 - 1300 of 3436 matches
Mail list logo
