Thanks for fix!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1529074
Title:
Due to AppArmor profile restrictions Telepathy can't connect when
networkd used instead of
This bug was fixed in the package apparmor - 2.10-0ubuntu10
---
apparmor (2.10-0ubuntu10) xenial; urgency=medium
* debian/patches/lp1529074.patch: for systems using networkd, add read on
/run/systemd/resolve/resolv.conf (LP: #1529074)
-- Jamie Strandboge Tue, 05 Jan 2016 10:
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1529074
Title:
Due to AppArmor profile restric
Rather than adding this to the telepathy profile, it should be added to
the apparmor nameservice abstraction.
** Package changed: telepathy-mission-control-5 (Ubuntu) => apparmor
(Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: Confirmed => In Progress
** Changed in: apparmor (Ubuntu)
** Changed in: telepathy-mission-control-5 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1529074
Title:
Due
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: telepathy-mission-control-5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
cont
Workaround: add line
/run/systemd/resolve/resolv.confr,
to section /usr/lib/telepathy/telepathy-* in file
/etc/apparmor.d/usr.lib.telepathy and then restart AppArmor.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to te
7 matches
Mail list logo