Public bug reported:
Due to a trademark issue [1][2], chef and associated packages were
removed from Debian [3]. I'd like to follow their decision and do the
same in Ubuntu and not maintain those packages by ourselves. The
following packages should be removed:
## src:chef/15.8.25.3.gcf41df6a2-6
sbuild dep8 tests are failing in xenial and bionic in all architectures
even before the postfix update, so this is not a regression introduced
by postfix. I retried all the tests in the hope of this been a flaky
test but they failed again. The architectures not reported by the SRU
bot are hinted
I also tried to reproduce the mentioned failure in a clean Xenial
container with no success. Since this is an old bug and no one replied
to it for years I am removing the server-next tag.
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Sorry for the delay to reply to this bug, the fix should have been
backported to Xenial some years ago but now seems too late for that. If
you really need it, you are better off upgrading to Bionic, or explain
why you really need it in Xenial and we may reconsider.
** Changed in: samba (Ubuntu
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/158
Title:
document manual_cache_clean better
To manage notifications about
Hi Iain,
The bug looks good indeed, thanks for describing all the details.
The next step is to prepare the package to be uploaded to the unapproved
queue. That should be easy, you can get the package in Groovy (version
1.0-3), add a new changelog entry mentioning this is a no change rebuild
for
Thanks for trying to sort this out, appreciated.
I am not familiar with the bzr workflow for doing packaging work, if you
want me to guide you I'd prefer you trying to follow this doc:
https://wiki.ubuntu.com/MOTU/Contributing#Preparing_New_Revisions
The outcome should be a debdiff file that I
Hi Marietto,
This bug is marked as Fix Released, ideally if you are using the latest
updates in Xenial it should work. Could you share with us which version
of the mentioned packages you're using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
With no action from my side (not sure what happened) nomad migrated, so
there is nothing blocking the removal now:
$ reverse-depends -r groovy golang-prometheus-client-dev
No reverse dependencies found
$ reverse-depends -r groovy -b golang-prometheus-client-dev
No reverse dependencies found
--
** Tags removed: 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/1786244
Title:
package linux-image-4.15.0-24-generic (not installed) failed to
install/upgrade: run-parts:
Hey @Thomas, any news about the fix proposed by Christian? Also steps to
reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858763
Title:
assertion failed: store_client.cc:92:
Anyone willing to do the verification work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868127
Title:
[SRU] OpenVPN will not reload due to misconfigured .service file
To manage notifications
** Changed in: smartmontools (Ubuntu Eoan)
Status: New => 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/1874362
Title:
xenial/man8/update-smart-drivedb.8.html incorrect
To manage
)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
** Tags removed: server-next
** Changed in: net-snmp (Ubuntu)
Assignee: (unassigned) => Paulo Flabiano Smorigo (pfsmorigo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: net-snmp (Ubuntu)
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/1886658
Title:
libsnmp-perl depends on wrong p
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
I've seen some people facing issues regarding the packet version
compatibility, you have version 3 and 4 in your setup. I tried to make a
quick research about any compatibility issue between version 3 and 4 but
I did
Thanks for taking the time to report this bug and try to make Ubuntu
better!
I was able to reproduce what you mentioned even in Groovy. Checking the
code, the warning about specifying the port number with --server seems
something desired by upstream since it is not IPv6 friendly [1]. I did
not go
** Changed in: smartmontools (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/1888009
Title:
smartmontools.service: start operation timed out.
** Changed in: mysql-8.0 (Ubuntu Focal)
Status: Incomplete => Invalid
** Changed in: mysql-8.0 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
First of all, thanks for filing this bug and trying to make Ubuntu
better.
As commented in #2 by Eduardo, tomcat8 is an universe package which
means it is community maintained. I am subscribing ~ubuntu-server to
this bug which will add it to the Ubuntu Server team backlog (community
team) and
I prepared a PPA with a package containing the upstream fix linked in
comment #2 by Christian:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/xenial-munin/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
+ The network interface traffic metric plugin reports invalid values for
+ network speed interface (negative values).
+
+ This is the upstream fix for this issue:
+
+ https://github.com/munin-monitoring/munin/commit/78c3c3aa
+
+ [Test Case]
+
+ Install
** Changed in: munin (Ubuntu Xenial)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: munin (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
containerd/1.3.6-0ubuntu1 which fixes the library issue (take a look at
comment #6) migrated to the release pocket.
** Changed in: containerd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
At the moment cadvisor and golang-github-openshift-imagebuilder FTBFS, I
am uploading the attached debdiffs to fix them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
containerd
Thank you for taking the time to file a bug report.
I assume you tried to install 'nginx-full' and not 'nginx' because
'libnginx-mod-http-upstream-fair' is not a dependency of 'nginx' binary
package. With that in mind, I created a brand new Focal container and
tried to install 'nginx-full' and it
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Actually the resolvconf binary is still present in Focal, shipped by
resolvconf binary package. The resolvconf binary package is suggested by
the openvpn binary package. So if you are facing any failure because of
I forgot to mention this LP bug in the changelog but the vendor code in
the golang-github-containerd-containerd-dev package was removed. It
would never work with vendor code anyway. The fix is in version
1.3.6-0ubuntu1.
The side effect is that now packages which depends on the containerd
library
** Attachment added: "golang-github-openshift-imagebuilder-debdiff"
https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1884663/+attachment/5392921/+files/golang-github-openshift-imagebuilder-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
containerd library package is not working with vendorized deps
To manage notifications about this bug go to:
nomad FTBFS was fixed and now it is blocked by golang-github-prometheus-
client-golang. Excuses page says golang-github-prometheus-client-golang
is missing builds on arm64, armhf, ppc64el and s390x, but from my
understanding this is happening because the package changed to arch:all.
** Changed
Thank you for taking the time to file a bug report.
Checking the logs I noticed the mysqld failed to start:
ERROR: Unable to start MySQL server:
/var/lib/dpkg/info/mysql-server-5.7.postinst: línea 102: mysqld: orden no
encontrada
Please take a look at https://wiki.debian.org/Teams/MySQL/FAQ for
Thank you for taking the time to file a bug report.
Could you please provide more information about your setup? Could you
share your anonymized config file? Without more information I am not
able to reproduce the bug to act on it.
Since there is not enough information in your report to begin
I launched a VM locally and I also was not able to find what you
mentioned. Not sure what might have happened to make you get to this
state.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887016
hi, i got a similar problem when run "sudo lshw -c memory"
here the output:
root@l4cus:/home/l4cus# lshw -c memory
*-memory
descripción: Memoria de sistema
id físico: 40
ranura: Placa de sistema o placa base
tamaño: 8GiB
*-bank:0
descripción: DIMM DDR3
** Description changed:
[Impact]
"postfix tls deploy-server-cert" did not handle a missing optional
argument which makes users get a "can't shift that many..." error.
- In this SRU we are proposing a microrelease update in Focal from version
- 3.4.10 to 3.4.13 since the changes are
** Changed in: postfix (Ubuntu Xenial)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: postfix (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: postfix (Ubuntu Xenial)
Status: Triaged => In Progress
*
In this case, I believe that the screenpad upgrade tool is needed. I
only have Pop!Os 20.04, and no Windows available. It might be were the
issue is coming from
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Had Found this because [https://github.com/federico-terzi/espanso/] severely
froze my desktop when expanding text snippets.
Disabling Scroll lock did solve it.
Using Pop!_OS 20.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
FYI uploaded:
$ dput ubuntu ruby-ncurses_1.4.9-1build3ubuntu0.18.04.1_source.changes
Checking signature on .changes
gpg:
/home/kanashiro/packaging/ubuntu/ruby-ncurses/ruby-ncurses_1.4.9-1build3ubuntu0.18.04.1_source.changes:
Valid signature from F823A2729883C97C
Checking signature on .dsc
gpg:
First, you'd not need to bump the version to
1.4.9-1build3ubuntu0.18.04.2, we have not uploaded
1.4.9-1build3ubuntu0.18.04.1 yet. And the SRU bug template is good IMO,
good job!
Answering your questions:
* I marked this bug as affecting bionic only, I am not sure if some
special permission is
** Also affects: tpp (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ruby-ncurses (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: tpp (Ubuntu Bionic)
Status: New => Invalid
** Changed in: ruby-ncurses (Ubuntu)
Status: In
Your patch looks much better now, thanks Iain! I made some small changes
in your changelog and uploaded it to a PPA [1] for testing purposes:
* Changed the target to bionic instead of UNRELEASED
* Added "~ppa1" to the string version. With that if someone decides to install
the package from the
Thanks for the patch and the steps to reproduce the bug Iain! I played
with it and it indeed fixes the package and now I can "require
'ncurses'" in Bionic.
To get it ready for the SRU we need to fix a couple of things in your
patch:
* The version string. You used 1.4.9-1ubuntu1 but this version
** Changed in: postfix (Ubuntu Eoan)
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/1881196
Title:
[SRU] postfix tls deploy-server-cert fails with "can't shift
golang-github-armon-go-metrics got fixed and made its way into the
release pocket, now there is no runtime dep blocking this removal.
$ reverse-depends -r groovy golang-prometheus-client-dev
$ reverse-depends -r groovy -b golang-prometheus-client-dev
Reverse-Build-Depends
* nomad
--
You
Thank you for taking the time to file a bug report.
>From your logs I can see these errors:
2020-07-04T12:58:32.542859Z 2 [ERROR] [MY-010767] [Server] Error in fixing SE
data for family_tree.user
2020-07-04T12:58:32.560061Z 2 [ERROR] [MY-012083] [InnoDB] Table
family_tree/family_tree is not
Updated list of rdeps:
$ reverse-depends -r groovy golang-prometheus-client-dev
Reverse-Depends
* golang-github-armon-go-metrics-dev
Packages without architectures listed are reverse-dependencies in:
amd64, arm64, armhf, i386, ppc64el, s390x
$ reverse-depends -r groovy -b
** Summary changed:
- cadvisor/0.35.0+ds1-4 FTBFS in Groovy
+ containerd library package is not working with vendorized deps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
containerd
cadvisor is uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
cadvisor/0.35.0+ds1-4 FTBFS in Groovy
To manage notifications about this bug go to:
mwhudson gave a +1 for this cadvisor debdiff as a workaround for now:
" kanashiro: yes, that debdiff is fine for now"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
Public bug reported:
In version 2.20.4, pristine-tar was added to Recommends because it is an
optional dependency of origtargz. Since pristine-tar is not in main it
caused a component-mismatch. Downgrade its dependency relation to
Suggests should fix the issue.
** Affects: devscripts (Ubuntu)
Public bug reported:
ruby-webmock/3.8.3-1 is blocked in groovy-proposed because some tests
rely on http://0.0.0.0 and the proxy used in autopkgtest environment is
not allowing it. The easy way to fix it is adding '0.0.0.0' to the
'no_proxy' environment variable used by autopkgtest.
** Affects:
Salsa MR updating the Debian patch:
https://salsa.debian.org/debian/puppet-beaker/-/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885614
Title:
Version 4.21.0-2 is blocking
Also submitted a PR:
https://github.com/puppetlabs/beaker/pull/1661
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885614
Title:
Version 4.21.0-2 is blocking ruby-net-scp/3.0.0-1 migration
To
Public bug reported:
puppet-beaker/4.21.0-2 is blocking ruby-net-scp/3.0.0-1 migration
because it has a tight version constraints regarding dependency on net-
scp (and also net-ssh 6.x which is already in the Groovy release
pocket).
Upstream already patched its gemspec file to be compatible with
Public bug reported:
puppetdb/6.2.0-4 is stuck in groovy-proposed for 64 days and in Debian
unstable for 347 days. Version 6.2.0-3 was removed from Debian testing
because it did not migrate to testing for too long [1]. After gathering
all these information seems that the Debian maintainer is not
This issue was fixed in Debian on version
1:0.0~git20200410.79a7a31+ds-2. It was already sync'ed and it migrated
to the release pocket as you can see here:
https://launchpad.net/ubuntu/+source/golang-golang-x-tools
** Changed in: golang-golang-x-tools (Ubuntu)
Status: New => Fix Released
** Tags removed: 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/1820288
Title:
Tomcat Web Application Manager does not copy context configuration
To manage notifications about this bug
** 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/1868955
Title:
[SRU] after
Thanks for all the debugging Christian! Very useful :)
I also did some investigation and this behavior is expected by the
Debian maintainers. According to the maintainers the current
implementation does not support using copyXML=true, because in this case
when the app is deployed the context file
This bug was already fixed in Xenial on version 8.0.32-1ubuntu1.9:
tomcat8 (8.0.32-1ubuntu1.9) xenial; urgency=medium
* d/p/fix-class-resource-name-filtering.patch: Fix class and resource name
filtering in WebappClassLoader (LP: #1606331).
-- Karl Stenerud Mon, 10 Dec 2018
15:08:07
Hi Nick and Jan (and anyone affected by this bug),
Could you please try out version 3.4.13-0ubuntu1 in focal-proposed? And
tell us if it's properly fixed for the sake of the SRU process? If it is
the case please remove verification-needed and verification-needed-focal
tags from this bug and add
** Tags removed: 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/1845845
Title:
follow gnome-terminal libexec migration
To manage notifications about this bug go to:
Thank you Luis! The MP I submitted with those changes was also reviewed
and accepted, I am uploading the package now and let's wait for the SRU
team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for the delay, and also thanks for the feedback you provided!
I talked to the Debian maintainer and the warnings you mention were
tackled and the upstream PR was updated accordingly:
https://github.com/hashicorp/vagrant/pull/11459
I applied the new changes locally and I was able to run
Above is attached a cadvisor debdiff, I forgot to mention it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
cadvisor/0.35.0+ds1-4 FTBFS in Groovy
To manage notifications about this
The attached debdiff contains a workaround for this issue, it disables
the containerd support. With this new version the package builds fine
and autopkgtest passes.
** Attachment added: "debdiff"
Unfortunately we cannot guide you through a fix nor a workaround because
we are not able to reproduce the bug. If by any mean you provide a core
dump as Sergio mentioned (or better: a step by step on how to reproduce
it) you can come back to this bug and we will be happy to investigate
this crash.
Thank you for taking the time to file a bug report.
Checking the logs I noticed there is a bad configuration option:
/etc/ssh/sshd_config: line 111: Bad configuration option: sudo
Could you please share what you have changed in your sshd_config file? I
set up a brand new Xenial conatainer with
Public bug reported:
Currently, version 0.35.0+ds1-4 FTBFS in Groovy because of a bug in the
`golang-github-containerd-containerd-dev` package. The containerd
library package provides all the dependencies vendorized and there is a
namespace issue. I started a discussion here to figure out the
Public bug reported:
Version 0.1.3-2 is blocked in proposed because of a test failure on
armhf:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/armhf/g/golang-
procfs/20200622_123558_68ee3@/log.gz
A patch was submitted
** Summary changed:
- postfix tls deploy-server-cert fails with "can't shift that many"
+ [SRU] postfix tls deploy-server-cert fails with "can't shift that many"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
+ "postfix tls deploy-server-cert" did not handle a missing optional
+ argument which makes users get a "can't shift that many..." error.
+
+ In this SRU we are proposing a microrelease update in Focal from version
+ 3.4.10 to 3.4.13 since the changes are
** 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
Updated list of rdeps at the moment:
$ reverse-depends -r groovy golang-prometheus-client-dev
Reverse-Depends
* golang-github-armon-go-metrics-dev
* golang-github-google-cadvisor-dev
* golang-github-influxdb-influxdb-dev
Packages without architectures listed are reverse-dependencies in: amd64,
** Changed in: postfix (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** 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.
Please do not consider version 3.4.11-0ubuntu1. I am preparing a SRU to
include version 3.4.13 which also fixes LP #1881196.
--
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
FYI the SRU exception for Postfix is documented here:
https://wiki.ubuntu.com/StableReleaseUpdates#Postfix
--
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
Awesome, thank you for that. Since it was already approved there is no
reason to go through the whole process again, but to keep it documented
I'll create a wiki page for this Postfix exception and link it here:
https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases
After
Scott, I asked around about this subject and those past SRUs with micro-
release updates were accepted probably based on this:
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
And since Debian is also including those micro-releases in stable point
releases I also think we
Thanks for the pointer Scott, appreciated. And also for fixing it in
Debian and consequently in Groovy which is a sync.
I see this fix in version 3.4.13. Hopefully this postfix SRU [1] will be
accepted and we will have version 3.4.11 in Focal, so we have two patch
level releases to consider if
Public bug reported:
Hi,
the socat version in Focal (1.7.3.3) breaks certain applications (i.e.
qemu serial console), when using raw mode or disabling echo (required
for serial consoles). Example: start socket in listening mode: "qemu-
system-x86_64 -serial unix:/tmp/socket,server", connect with
** Also affects: containerd (Ubuntu Bionic)
Importance: Undecided
Status: New
** No longer affects: containerd (Ubuntu Focal)
** Also affects: containerd (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: containerd (Ubuntu Focal)
--
You received this
** Also affects: containerd (Ubuntu Focal)
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/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker
** 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
** Summary changed:
- [SRU] after upgrade to 20.04: posttls cannot connect to private/tlsmgr
+ [SRU] after upgrade to 20.04: dane support is not working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
1101 - 1200 of 3423 matches
Mail list logo
