This issue was fixed in Ubuntu 16.04 LTS in apparmor 2.10.95-0ubuntu2.2
(by way of 2.10.95-0ubuntu2.1, which was superceded in xenial-proposed).
Marking that task closed.
** Changed in: apparmor (Ubuntu Xenial)
Status: In Progress => Fix Released
--
You received this bug notification
Fixed in AppArmor 2.11
** Changed in: apparmor
Status: Fix Committed => Fix Released
--
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/1604872
Title:
Apps can't
That apparmor="STATUS" message simply means that the /usr/lib/lightdm
/lightdm-guest-session AppArmor profile was loaded. Nothing to worry
about there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
@Tyler
apparmor logs seems good; like that example:
audit: type=1400 audit(1470130477.689:35): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/lib/lightdm
/lightdm-guest-session" pid=20307 comm="apparmor_parser"
--
You received this bug notification because you
I've thoroughly tested apparmor 2.10.95-0ubuntu2.2 in xenial-proposed.
I've verified that this bug is fixed (via the Test Case in the
description) and I've also went through the AppArmor Test Plan
(excluding the Ubuntu Touch specific tests):
My apologies once again. Comment 13 was accurate. I got confused by some
of the recent comments and thought I was looking at the wrong bug
report.
I don't think that dino99's issues are related to the original AppArmor
denials mentioned in the bug description and the presence of the
Bah! My apologies for comment 13. I accidentally left that comment in
the wrong bug report.
--
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/1604872
Title:
Apps can't
@Martin
this is logged once with each cold boot only.
I suppose the "too long time loading X" seen after lightdm password validation,
could be related with this logged message.
I have browsed the net about that issue, and many distros are affected, or have
been affected.
Most comments are
#11 adds:
this is with a gnome-shell session on yakkety 64 bits, with gnome3-staging ppa
packages.
--
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/1604872
Title:
Apps
@dino99: How exactly do you reproduce this? I. e. with which program
gets the violation? Calling dbus-update-activation-environment in
general certainly works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
Should be nice to test with the newer dbus version from Debian Unstable too
http://metadata.ftp-master.debian.org/changelogs//main/d/dbus/dbus_1.10.8-1_changelog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
Still get the error on yakkety with the latest apparmor 2.10.95-4ubuntu2
dbus-update-activation-environment: error: unable to connect to D-Bus:
Failed to connect to socket /tmp/dbus-S7lUkEeXo9: Connection refused
--
You received this bug notification because you are a member of Ubuntu
Touch
Even with the fix GTK apps under Xmir are hung trying to connect to the
wrong dbus address. Moved that to bug 1604704.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Description changed:
[Impact]
- Using yakkety with systemd user session makes telepathy unhappy because
- access to /run/user//bus is denied
+ Systemd user sessions makes telepathy unhappy because access to
+ /run/user//bus is denied
[Test Case]
In yakkety:
- sudo apt
** Description changed:
+ [Impact]
+
Using yakkety with systemd user session makes telepathy unhappy because
access to /run/user//bus is denied
+
+ [Test Case]
+
+ In yakkety:
+
+ sudo apt install dbus-user-session empathy
+
+ Restart the session (or reboot), start empathy. It fails
This bug was fixed in the package apparmor - 2.10.95-4ubuntu2
---
apparmor (2.10.95-4ubuntu2) yakkety; urgency=medium
* Drop the following change now that click-apparmor has been updated:
- Continue installing aa-exec into /usr/sbin/ for now since
click-apparmor's
** Branch linked: lp:~apparmor-dev/apparmor/apparmor-ubuntu-citrain
--
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/1604872
Title:
Apps can't connect to the user's
I'll include this in my apparmor upload tomorrow.
** Changed in: apparmor (Ubuntu)
Assignee: Martin Pitt (pitti) => Tyler Hicks (tyhicks)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3492
** Changed in: apparmor
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Branch linked: lp:apparmor
--
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/1604872
Title:
Apps can't connect to the user's session bus, even though it exists
Status
This is very simple to reproduce: In yakkety:
sudo apt install dbus-user-session empathy
Restart the session (or reboot), start empathy. It fails with "Error
contacting the account manager", and dmesg shows several
[ 63.960358] audit: type=1400 audit(1469458539.595:27):
apparmor="DENIED"
Can you paste in the denial for this issue (logged to /var/log/syslog)?
--
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/1604872
Title:
Apps can't connect to the user's
** Summary changed:
- dbus abstraction not compatible with dbus-user-session
+ Apps can't connect to the user's session bus, even though it exists
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch
23 matches
Mail list logo
