** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
** Changed in: haproxy (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848902
** Changed in: strongswan (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1772705
Title:
IKEv2 VPN connections fail to use DNS servers
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1723350
Title:
sssd offline on boot, stays offline forever
To manage notifications about this bug go to:
Good to know. I also couldn't reproduce it just by using those commands,
some more setting up is probably needed. If we get reproducible steps,
we might be able to identify the commit (or series of commits) that
fixed it after 1.1.14. I took a quick look at the ChangeLog file but
failed to spot
For reference:
https://wiki.ubuntu.com/DebuggingInstallationIssues#triggers_ci_file_contains_unknown_directive_syntax
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1851302
Title:
Error
*** This bug is a duplicate of bug 1851302 ***
https://bugs.launchpad.net/bugs/1851302
** This bug has been marked a duplicate of bug 1851302
Error in update
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
Thanks for filing this bug in ubuntu.
You seem to have a corrupted trigger file. What's the contents of
/var/lib/dpkg/info/samba-libs.triggers? It might have a slightly
different name, like have an architecture as part of the name.
** Changed in: samba (Ubuntu)
Status: New => Incomplete
Bug still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/810736
Title:
logrotate script needs to notify all samba processes when logs are
rotated
To manage notifications
This bug is still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1670450
Title:
samba4 bind dlz module stops working on rndc reload
To manage notifications about this bug go
Thanks for filing this bug in Ubuntu.
Do you mean that in your current disco system, dist-upgrade does not
install all available updates? Or is this error something you only get
when running do-release-upgrade?
Could you please also attach the release upgrader logs from /var/log
/dist-upgrade?
Thanks for filing this bug in Ubuntu.
The package you were upgrading from, 7.70-2, was apparently never
published in Ubuntu, according to the list here:
https://launchpad.net/ubuntu/+source/nmap/+publishinghistory
Was that a local build perhaps?
** Changed in: nmap (Ubuntu)
Status: New
Thanks for filing this bug in Ubuntu.
It's not clear why the postfix postinst script failed. I suggest you
look in /var/log/mail.log and /var/log/mail.err to see if there is more
helpful information there.
Since there is not enough information in this bug report to diagnose the
problem, I'll
I personally think what we have is good enough. If someone thinks
otherwise, please file a merge request in https://salsa.debian.org/php-
team/php-defaults
** Changed in: php7.2 (Ubuntu)
Status: Triaged => Opinion
** Changed in: php7.3 (Ubuntu)
Status: Triaged => Opinion
--
You
I agree. Do you have a way to reproduce this somewhat reliably?
** Changed in: sssd (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1723350
Salsa MR: https://salsa.debian.org/postfix-team/postfix-
dev/merge_requests/3
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1845334
Title:
Update DEP8 test to python3
To manage
I have a pass with python3 for 3.4.7-1 in debian/sid. Let me clean that
branch up now and make a MR in salsa.
** Attachment added: "log"
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+attachment/5302040/+files/log
--
You received this bug notification because you are a
Looking at this now.
** Changed in: postfix (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1845334
Title:
Update DEP8 test to python3
To
I'm satisfied with the results, also considering test (5) done in the
other bug. Just to be sure, I also tried it via dist-upgrade. That is a
bit more hacky, as it involves changing s/precise/trusty/ in
sources.list snippets, ignoring gpg errors (as precise doesn't have the
gpg key for trusty-esm)
Test 4:
>From a fresh trusty instance, which has uat installed (from updates):
a) enable esm (via ubuntu-advantage enable-esm), upgrade to proposed
b) upgrade to proposed, enable esm (via ua attach)
Result: PASS
Details:
In the end, both instances have the same proposed package:
$ lxc exec
Test 3:
>From a fresh trusty system, no uat installed, no ubuntu-minimal installed
a) install uat from updates, enable esm, upgrade to proposed
b) install uat from proposed, enable esm (via ua attach)
Result: PASS
Details:
At the end, confirmed that both chroots have esm enabled and with a
Test 2:
a) fresh install from t-updates, go to t-proposed
b) fresh install from t-proposed directly
Result: PASS
Details:
At the end, we have two chroots: /tank/trusty-2a and /tank/trusty-2b
# chroot /tank/trusty-2a apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Installed:
addendum for test 2:
# diff -uNr /tank/trusty-2{a,b}/ 2>/dev/null|diffstat
root/.bash_history |2
var/cache/apt/archives/ubuntu-advantage-tools_10ubuntu0.14.04.4_all.deb |binary
var/cache/apt/pkgcache.bin
Test 1: basic attach w/ proposed
Result: PASS
Details:
$ lxc launch ubuntu-daily:trusty t1
Creating t1
Starting t1
# enable proposed, update, check
$ lxc exec t1 apt-get update
$ lxc exec t1 apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Repeating tests 1-4 here.
Test number 5, which failed in the previous verification, can be seen
done in bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/+bug/1850672. It was done with do-release-upgade, which is how I
expect users would upgrade from precise, and I took care
Trusty verification, in two parts:
a) following the [testing] section, i.e., upgrading from precise, to trusty,
then to trusty-updates
b) almost the same setup, but upgrading from precise to trusty with the u-a-t
proposed package, without going through the intermediary current u-a-t from
trusty verification succeeded
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1850672
The package https://launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/19.6~ubuntu14.04.3 built just fine, confirming the fix.
trusty verification succeeded.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you
b) almost the same setup, but upgrading from precise to trusty with the
u-a-t proposed package, without going through the intermediary current
u-a-t from trusty-updates.
$ lxc launch ubuntu-daily:precise p1
$ lxc exec p1 ubuntu-advantage enable-esm $u:$p
Running apt-get update...
Ubuntu ESM
a) upgrading from precise, to trusty, then to trusty-updates
$ lxc launch ubuntu-daily:precise p1
Creating p1
Starting p1
$ lxc exec p1 ubuntu-advantage enable-esm $u:$p
Running apt-get update...
Ubuntu ESM repository enabled.
# esm enabled, positive pinning:
$ lxc exec p1 apt-cache policy|grep
Please remember that in order for this update to be released, the tags
need to be updated, as explained in comment #16.
Thanks for testing!
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Changed in: bind9 (Ubuntu)
Status: New => Triaged
** Changed in: bind9 (Ubuntu)
Importance: Undecided => High
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubun
** Description changed:
[Impact]
When enabling ESM on precise, then upgrading that to current trusty, and from
there to the proposed new trusty client (see #1832757), ESM gets disabled.
This was found when executing test case (5) in the original SRU bug
#1832757.
The reason is
** Description changed:
[Impact]
When enabling ESM on precise, then upgrading that to current trusty, and from
there to the proposed new trusty client (see #1832757), ESM gets disabled.
This was found when executing test case (5) in the original SRU bug
#1832757.
The reason is
** Description changed:
[Impact]
When enabling ESM on precise, then upgrading that to current trusty, and from
there to the proposed new trusty client (see #1832757), ESM gets disabled.
This was found when executing test case (5) in the original SRU bug
#1832757.
The reason is
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test
hanged in: ubuntu-advantage-tools (Ubuntu Trusty)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: In Progress => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: High => Low
** Changed in: ubuntu-
d to check for the version.
** Affects: ubuntu-advantage-script
Importance: Unknown
Status: Unknown
** Affects: ubuntu-advantage-tools (Ubuntu)
Importance: High
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Changed in: ubuntu-advantage-tools (Ubuntu)
S
An 19.6~ubuntu14.04.3 upload with the fix will be done shortly.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1832757
Title:
Update ubuntu-advantage-client
To manage
Test (5a) failed. The scenario is an upgrade from precise with esm
enabled to trusty, and then to trusty-proposed. What happened is that
after installing the trusty proposed package in this sequence, ESM
became disabled.
Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage-
I'll resume distro packaging work starting tomorrow, thanks for the
ping.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1845334
Title:
Update DEP8 test to python3
To manage
trusty verification, test case (4)
Both scenarios, (a) and (b), start from trusty with u-a-t already
installed from updates
Test (a): enable esm -> upgrade to proposed
Test (b): upgrade to proposed -> ua attach (which enables esm)
The u-a-t package from updates that was used is:
trusty verification, test case (3)
Both start from fresh trusty minimal with no u-a-t installed
a) u-a-t updates -> enable esm -> upgrade proposed
b) u-a-t proposed -> attach
The u-a-t package from updates that was used is: 10ubuntu0.14.04.4
The u-a-t package from proposed that was used is:
i.e. upgradable to the same version
(...)
out 09 11:36:04andreas: this is a display bug in apt list,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753297
out 09 11:36:33Caused by weird behavior in the old pinning
implementation, the fix for that is more like a workaround
out 09 11
Have you used apt 1.0.1ubuntu2.24 ? It should have the fix for the bug
that was filed during the conversation above, which I'm assuming is the
same as this one.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in
grow a dependency on the universe package, but it's
still not allowed for trusty.
** Affects: ubuntu-advantage-tools (Ubuntu)
Importance: Critical
Assignee: Andreas Hasenack (ahasenack)
Status: Fix Released
** Affects: ubuntu-advantage-tools (Ubuntu Trusty)
Importance
Thanks for reporting that here:
https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1847716
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1798786
Title:
can't retrieve gmail emails.
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
Status: In Progress => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server,
Public bug reported:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {}
The python-azure test failed in bileto in the same way, so it can be
used to further troubleshoot this issue. My first attempt would be to
unset the http_proxy variable, or set it to localhost so connections
fail, and see what happens.
--
You received this bug notification because you are a
Given the tests pass locally in a container (autopkgtest ... -- lxd
ubuntu-daily;eoan), I'm trying a bileto run
(https://bileto.ubuntu.com/#/ticket/3818) to see if that reproduces the
test failure. If yes, then I can use that platform for troubleshooting.
--
You received this bug notification
comment #4 suggested that the panic only happened because
kernel.softlockup_panic was set to 1, was that verified?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1846237
Title:
Kernel
This isn't "just" a bug, it's a roadmap item in my view, as many
products are affected. It needs a spec, like in the fedora case. I agree
that it would be awesome to have this.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
/
/media/andreas/dataext4/
/testdata was populated with a copy of all files in /usr/bin that start
with "b*". I don't think the --exclusion parameters you used play a
factor here.
Can you please verify the target filesystem in your test case, and if
rsync reported errors? And there
** Changed in: asterisk (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1845765
Title:
asterisk-modules package built without amr_codec.so
To
Adding a task for python-cryptography so this bug shows up in the
excuses page, even though it's not a bug in python-cryptography itself.
** Also affects: python-cryptography (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
In bionic, that codec was added by a debian patch:
debian/patches/amr.patch
Description: Add AMR and AMR-WB codec modules supporting transcoding
That patch is present in disco and eoan, but neither have the
codec_arm.so file shipped, nor is codec_amr.c mentioned in their
respective build logs.
What's the filesystem on the target? If the target is vfat, for example,
setting ownership and permissions won't work, and -W tells rsync to
transfer the whole file.
** Changed in: rsync (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
@cosmos-door, thanks for that merge request against upstream. We are
just a few days away from Final Freeze, though. Would you perhaps be
able to make a merge proposal against the packaging, with a quilt patch?
That would be the ubuntu/devel branch, if you clone the repository
according to the
, for comparison:
andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G
Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960
cluster_size=65536 lazy_refcounts=off refcount_bits=16
real0m0,016s
user0m0,010s
sys 0m0,006s
andreas@nsn7:~$ qemu-img info
** Changed in: haproxy (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1828496
Title:
service haproxy reload sometimes fails to pick up new TLS
So, on the GA iso, one cannot get to the step where the installer is
updated. Do you get at least to the language selection prompt, i.e.,
does the installer at least stop somewhere asking you a question? You
say:
"4. We get a continuous flash at early install stage."
I ask because if you are
This may be tricky to reproduce reliably on a test machine, unless you
own a system where it is already happening.
In the upstream bug at
https://github.com/libstatgrab/libstatgrab/issues/102, there is a hint
that
** Bug watch added: Debian Bug tracker #941202
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941202
** Also affects: apache2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941202
Importance: Unknown
Status: Unknown
--
You received this bug notification
Public bug reported:
d/t/test-squid.py should be updated to python3
** Affects: squid (Ubuntu)
Importance: Low
Status: Triaged
** Tags: dep8
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to squid in Ubuntu.
According to git log, https://git.launchpad.net/qa-regression-
testing/tree/scripts/test-squid.py already got some changes to work with
py3.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
/scripts/test-postfix.py
** Affects: postfix (Ubuntu)
Importance: Undecided
Assignee: Andreas Hasenack (ahasenack)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net
By blocking the ruby2.5 migration this also affects ruby2.5 (for
tracking)
** Also affects: ruby2.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ruby2.5 in Ubuntu.
I mean the crash is not frequent enough.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810827
Title:
There is a fix available, but is not frequent enough and there is a
simple workaround: restart instead of reload. Also only that specific
"force group" config change is affected.
** Tags removed: server-next
** Also affects: samba (Ubuntu Bionic)
Importance: Undecided
Status: New
**
** Changed in: nagios-plugins (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1516451
Title:
Bryce, I think this can perhaps be proposed and uploaded, given the
previous comments. For the actual [test] section of the sru, perhaps
point at the comments above.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
It's part of our delta. If you clone bind9, you'll see the commit disabling it:
commit 27364096b130d52beef7aaacfa5c824e3968a66d
Author: Andreas Hasenack
Date: Fri Jul 27 14:16:35 2018 -0300
- Don't build dnstap as it depends on universe packages:
+ d/control: drop build
hm, I'm sorry, I may be mixing things up. The lmdb commit is another one:
commit 4f9a9b60845feb1202020ec71bd6a9e7298e6e19
Author: Andreas Hasenack
Date: Wed Jun 20 17:28:42 2018 -0300
- Build without lmdb support as that package is in Universe
I don't remember now if lmdb was related
Maybe you figured this out by now, but to use dnstap we need to MIR
lmdb.
And I just saw that the lmdb mir was accepted and it's in main in eoan:
https://bugs.launchpad.net/ubuntu/+source/lmdb/+bug/1833745
So were we not in feature freeze, we could enable this...
--
You received this bug
Public bug reported:
Saw this debian bug which also affects ubuntu:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939522
I did a release upgrade from disco to eoan, and even though it didn't fail the
upgrade, the problem is there:
Preparing to unpack
Still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810827
Title:
/usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon
*** This bug is a duplicate of bug 1843036 ***
https://bugs.launchpad.net/bugs/1843036
I think this is a duplicate of bug #1843036, which is tracking a
regression in net-snmp introduced by the previous update. Could you
please follow that bug instead? There are packages available for testing
In progress branch:
https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+ref
/eoan-squid-ftbfs-glibc-230
With accompanying ppa:
https://launchpad.net/~ahasenack/+archive/ubuntu/squid-ftbfs-glibc-230
I'm waiting a bit to hear from upstream before uploading that to ubuntu.
--
5.7.3+dfsg-1ubuntu4.3 has this changelog entry:
net-snmp (5.7.3+dfsg-1ubuntu4.3) xenial; urgency=medium
* Skip autofs entries when calling statfs to prevent autofs being mounted on
snmpd startup (LP: #1835818):
- d/p/autofs-skip-autofs-entries.patch
-
I filed https://bugzilla.mindrot.org/show_bug.cgi?id=3069 upstream
** Bug watch added: OpenSSH Portable Bugzilla #3069
https://bugzilla.mindrot.org/show_bug.cgi?id=3069
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=3069
Importance: Unknown
Status:
** Changed in: squid (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: squid (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to squid in Ubuntu.
Public bug reported:
>From the announcement at
>https://savannah.gnu.org/forum/forum.php?forum_id=9515:
"""
The Linux-specific header and the sysctl function have been
deprecated and will be removed from a future version of glibc.
Application should directly access /proc instead. For
For what is worth, your log shows the /usr/local path for the samba
binaries. This indicates that this is not an ubuntu package, but likely
an installation from source or some other method.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to
ix being in 3.5:
"""
etc. Fixed in Postfix 3.5. You cn delete the offending lines.
"""
I believe I located it in a hunk in this commit:
https://github.com/vdukhovni/postfix/commit/3274c3cea9d739f86e84b65664aabb692e37e83f#diff-777bfb681a1cd539ddc8e1e606959ffa
** Affects: postf
Hello,
I appreciate that you are having similar problems with winbind, but
let's please use a new bug for that. This one here had a clear error in
the configuration file.
Steven, I would appreciate a new bug with details of your case, in
particular, the config file and the ordering of events
Bryce, is this something we could do for eoan's new php 7.3?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1834963
Title:
apache dependency should be documented in package description
To
** Changed in: ruby2.3 (Ubuntu)
Status: New => Triaged
** Changed in: ruby2.3 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ruby2.3 in Ubuntu.
https://bugs.launchpad.net/bugs/1842316
This can be enabled in firefox 68+ by going to "about:config" and
setting security.tls.enable_post_handshake_auth to true. It's disabled
by default (from upstream), not sure why.
** Changed in: apache2 (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because
A PR which might address this was posted to the sssd mailing list:
https://github.com/SSSD/sssd/pull/864
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1723350
Title:
sssd offline on boot,
Public bug reported:
While doing the SRU verification for bug #1834072, two DEP8 failures
came up that we believe can be fixed:
a) test/io/console/test_io_console.rb
Apply patch from ruby2.5:
https://github.com/ruby/ruby/commit/ac40fc997b6b27c4f61084d9f6fae83ea251d614
b)
at this time.
** Affects: soupsieve (Ubuntu)
Importance: Undecided
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to soupsieve in Ubuntu.
https://bugs.launchpad.net/bugs
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to unbound in Ubuntu.
https://bugs.launchpad.net/bugs/1841364
Title:
AppArmor breaks the default Unbound installation in a live session
To manage
Thanks, looks like clamav has bzip2 vendored in, in
libclamav/nsis/bzlib.c (or at least bits of bzip2), and was missed in
the CVE 2019-12900 bzip2 fix (https://people.canonical.com/~ubuntu-
security/cve/2019/CVE-2019-12900.html)
I flagged the bug as public security, and contacted the security
eoan has 0.101.4+dfsg-1ubuntu1 and has the fix.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1841281
Title:
ClamAV needs updated to reflect security fixes
To manage notifications
This is now in eoan.
** Changed in: nmap (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nmap in Ubuntu.
https://bugs.launchpad.net/bugs/1840152
Title:
Upgrade Nmap package from 7.70 to
** Summary changed:
- defragfs.ocfs2 hangs (or takes too long) on arm64
+ defragfs.ocfs2 hangs (or takes too long) on arm64, ppc64el
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ocfs2-tools in Ubuntu.
** Bug watch added: github.com/markfasheh/ocfs2-tools/issues #42
https://github.com/markfasheh/ocfs2-tools/issues/42
** Also affects: ocfs2-tools via
https://github.com/markfasheh/ocfs2-tools/issues/42
Importance: Unknown
Status: Unknown
--
You received this bug notification
Public bug reported:
The new defragfs.ocfs2 test added in the 1.8.6-1 version of the package
hangs (or takes too long) in our dep8 infrastructure.
I reproduced this on an arm64 VM. The command stays silent, and
consuming 99% of CPU. There is no I/O being done (checked with iostat
and iotop).
Thanks for getting back to us!
I'll mark the ticket as invalid, since it looks like it was just a local
configuration error. If you later determine you reached this state due
to a bug, please feel free to comment here.
** Changed in: krb5 (Ubuntu)
Status: New => Invalid
--
You received
401 - 500 of 4057 matches
Mail list logo
