Ubuntu
apparmor package

Apparmor breaks wireless networking

Bug #408829 reported by tekstr1der on 2009-08-04

This bug report is a duplicate of: Bug #408773: apparmor capabilities not working properly. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	apparmor (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: apparmor

Recent updates to apparmor seem to have broken network manager's ability to connect to wireless networks. Disabling apparmor fixes the issue:

sudo /etc/init.d/apparmor stop
sudo /etc/init.d/networking restart

This is confirmed by several users on Ubuntu forum and being discussed here: http://ubuntuforums.org/showthread.php?s=428e0b667e34aacbc8524aa2814f368f&t=1231130

ProblemType: Bug
ApparmorStatusOutput:
Error: command /usr/sbin/apparmor_status failed with exit code 4: You do not have enough privilege to read the profile set.
apparmor module is loaded.
Architecture: i386
Date: Tue Aug 4 08:33:15 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: apparmor 2.3.1+1403-0ubuntu8
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SourcePackage: apparmor
Uname: Linux 2.6.31-5-generic i686

Tags:

Revision history for this message

tekstr1der (tekstr1der) wrote on 2009-08-04:

ApparmorPackages.txt Edit (302 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (222 bytes, text/plain; charset="utf-8")
KernLog.txt Edit (11.6 KiB, text/plain; charset="utf-8")
PstreeP.txt Edit (6.8 KiB, text/plain; charset="utf-8")

Revision history for this message

unchiujar (vasile-jureschi) wrote on 2009-08-04:

Same thing happens to me, it is apparmor and dhclient related.

If I disable Network Manager and try to get the settings through dhclient I get:

#dhclient eth0
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Open a socket for LPF: Operation not permitted

Settings complaining mode for dhclient fixes the situation and I can connect to wired/wireless:

#aa-complain --complain /sbin/dhclient
#/etc/init.d/NetworkManager restart

Hope this helps.

Revision history for this message

Jamie Strandboge (jdstrand) wrote on 2009-08-04:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 408773, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.