Apparmor Profile Error because of wrong file under /etc/apparmor.d/local as leftover from previous versions #2835

bool_purist commented 2026年01月27日 23:33:02 +01:00

LibreWolf Version

147.0.2-1

Operating System

Debian / Ubuntu / Mint

Installation Source / Package

Official Repository (Debian/Ubuntu/Fedora/openSUSE)

Description

On 27.01.2026 I updated my system via sudo apt update && sudo apt upgrade. I got the following error.

Get:1 http://security.debian.org/debian-security trixie-security/main amd64 openssl-provider-legacy amd64 3.5.4-1~deb13u2 [308 kB]
Get:2 http://security.debian.org/debian-security trixie-security/main i386 libssl3t64 i386 3.5.4-1~deb13u2 [2,425 kB] 
Get:4 https://mise.jdx.dev/deb stable/main amd64 mise amd64 2026年1月8日 [28.9 MB] 
Get:5 http://security.debian.org/debian-security trixie-security/main amd64 libssl3t64 amd64 3.5.4-1~deb13u2 [2,442 kB]
Get:6 http://security.debian.org/debian-security trixie-security/main amd64 openssl amd64 3.5.4-1~deb13u2 [1,495 kB]
Get:3 https://repo.librewolf.net librewolf/main amd64 librewolf amd64 147.0.2-1 [128 MB] 
Fetched 164 MB in 13s (12.8 MB/s) 
apt-listchanges: Reading changelogs...
(Reading database ... 83873 files and directories currently installed.)
Preparing to unpack .../openssl-provider-legacy_3.5.4-1~deb13u2_amd64.deb ...
Unpacking openssl-provider-legacy (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1) ...
Setting up openssl-provider-legacy (3.5.4-1~deb13u2) ...
(Reading database ... 83873 files and directories currently installed.)
Preparing to unpack .../libssl3t64_3.5.4-1~deb13u2_amd64.deb ...
De-configuring libssl3t64:i386 (3.5.4-1~deb13u1), to allow configuration of libssl3t64:amd64 (3.5.4-1~deb13u2) ...
Unpacking libssl3t64:amd64 (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1) ...
Preparing to unpack .../libssl3t64_3.5.4-1~deb13u2_i386.deb ...
Unpacking libssl3t64:i386 (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1) ...
Preparing to unpack .../librewolf_147.0.2-1_amd64.deb ...
Unpacking librewolf (147.0.2-1) over (147.0.1-3) ...
Preparing to unpack .../mise_2026年1月8日_amd64.deb ...
Unpacking mise (2026年1月8日) over (2026年1月7日) ...
Preparing to unpack .../openssl_3.5.4-1~deb13u2_amd64.deb ...
Unpacking openssl (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1) ...
Setting up librewolf (147.0.2-1) ...
Job for apparmor.service failed because the control process exited with error code.
See "systemctl status apparmor.service" and "journalctl -xeu apparmor.service" for details.
Setting up libssl3t64:amd64 (3.5.4-1~deb13u2) ...
Setting up libssl3t64:i386 (3.5.4-1~deb13u2) ...
Setting up mise (2026年1月8日) ...
Setting up openssl (3.5.4-1~deb13u2) ...
Processing triggers for hicolor-icon-theme (0.18-2) ...
Processing triggers for libc-bin (2.41-12+deb13u1) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for desktop-file-utils (0.28-1) ...

The command sudo systemctl status apparmor.service gives me following output

Jan 27 22:22:08 nice-box systemd[1]: Starting apparmor.service - Load AppArmor profiles...
Jan 27 22:22:08 nice-box apparmor.systemd[6072]: Restarting AppArmor
Jan 27 22:22:08 nice-box apparmor.systemd[6072]: Reloading AppArmor profiles
Jan 27 22:22:08 nice-box apparmor.systemd[6110]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/tunables/home at line 15: syntax error, unexpected TOK_>
Jan 27 22:22:08 nice-box apparmor.systemd[6183]: Skipping profile in /etc/apparmor.d/disable: usr.bin.thunderbird
Jan 27 22:22:08 nice-box apparmor.systemd[6072]: Error: At least one profile failed to load
Jan 27 22:22:08 nice-box systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE
Jan 27 22:22:08 nice-box systemd[1]: apparmor.service: Failed with result 'exit-code'.
Jan 27 22:22:08 nice-box systemd[1]: Failed to start apparmor.service - Load AppArmor profiles.

This error keeps happening after sudo systemctl restart apparmor.service

When I however replace the file under /etc/apparmor.d/local/librewolf with en empty one then the error goes away after the command sudo systemctl restart apparmor.service.

Empty files under /etc/apparmor.d/local are normal and do not cause any problems. Not all syntax under /etc/apparmor.d/librewolf which was saved under /etc/apparmor.d/local before, is valid for a file under /etc/apparmor.d/local.

I think this comes from this recent commit, librewolf/bsys6@822b6a99a9, which leads to 2 apparmor files under /etc/apparmor.d/librewolf and /etc/apparmor.d/local/librewolf for all people with a previous version before 147.0.2.1 since there is a leftover under /etc/apparmor.d/local/librewolf.

Current Workaround for User before the Fix

Remove the profile under /etc/apparmor.d/local/librewolf to fix the error.

My proposed change

In the next path you should provide again a file under /etc/apparmor.d/local/librewolf but without any content so it does not cause any errors.

Logs / Screenshots

No response

### LibreWolf Version 147.0.2-1 ### Operating System Debian / Ubuntu / Mint ### Installation Source / Package Official Repository (Debian/Ubuntu/Fedora/openSUSE) ### Description On 27.01.2026 I updated my system via `sudo apt update && sudo apt upgrade`. I got the following error. ``` Get:1 http://security.debian.org/debian-security trixie-security/main amd64 openssl-provider-legacy amd64 3.5.4-1~deb13u2 [308 kB] Get:2 http://security.debian.org/debian-security trixie-security/main i386 libssl3t64 i386 3.5.4-1~deb13u2 [2,425 kB] Get:4 https://mise.jdx.dev/deb stable/main amd64 mise amd64 2026年1月8日 [28.9 MB] Get:5 http://security.debian.org/debian-security trixie-security/main amd64 libssl3t64 amd64 3.5.4-1~deb13u2 [2,442 kB] Get:6 http://security.debian.org/debian-security trixie-security/main amd64 openssl amd64 3.5.4-1~deb13u2 [1,495 kB] Get:3 https://repo.librewolf.net librewolf/main amd64 librewolf amd64 147.0.2-1 [128 MB] Fetched 164 MB in 13s (12.8 MB/s) apt-listchanges: Reading changelogs... (Reading database ... 83873 files and directories currently installed.) Preparing to unpack .../openssl-provider-legacy_3.5.4-1~deb13u2_amd64.deb ... Unpacking openssl-provider-legacy (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1) ... Setting up openssl-provider-legacy (3.5.4-1~deb13u2) ... (Reading database ... 83873 files and directories currently installed.) Preparing to unpack .../libssl3t64_3.5.4-1~deb13u2_amd64.deb ... De-configuring libssl3t64:i386 (3.5.4-1~deb13u1), to allow configuration of libssl3t64:amd64 (3.5.4-1~deb13u2) ... Unpacking libssl3t64:amd64 (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1) ... Preparing to unpack .../libssl3t64_3.5.4-1~deb13u2_i386.deb ... Unpacking libssl3t64:i386 (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1) ... Preparing to unpack .../librewolf_147.0.2-1_amd64.deb ... Unpacking librewolf (147.0.2-1) over (147.0.1-3) ... Preparing to unpack .../mise_2026年1月8日_amd64.deb ... Unpacking mise (2026年1月8日) over (2026年1月7日) ... Preparing to unpack .../openssl_3.5.4-1~deb13u2_amd64.deb ... Unpacking openssl (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1) ... Setting up librewolf (147.0.2-1) ... Job for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xeu apparmor.service" for details. Setting up libssl3t64:amd64 (3.5.4-1~deb13u2) ... Setting up libssl3t64:i386 (3.5.4-1~deb13u2) ... Setting up mise (2026年1月8日) ... Setting up openssl (3.5.4-1~deb13u2) ... Processing triggers for hicolor-icon-theme (0.18-2) ... Processing triggers for libc-bin (2.41-12+deb13u1) ... Processing triggers for man-db (2.13.1-1) ... Processing triggers for desktop-file-utils (0.28-1) ... ``` The command `sudo systemctl status apparmor.service` gives me following output ``` Jan 27 22:22:08 nice-box systemd[1]: Starting apparmor.service - Load AppArmor profiles... Jan 27 22:22:08 nice-box apparmor.systemd[6072]: Restarting AppArmor Jan 27 22:22:08 nice-box apparmor.systemd[6072]: Reloading AppArmor profiles Jan 27 22:22:08 nice-box apparmor.systemd[6110]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/tunables/home at line 15: syntax error, unexpected TOK_> Jan 27 22:22:08 nice-box apparmor.systemd[6183]: Skipping profile in /etc/apparmor.d/disable: usr.bin.thunderbird Jan 27 22:22:08 nice-box apparmor.systemd[6072]: Error: At least one profile failed to load Jan 27 22:22:08 nice-box systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE Jan 27 22:22:08 nice-box systemd[1]: apparmor.service: Failed with result 'exit-code'. Jan 27 22:22:08 nice-box systemd[1]: Failed to start apparmor.service - Load AppArmor profiles. ``` This error keeps happening after `sudo systemctl restart apparmor.service` When I however replace the file under `/etc/apparmor.d/local/librewolf` with en empty one then the error goes away after the command `sudo systemctl restart apparmor.service`. Empty files under `/etc/apparmor.d/local` are normal and do not cause any problems. Not all syntax under `/etc/apparmor.d/librewolf` which was saved under `/etc/apparmor.d/local` before, is valid for a file under `/etc/apparmor.d/local`. I think this comes from this recent commit, https://codeberg.org/librewolf/bsys6/commit/822b6a99a939fa039866b3d9bba1b7f5489be379, which leads to 2 apparmor files under `/etc/apparmor.d/librewolf` and `/etc/apparmor.d/local/librewolf` for all people with a previous version before 147.0.2.1 since there is a leftover under `/etc/apparmor.d/local/librewolf`. ## Current Workaround for User before the Fix Remove the profile under `/etc/apparmor.d/local/librewolf` to fix the error. ## My proposed change In the next path you should provide again a file under `/etc/apparmor.d/local/librewolf` but without any content so it does not cause any errors. ### Logs / Screenshots _No response_

daanmageddon commented 2026年01月28日 15:22:15 +01:00

"AppArmor parser error for /etc/apparmor.d/librewolf in profile /etc/apparmor.d/tunables/home at line 15: syntax error, unexpected TOK_EQUALS, expecting TOK_MODE" is the specific error "apparmor_parser -qp /etc/apparmor.d/librewolf" raises.

"AppArmor parser error for /etc/apparmor.d/librewolf in profile /etc/apparmor.d/tunables/home at line 15: syntax error, unexpected TOK_EQUALS, expecting TOK_MODE" is the specific error "apparmor_parser -qp /etc/apparmor.d/librewolf" raises.

any1here commented 2026年01月28日 15:23:57 +01:00

@daanmageddon

Remove the profile under /etc/apparmor.d/local/librewolf to fix the error.

@daanmageddon > Remove the profile under /etc/apparmor.d/local/librewolf to fix the error.

daanmageddon commented 2026年01月28日 16:39:12 +01:00

@any1here wrote in #2835 (comment):

@daanmageddon

Remove the profile under /etc/apparmor.d/local/librewolf to fix the error.

Yeah i know, i just wanted to add some additional information. Didnt spot the error "unexpected TOK_EQUALS, expecting TOK_MODE" in your writeup, cheers.
EDIT: that wasnt your writeup, the possible temp fix is already mentioned in there, but not the exact error. Im just adding that so others can find it when searching for it.

@any1here wrote in https://codeberg.org/librewolf/issues/issues/2835#issuecomment-10232962: > @daanmageddon > > > Remove the profile under /etc/apparmor.d/local/librewolf to fix the error. Yeah i know, i just wanted to add some additional information. Didnt spot the error "unexpected TOK_EQUALS, expecting TOK_MODE" in your writeup, cheers. EDIT: that wasnt your writeup, the possible temp fix is already mentioned in there, but not the exact error. Im just adding that so others can find it when searching for it.

htconst commented 2026年01月28日 17:36:12 +01:00

For what its worth, I am running Linux Mint 21 on two machines and this is what I experienced on the one, and then verified on the second:
Last night on the first machine I updated Librewolf from 147.0.1-3 to 147.0.2-1. During the update there was something about an error but it scrolled by too fast for me to see. This morning during startup I saw the apparmor error, which got my attention. The error I got is that it couldn't find the file abi/4.0, and sure enough in the apparmor.d/abi folder this version of Linux Mint only has a file called 3.0. My first move was to change theabi <abi/4.0> line to abi <abi/3.0> on the librewolf file that is located in /etc/apparmor.d, after which I got the "unexpected TOK_END_OF_RULE, expecting TOK_MODE" error. After reading the proposed solutions here, I deleted the librewolf file located in /etc/apparmor.d and apparmor loaded normally.
What I must mention here is that there is a librewolf file located in /etc/apparmor.d/local but it does not seem to bother the apparmor process.
I verified this on the second machine, which had Librewolf 147.0.1-3. On this machine at this point there was no librewolf file at /etc/apparmor.d/ but there was one at /etc/apparmor.d/local. This file referenced abi/4.0, by the way.
I ran the update process and installed Librewolf 147.0.2-1 and this caused the apparamor error during the installation process. After the installation there was now a librewolf file at /etc/apparmor.d/. I compared the contents of the two librewolf files, the one at /etc/apparmor.d/ and the one at /etc/apparmor.d/local and they are identical. The fix I tried here was, instead of deleting the librewolf file at /etc/apparmor.d/, I edited it. I kept the first two lines with the comments and deleted the rest. This works too.
So, to conclude, I think that the Librewolf installation process for 147.0.2-1 erroneously copied the librewolf file to /etc/apparmor.d/ instead of to /etc/apparmor.d/local.

For what its worth, I am running Linux Mint 21 on two machines and this is what I experienced on the one, and then verified on the second: Last night on the first machine I updated Librewolf from 147.0.1-3 to 147.0.2-1. During the update there was something about an error but it scrolled by too fast for me to see. This morning during startup I saw the apparmor error, which got my attention. The error I got is that it couldn't find the file abi/4.0, and sure enough in the apparmor.d/abi folder this version of Linux Mint only has a file called 3.0. My first move was to change theabi <abi/4.0> line to abi <abi/3.0> on the librewolf file that is located in /etc/apparmor.d, after which I got the "unexpected TOK_END_OF_RULE, expecting TOK_MODE" error. After reading the proposed solutions here, I deleted the librewolf file located in /etc/apparmor.d and apparmor loaded normally. What I must mention here is that there is a librewolf file located in /etc/apparmor.d/local but it does not seem to bother the apparmor process. I verified this on the second machine, which had Librewolf 147.0.1-3. On this machine at this point there was no librewolf file at /etc/apparmor.d/ but there was one at /etc/apparmor.d/local. This file referenced abi/4.0, by the way. I ran the update process and installed Librewolf 147.0.2-1 and this caused the apparamor error during the installation process. After the installation there was now a librewolf file at /etc/apparmor.d/. I compared the contents of the two librewolf files, the one at /etc/apparmor.d/ and the one at /etc/apparmor.d/local and they are identical. The fix I tried here was, instead of deleting the librewolf file at /etc/apparmor.d/, I edited it. I kept the first two lines with the comments and deleted the rest. This works too. So, to conclude, I think that the Librewolf installation process for 147.0.2-1 erroneously copied the librewolf file to /etc/apparmor.d/ instead of to /etc/apparmor.d/local.

alyx161 commented 2026年01月28日 18:12:45 +01:00

The file is suppose to be at /etc/apparmor.d/librewolf
The previous version accidentlally created it in /etc/apparmor.d/local/librewolf.

If you would like to address/fix this issue, please delete /etc/apparmor.d/local/librewolf and NOT /etc/apparmor.d/librewolf.
Any changes to /etc/apparmor.d/librewolf will be overriten in the next update.

@htconst The file in /etc/apparmor.d/local/librewolf can, and probably should, be deleted.
Its not suppose to be there unless you really know what you are doing and you want to do manual overrides.

The file is suppose to be at /etc/apparmor.d/librewolf The previous version accidentlally created it in `/etc/apparmor.d/local/librewolf`. If you would like to address/fix this issue, please delete `/etc/apparmor.d/local/librewolf` and **NOT** `/etc/apparmor.d/librewolf`. Any changes to `/etc/apparmor.d/librewolf` will be overriten in the next update. @htconst The file in `/etc/apparmor.d/local/librewolf` can, and probably should, be deleted. Its not suppose to be there unless you really know what you are doing and you want to do manual overrides.

htconst commented 2026年01月29日 09:43:44 +01:00

@alyx161 Thank you for your prompt reply and for setting me on the right path (sorry for the pun). I have deleted the /etc/apparmor.d/local/librewolf file as per your instructions. Thanks again! :-)

@alyx161 Thank you for your prompt reply and for setting me on the right path (sorry for the pun). I have deleted the /etc/apparmor.d/local/librewolf file as per your instructions. Thanks again! :-)

notDavid commented 2026年02月03日 14:24:24 +01:00

Fyi, the problem seems to be that 2 identical files are created. I did a very recent first time install of Librewolf on Ubuntu 22.04.3 LTS :

Removing either one of these duplicates fixes the problem.

❯ find /etc/apparmor.d/ -type f -exec md5sum {} + | sort | uniq -w32 -d --all-repeated=separate
c673ced43ad0927cfdcbd55c6125665f /etc/apparmor.d/librewolf
c673ced43ad0927cfdcbd55c6125665f /etc/apparmor.d/local/librewolf

❯ dpkg --listfiles librewolf 
/.
/usr
#
# ...REMOVED because not relevant
#
/etc
/etc/apparmor.d
/etc/apparmor.d/librewolf
/usr/bin/librewolf
/etc/apparmor.d/local/librewolf

❯ apt policy librewolf
librewolf:
 Installed: 147.0.2-1
 Candidate: 147.0.2-1
 Version table:
 *** 147.0.2-1 500
 500 https://repo.librewolf.net librewolf/main amd64 Packages
 500 https://repo.librewolf.net librewolf/main arm64 Packages
 100 /var/lib/dpkg/status
# ...REMOVED because not relevant

Fyi, the problem seems to be that 2 **identical** files are created. I did a very recent first time install of Librewolf on Ubuntu 22.04.3 LTS : Removing either one of these duplicates fixes the problem. ```shell ❯ find /etc/apparmor.d/ -type f -exec md5sum {} + | sort | uniq -w32 -d --all-repeated=separate c673ced43ad0927cfdcbd55c6125665f /etc/apparmor.d/librewolf c673ced43ad0927cfdcbd55c6125665f /etc/apparmor.d/local/librewolf ``` ```shell ❯ dpkg --listfiles librewolf /. /usr # # ...REMOVED because not relevant # /etc /etc/apparmor.d /etc/apparmor.d/librewolf /usr/bin/librewolf /etc/apparmor.d/local/librewolf ``` ```shell ❯ apt policy librewolf librewolf: Installed: 147.0.2-1 Candidate: 147.0.2-1 Version table: *** 147.0.2-1 500 500 https://repo.librewolf.net librewolf/main amd64 Packages 500 https://repo.librewolf.net librewolf/main arm64 Packages 100 /var/lib/dpkg/status # ...REMOVED because not relevant ```

alyx161 commented 2026年02月03日 14:41:12 +01:00

@notDavid wrote in #2835 (comment):

Removing either one of these duplicates fixes the problem.

As mentioend 2 comments above yours (#2835 (comment)), removing /etc/apparmor.d/librewolf will NOT be a persistent solution.

If you want to fix this, then please remove /etc/apparmor.d/local/librewolf and nothing else.

Will close this issue for now.
Issue was fixed with librewolf/bsys6!28 and will be in the next release.

@notDavid wrote in https://codeberg.org/librewolf/issues/issues/2835#issuecomment-10341192: > Removing either one of these duplicates fixes the problem. As mentioend **2 comments above yours** (https://codeberg.org/librewolf/issues/issues/2835#issuecomment-10235881), removing /etc/apparmor.d/librewolf will **NOT** be a persistent solution. If you want to fix this, then please remove `/etc/apparmor.d/local/librewolf` and nothing else. Will close this issue for now. Issue was fixed with librewolf/bsys6!28 and will be in the next release.

visualblind commented 2026年02月07日 06:14:46 +01:00

Even though this is closed I wanted to add that I had the same exact issue with Librewolf 147.0.2-1 on LMDE 7 (linux mint debian edition) and this solution resolved it.

Even though this is closed I wanted to add that I had the same exact issue with Librewolf 147.0.2-1 on LMDE 7 (linux mint debian edition) and this solution resolved it.

1sroberts commented 2026年02月09日 06:02:43 +01:00

I seem to be running into the same or similar issue.

current versions of os and librewolf:

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"

$ librewolf --version
Mozilla LibreWolf 147.0.3-2

I took a look at /etc/apparmor.d and /etc/apparmor.d/local it doesn't look like there is a duplicate file currently

/etc/apparmor.d/local$ ls -larth /etc/apparmor.d/ | grep -i librewolf
-rw-r--r-- 1 root root 391 Feb 7 23:33 librewolf

/etc/apparmor.d/local$ ls -larth /etc/apparmor.d/local/ | librewolf

However when attempting to start/restart the apparmor.service I sun into the same Could not open 'abi/4.0': No such file or directory error

systemctl status apparmor.service
×ばつ apparmor.service - Load AppArmor profiles
Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sun 2026年02月08日 09:21:08 EST; 14h ago
Docs: man:apparmor(7)
https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 905 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, status=1/FAILURE)
Main PID: 905 (code=exited, status=1/FAILURE)
CPU: 417ms

Feb 08 09:21:08 apparmor.systemd[905]: Restarting AppArmor
Feb 08 09:21:08 apparmor.systemd[905]: Reloading AppArmor profiles
Feb 08 09:21:08 apparmor.systemd[918]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/librewolf at line 3: Could not open 'abi/4.0': No such file or directory
Feb 08 09:21:08 apparmor.systemd[1003]: AppArmor parser error for /etc/apparmor.d/librewolf in profile /etc/apparmor.d/librewolf at line 3: Could not open 'abi/4.0': No such file or directory
Feb 08 09:21:08 apparmor.systemd[905]: Error: At least one profile failed to load
Feb 08 09:21:07 systemd[1]: Starting apparmor.service - Load AppArmor profiles...
Feb 08 09:21:08 systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 09:21:08 systemd[1]: apparmor.service: Failed with result 'exit-code'.
Feb 08 09:21:08 systemd[1]: Failed to start apparmor.service - Load AppArmor profiles.

Thanks for taking a look at this and if there is any additional information that I can provide, let me know.

I seem to be running into the same or similar issue. current versions of os and librewolf: > $ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" > $ librewolf --version Mozilla LibreWolf 147.0.3-2 I took a look at /etc/apparmor.d and /etc/apparmor.d/local it doesn't look like there is a duplicate file currently > /etc/apparmor.d/local$ ls -larth /etc/apparmor.d/ | grep -i librewolf -rw-r--r-- 1 root root 391 Feb 7 23:33 librewolf > /etc/apparmor.d/local$ ls -larth /etc/apparmor.d/local/ | librewolf However when attempting to start/restart the apparmor.service I sun into the same `Could not open 'abi/4.0': No such file or directory` error > systemctl status apparmor.service ×ばつ apparmor.service - Load AppArmor profiles Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sun 2026年02月08日 09:21:08 EST; 14h ago Docs: man:apparmor(7) https://gitlab.com/apparmor/apparmor/wikis/home/ Process: 905 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, status=1/FAILURE) Main PID: 905 (code=exited, status=1/FAILURE) CPU: 417ms > Feb 08 09:21:08 apparmor.systemd[905]: Restarting AppArmor Feb 08 09:21:08 apparmor.systemd[905]: Reloading AppArmor profiles Feb 08 09:21:08 apparmor.systemd[918]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/librewolf at line 3: Could not open 'abi/4.0': No such file or directory Feb 08 09:21:08 apparmor.systemd[1003]: AppArmor parser error for /etc/apparmor.d/librewolf in profile /etc/apparmor.d/librewolf at line 3: Could not open 'abi/4.0': No such file or directory Feb 08 09:21:08 apparmor.systemd[905]: Error: At least one profile failed to load Feb 08 09:21:07 systemd[1]: Starting apparmor.service - Load AppArmor profiles... Feb 08 09:21:08 systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE Feb 08 09:21:08 systemd[1]: apparmor.service: Failed with result 'exit-code'. Feb 08 09:21:08 systemd[1]: Failed to start apparmor.service - Load AppArmor profiles. Thanks for taking a look at this and if there is any additional information that I can provide, let me know.

any1here commented 2026年02月09日 15:16:17 +01:00

@1sroberts wrote in #2835 (comment):

I seem to be running into the same or similar issue.

current versions of os and librewolf:

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"

$ librewolf --version
Mozilla LibreWolf 147.0.3-2

I took a look at /etc/apparmor.d and /etc/apparmor.d/local it doesn't look like there is a duplicate file currently

/etc/apparmor.d/local$ ls -larth /etc/apparmor.d/ | grep -i librewolf
-rw-r--r-- 1 root root 391 Feb 7 23:33 librewolf

/etc/apparmor.d/local$ ls -larth /etc/apparmor.d/local/ | librewolf

However when attempting to start/restart the apparmor.service I sun into the same Could not open 'abi/4.0': No such file or directory error

systemctl status apparmor.service
×ばつ apparmor.service - Load AppArmor profiles
Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sun 2026年02月08日 09:21:08 EST; 14h ago
Docs: man:apparmor(7)
https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 905 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, status=1/FAILURE)
Main PID: 905 (code=exited, status=1/FAILURE)
CPU: 417ms

Feb 08 09:21:08 apparmor.systemd[905]: Restarting AppArmor
Feb 08 09:21:08 apparmor.systemd[905]: Reloading AppArmor profiles
Feb 08 09:21:08 apparmor.systemd[918]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/librewolf at line 3: Could not open 'abi/4.0': No such file or directory
Feb 08 09:21:08 apparmor.systemd[1003]: AppArmor parser error for /etc/apparmor.d/librewolf in profile /etc/apparmor.d/librewolf at line 3: Could not open 'abi/4.0': No such file or directory
Feb 08 09:21:08 apparmor.systemd[905]: Error: At least one profile failed to load
Feb 08 09:21:07 systemd[1]: Starting apparmor.service - Load AppArmor profiles...
Feb 08 09:21:08 systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 09:21:08 systemd[1]: apparmor.service: Failed with result 'exit-code'.
Feb 08 09:21:08 systemd[1]: Failed to start apparmor.service - Load AppArmor profiles.

Thanks for taking a look at this and if there is any additional information that I can provide, let me know.

This is because Debian 12 is stuck on AppArmor 3. librewolf/bsys6#29 adds a check if AppArmor 4 is supported and otherwise removes the AppArmor file.

@1sroberts wrote in https://codeberg.org/librewolf/issues/issues/2835#issuecomment-10462612: > I seem to be running into the same or similar issue. > > current versions of os and librewolf: > > > $ cat /etc/os-release > > PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" > > NAME="Debian GNU/Linux" > > VERSION_ID="12" > > VERSION="12 (bookworm)" > > > $ librewolf --version > > Mozilla LibreWolf 147.0.3-2 > > I took a look at /etc/apparmor.d and /etc/apparmor.d/local it doesn't look like there is a duplicate file currently > > > /etc/apparmor.d/local$ ls -larth /etc/apparmor.d/ | grep -i librewolf > > -rw-r--r-- 1 root root 391 Feb 7 23:33 librewolf > > > /etc/apparmor.d/local$ ls -larth /etc/apparmor.d/local/ | librewolf > > However when attempting to start/restart the apparmor.service I sun into the same `Could not open 'abi/4.0': No such file or directory` error > > > systemctl status apparmor.service > > ×ばつ apparmor.service - Load AppArmor profiles > > Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; preset: enabled) > > Active: failed (Result: exit-code) since Sun 2026年02月08日 09:21:08 EST; 14h ago > > Docs: man:apparmor(7) > > https://gitlab.com/apparmor/apparmor/wikis/home/ > > Process: 905 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, status=1/FAILURE) > > Main PID: 905 (code=exited, status=1/FAILURE) > > CPU: 417ms > > > Feb 08 09:21:08 apparmor.systemd[905]: Restarting AppArmor > > Feb 08 09:21:08 apparmor.systemd[905]: Reloading AppArmor profiles > > Feb 08 09:21:08 apparmor.systemd[918]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/librewolf at line 3: Could not open 'abi/4.0': No such file or directory > > Feb 08 09:21:08 apparmor.systemd[1003]: AppArmor parser error for /etc/apparmor.d/librewolf in profile /etc/apparmor.d/librewolf at line 3: Could not open 'abi/4.0': No such file or directory > > Feb 08 09:21:08 apparmor.systemd[905]: Error: At least one profile failed to load > > Feb 08 09:21:07 systemd[1]: Starting apparmor.service - Load AppArmor profiles... > > Feb 08 09:21:08 systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE > > Feb 08 09:21:08 systemd[1]: apparmor.service: Failed with result 'exit-code'. > > Feb 08 09:21:08 systemd[1]: Failed to start apparmor.service - Load AppArmor profiles. > > Thanks for taking a look at this and if there is any additional information that I can provide, let me know. This is because Debian 12 is stuck on AppArmor 3. https://codeberg.org/librewolf/bsys6/pulls/29 adds a check if AppArmor 4 is supported and otherwise removes the AppArmor file.