Apparmor 2.9.0 has been released; closing.
** Changed in: ac100
Status: New => Fix Released
** Changed in: apparmor
Status: Fix Committed => Fix Released
** Changed in: network-manager (Ubuntu)
Status: Invalid => Fix Released
** Changed in: network-manager (Ubuntu Saucy)
** Changed in: apparmor
Milestone: None => 2.9.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salamander
To manage notifications about this bug go to:
Hi min-soo-cho - this fix has not yet been released in the upstream
apparmor project so I'm changing this back to 'fix committed'
** Changed in: apparmor
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salamander
To manage notifications about
This bug was fixed in the package apparmor - 2.8.0-0ubuntu31.1
---
apparmor (2.8.0-0ubuntu31.1) saucy-proposed; urgency=low
* 0078-parser-check-for-dbus-kernel-support.patch: The parser should not
include D-Bus rules in the binary policy that it loads into the kernel if
the
I've verified that the test added to QRT's test-apparmor.py succeeds
under Ubuntu Saucy kernel 3.11.0-13.20-generic, using the
2.8.0-0ubuntu31.1 package from -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Tested apparmor_2.8.0-0ubuntu31.1-ubuntu, works!
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salamander
To manage notifications about this bug go
verification done, Tag updated.
version tested: apparmor_2.8.0-0ubuntu31.1-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salamander
To manage notific
Ciao Stéphane,
precisely today I decided to test if the fix solves my issue on Saucy. :)
Because Ac100 can access to network only by wifi, I had to download all
debs on a usb stick and install offline.
After install apparmor wifi is working, tested from LXDE and with
network-manager , THANK YOU!
** Branch linked: lp:ubuntu/saucy-proposed/apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salamander
To manage notifications about this bug go to:
h
Hello Federico, or anyone else affected,
Accepted apparmor into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/apparmor/2.8.0-0ubuntu31.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
what about Saucy?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salamander
To manage notifications about this bug go to:
https://bugs.launchpad.net/ac100/+b
This bug was fixed in the package apparmor - 2.8.0-0ubuntu34
---
apparmor (2.8.0-0ubuntu34) trusty; urgency=low
[ Tyler Hicks ]
* 0078-parser-check-for-dbus-kernel-support.patch: The parser should not
include D-Bus rules in the binary policy that it loads into the kernel if
** Branch linked: lp:ubuntu/trusty-proposed/apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salamander
To manage notifications about this bug go to:
apparmor 2.8.0-0ubuntu34 uploaded to trusty.
** Changed in: apparmor (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi no
** Changed in: apparmor (Ubuntu Trusty)
Status: Triaged => In Progress
** Changed in: apparmor (Ubuntu Saucy)
Status: Triaged => In Progress
** Changed in: apparmor
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Uploaded 2.8.0-0ubuntu31.1. Tyler, can you make sure you follow any of
the other steps in https://wiki.ubuntu.com/StableReleaseUpdates so it
shows up on the SRU team's radar?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
apparmor 2.8.0-0ubuntu34 is awaiting landing team approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salamander
To manage notifications about this bug
Unsusubscribing sponsors, Marc said that the security team is going to
take care of sponsoring that one
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salaman
I've added tests for this bug and bug 1243932 to QRT's test-apparmor.py.
I've successfully ran the new tests on Trusty and Saucy. I ran the tests
under a Trusty/Saucy, Raring, and Lucid kernels to test all potential
policy load scenarios. All scenarios pass.
** Description changed:
[Impact]
** Also affects: network-manager (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: apparmor
The attachment "apparmor_2.8.0-0ubuntu31.1.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "pat
Here's a Saucy debdiff for apparmor to fix this bug and bug 1243932.
I've tested it using the manual tests mentioned in the description of
both bugs, as well as with QRT's test-apparmor.py test script.
** Patch added: "apparmor_2.8.0-0ubuntu31.1.debdiff"
https://bugs.launchpad.net/apparmor/+bu
Here's a Trusty debdiff for apparmor to fix this bug, bug 1243932, and
bug 1247269. I've tested it using the manual tests mentioned in the
description of the first two bugs, as well as with QRT's test-
apparmor.py test script.
I've smoke tested the chromium-browser profile changes and manually
ver
** Description changed:
[Impact]
On older kernels that are missing certain AppArmor patches related to
AppArmor D-Bus mediation, the presence of dbus rules in the binary
AppArmor policy will result in policy load failures and, as a result,
applications may run unconfined. On newer ker
** Description changed:
+ [Impact]
+
+ On older kernels that are missing certain AppArmor patches related to
+ AppArmor D-Bus mediation, the presence of dbus rules in the binary
+ AppArmor policy will result in policy load failures and, as a result,
+ applications may run unconfined. On newer ker
** Branch linked: lp:apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231778
Title:
wifi not working on Saucy Salamander
To manage notifications about this bug go to:
https://bugs.launchpad.
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => In Progress
** Changed in: apparmor
Importance: Undecided => Medium
** Changed in: apparmor
Assignee: (unassigned) => Tyler Hicks (tyhicks)
--
You received this bug notif
This is most likely due to the apparmor_parser errors. They are caused
by having a new apparmor_parser, new policy (which now includes dbus
rules), and old kernel.
The parser should be checking to see if the kernel supports dbus rules.
Looking at the mount rule support in the parser,
* in parser/
Can you please provide the contents of
sudo aa-status
/etc/apparmor.d/cache/.features
/etc/apparmor.d/cache/sbin.dhclient
ls -a /sys/kernel/security/apparmor/
if present (and dependent on whether its a dir or file)
ls -a /sys/kernel/security/apparmor/features
or
cat -s /sys/kernel
[ 59.264921] type=1400 audit(1380291018.856:28): apparmor="STATUS"
info="failed to unpack profile" error=-71 pid=781 comm="apparmor_parser"
name="/usr/lib/NetworkManager/nm-dhcp-client.action" offset=155
this line from dmesg looks very suspicious ... adding
"apparmor.enable=0" to the kernel cmdl
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
32 matches
Mail list logo
