For reference: https://salsa.debian.org/sssd-team/sssd/merge_requests/2
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to sssd in Ubuntu.
https://bugs.launchpad.net/bugs/1793882
Title:
sssd: Add DEP8 tests
To manage notifications about thi
Disabling the pinger also works around the problem:
In /etc/squid/squid.conf:
pinger_enable off
** Summary changed:
- squid crashed with SIGABRT in xassert()
+ assertion error when rotating logs
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscrib
Upstream PR got some activity: https://github.com/squid-
cache/squid/pull/257
--
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/1794553
Title:
assertion error when rotating logs
To manage not
@yicwang, did you update the apparmor profile as per this bug for your
tests? The diff can be seen at
https://code.launchpad.net/~ahasenack/ubuntu/+source/strongswan/+git/strongswan/+merge/356135.
Make that change, then run this command:
sudo apparmor_parser -r -T -W /etc/apparmor.d/usr.lib.ipsec
Thanks for filing this bug in Ubuntu.
The mysql user is created by the mysql-server-5.7 package in its preinst
script. The logs you attached unfortunately don't contain the details
about what happened at that time, only that the user wasn't available
when the postinst script came along (the failed
@jnx, the 192.168.11.254 address you are trying to bind to, is that the
normal nic of that machine? Or something else, like a wifi interface, or
something that would only come up after the user logs in, assuming this
is a desktop?
--
You received this bug notification because you are a member of
Taking a look.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1796164
Title:
After interface/IP changes, bind9 can fail to respond to queries on
the new interface
To manage notification
Is MAAS using netplan to add the new interface? I was trying to
reproduce this without MAAS, but it worked just fine. I fear that maybe
netplan is triggering something else that MAAS by itself isn't, and that
made it work.
Here is what I did.
New VM, with just one nick, configured via netplan to
