You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Other Issues » [SOLVED] Apparmor update causing issues (Ceres) » Yesterday 11:18:22
Greetings:
After updating today this issue has disappeared. I suspect that this was due to these packages:
isc-dhcp-client
isc-dhcp-common
I haven't verified this but it makes sone sense considering the Apparmor profile that was having the issues.
Closing.
#2 Re: Other Issues » [SOLVED] Apparmor update causing issues (Ceres) » 2025-04-16 10:31:50
Linux kernel with Microsoft security module integration doing all of that.
I would assume one could disable this kernel module either modularly or when building the kernel (ie: Gentoo) if one doesn't want it, Some distros may integrate and others will scrutinize it heavily (hopefully).
As far as the Apparmor issues:
I have worked on this a bit and have found that after a restart of the apparmor service, the problematic apparmor profile will load properly. Here is a diff of the before/after of the aa-status showing the module that is started:
→ diff aa-status1 aa-status2
9a10
> "/usr/{lib/NetworkManager,libexec}/nm-dhcp-helper": "enforce",This matches Debian without needing to restart the service. I am starting to think it is a timing issue of some sort or Debian restarts the service for you. Haven't got that far.
If I try to enable this profile manually prior to restarting the service, it will fail complaining of a duplicate profile (sbin.dhclient/usr.sbin.dhclient).
That's about as far as I've gotten thus far.
EDIT: Changed codeblock to quote.
#3 Re: Other Issues » [SOLVED] Apparmor update causing issues (Ceres) » 2025-04-13 13:09:40
Hello Altoid,
It was installed and enabled from the minimal installation iso, otherwise I would not have it either. It hadn't really given me any issues until the update.
The only reason I don't disable it (yet) is because it is working on Sid (why not here?) I'll fight with it a bit before disabling completely (or a new update fixes).
I'd file a bug but I don't like Debian or Devuan bug systems, but that's a whole different topic.
EDIT: We were typing at the same time. I will say that it sounds like a pain to get rid of and/or disable (completely) too. I haven't looked into that but have seen many people looking for info. on how to do it. 
Have a good one.
#4 Other Issues » [SOLVED] Apparmor update causing issues (Ceres) » 2025-04-13 10:56:42
- Weezer
- Replies: 9
Greetings!
After updating 2 days ago, Apparmor was updated:
(apparmor:amd64 (4.1.0~beta5-6, 4.1.0-1), libapparmor1:amd64 (4.1.0~beta5-6, 4.1.0-1))
Following the update I am getting this error when booting:
Starting: AppArmorLoading AppArmor profiles...Error: Could not load profile /var/cache/apparmor/ac27e0ee.0/usr.sbin.dhclient: File exists
Sun Apr 13 06:20:10 2025: /sbin/apparmor_parser: Unable to add "/usr/lib/NetworkManager/nm-dhcp-client.action". Profile already exists
Sun Apr 13 06:20:10 2025: At least one profile failed to load ... failed!
Sun Apr 13 06:20:10 2025: failed.
I have disabled the usr.sbin.dhclient profile temporarily and that removes the error upon boot:
ln -s /etc/apparmor.d/usr.sbin.dhclient /etc/apparmor.d/disable
I run a few different distros on my computer, one being Debian-Sid, and it is not producing these errors. I've compared related apparmor files/configs and they are all identical.
I've checked bug reports and the Apparmor Gitlab and nothing mentioned about this.
Anyone else having this issue (if you haven't disabled apparmor already :) ) and how did you deal with this? I'm no apparmor expert and mostly let it do it's thing.
Thanks in advance!
EDIT: I forgot to mention that the 'usr.sbin.dhclient' apparmor profile is new with the latest update to apparmor. There was only 'sbin.dhclient' profile, now there are both.
Pages: 1
Board footer
