apparmor prevents user from connecting to network

[Iain Buclaw]

Currently in the LiveCD, users are unable to connect to any network due to the enforced apparmor profile on nm-dhcp-client.action profile located in: /etc/apparmor/sbin.dhclient3

Whilst there is nothing wrong with the profile inheritably, the application actually tries to access the file of the read-only filesystem, rather than on the rootfs mount.
ie: instead of reading:
/usr/lib/libdbus-glib-1.so.2.1.0
it instead tries and fails to read:
/rofs/usr/lib/libdbus-glib-1.so.2.1.0

It's not a major issue, but this is the reason as to why have been reporting no network connectivity in the LiveCD.

[Iain Buclaw (iainb)]

Attached is a snipped version of the logs from /var/log/messages which list the problematic files.

The way to currently work around the issue is just disabling apparmor on the LiveCD via:
sudo service stop apparmor
sudo restart network-manager

Regards

[bodhi.zazen (bodhi.zazen)]

Thank you for this report, it is helpful.

I will review the apparmor profiles.

In the future, it is very helpful if the apparmor log is included, even better if you know the offending line.

Now this can be tricky as apparmor generates a lot of logs.

IMO it is best to work with one profile at a time and rather then disable it , place it in complain mode.

sudo aa-complain dhclient3

clear the log

sudo -c bash ">| /var/log/messages"

Then reboot and check the logs.

[bodhi.zazen (bodhi.zazen)]

This is resolved in the new iso