Your message dated Thu, 12 Feb 2026 19:19:15 +0000
with message-id <[email protected]>
and subject line Bug#1121917: fixed in apparmor 4.1.6-2
has caused the Debian Bug report #1121917,
regarding apparmor: Kernel version out of sync / doesn't conform to protocol
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1121917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121917
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apparmor
Version: 4.1.0-1+b1
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
recently, some profiles (not all) fail to load because they don't "confirm to
protocol". Happens both during boot and on manual reload. Couldn't reliably
track down specific lines of these files that might cause it.
The upstream FAQ suggests that the userland tools might've been build against
kernel headers that are newer than the kernel. This is a sid machine however,
currently 6.17.9-deb14, so probably(?) not the issue.
The version of apparmor_parser that is currently in Debian-stable shows the
same problem.
I'm not sure what kind of other info I can provide currently
Thank you
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.17.9+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages apparmor depends on:
ii debconf [debconf-2.0] 1.5.91
ii libc6 2.42-4
apparmor recommends no packages.
Versions of packages apparmor suggests:
pn apparmor-profiles-extra <none>
ii apparmor-utils 4.1.0-1
-- Configuration Files:
/etc/apparmor.d/firefox changed [not included]
/etc/apparmor.d/tunables/home changed [not included]
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: apparmor
Source-Version: 4.1.6-2
Done: intrigeri <[email protected]>
We believe that the bug you reported is fixed in the latest version of
apparmor, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
intrigeri <[email protected]> (supplier of updated apparmor package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 12 Feb 2026 15:59:37 +0000
Source: apparmor
Architecture: source
Version: 4.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian AppArmor Team <[email protected]>
Changed-By: intrigeri <[email protected]>
Closes: 1121917
Changes:
apparmor (4.1.6-2) unstable; urgency=medium
.
* Drop non-Linux build support
* Fix file executability mismatch between Git and dpkg-source -x
.
apparmor (4.1.6-1) unstable; urgency=medium
.
[ intrigeri ]
* Import upstream release 4.1.6 (Closes: #1121917)
* Migrate to the workflow documented in dgit-maint-merge(7)
- Switch to 1.0 source format
- Apply Debian patches
- Delete obsolete Ubuntu patches
- Tell git-debpush that this package is non-native
- debian/watch: monitor Git tags, not tarballs
- Adjust Lintian overrides to new packaging workflow
* Improve README.source
- Drop useless git fetch verbosity
- Make remote name consistent
- Use long option name, for clarity
- Drop obsolete option
- Stop using gbp-dch snapshots
- Lint shell pipelines
* Remove unused upstream signing key
* Drop obsolete Lintian override
.
[ Ryan Lee ]
* debian/rules: remove __pycache__ directory generated by
python3-libapparmor build
* debian/python3-libapparmor.install: include new location of Python
_LibAppArmor*.so libraries
Checksums-Sha1:
01e9f84b56eca63967b06f4709d3f108da93bc30 3709 apparmor_4.1.6-2.dsc
2e0680cd4b667fa5b0073ec444e17a1857e23e9e 105992 apparmor_4.1.6-2.diff.gz
121387aeeeca4898335427bb7de3c53b1abc12af 8738700 apparmor_4.1.6-2.git.tar.xz
8645e25267be4a4d3b45738978c41324fd5e4736 17298
apparmor_4.1.6-2_source.buildinfo
64d0bea3dc8f86bcbe68a11ce770ecf9170051ab 7156274 apparmor_4.1.6.orig.tar.gz
Checksums-Sha256:
c1ef26d5fb798230bb6e04591182e7f4ec476638c723753c64a3be77a7854e1a 3709
apparmor_4.1.6-2.dsc
50a1a124826a4959fca84f7a10c2ee8af7e106dca6b0a71b81a65f6c90aaa2a6 105992
apparmor_4.1.6-2.diff.gz
e40b5af16bbc45e28578baf3f61017158da524d856c071c156c2901892686335 8738700
apparmor_4.1.6-2.git.tar.xz
e469e9d7f7d9b133c34a0f0358e4f0c84b2cc432b82969a8457a06a522c25f7b 17298
apparmor_4.1.6-2_source.buildinfo
751be319c814eaee12c8378d32911afa48356026c250983483f0c78b1f8b8d8c 7156274
apparmor_4.1.6.orig.tar.gz
Files:
112e1504b9e663d266ac6b7c8ffe1579 3709 admin optional apparmor_4.1.6-2.dsc
a050a1c636f40270a744b5fe1228c97a 105992 admin optional apparmor_4.1.6-2.diff.gz
e095f0b6c9f151510fbd0285a219cb16 8738700 admin None apparmor_4.1.6-2.git.tar.xz
35a09c6e120df93a67c1e244a275d44f 17298 admin optional
apparmor_4.1.6-2_source.buildinfo
ab08300564c257477b5acee4c2c256ea 7156274 admin optional
apparmor_4.1.6.orig.tar.gz
Git-Tag-Info: tag=4717bbd84364f320cb770168145d1065d76e938b
fp=61b4345c66efc790fed859c69f8fa72f6954c3a3
Git-Tag-Tagger: intrigeri <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmmOIn8ACgkQYG0ITkaD
wHmHew//QyMUGgiI0nPcryzBQ3pSo3kiM696kKAoLiryeviipioIJZBCAg32J5g+
ikF4OQ/oGrtWAARWNLGhg8CTAKrkWH16HMW021v8wEY6gmvxZvlBXwzTifeBvsUO
e8UWKaLZ1jGM4WhYQ0kDO8sBmUUtMsiVy4N3LQ/f7sFcDB233/P5vLL00KXvsEpw
Fy6RmR7buvw2a7As4OydK8FYhXn8/hHy1ppSSwNtMhZLPnPeR7DeyGbtH2clpXoo
f8QWCvFXrnCJka79mU7c5cDUw5TmxeKWYYZcQx4l24wk+ihWzohmfPuWiGPr6ACM
F9FpINVxSHAyWAA9YfziPyzbJNd9hQf/7oOMtnIQhqqwAB9dc/LLuy+alO3AD5k+
djsSkf8P1JehP1mfc/Ie5MmrJUI2S4ihtSSxUY+cnzuNY6o0sAsOjDfKNStb/EcF
MF4avyv4FEXa8lv/HJdGMbH1JIFy7FSx+sgL3/A0+YZLBMJ2x42Cr2WBNwNXvC0n
8ezTNnwefKKYqvVDRu5TalBcHXhznt+WoFClqx+N1qT5/oiikUg1aT/H9oEQgZel
0RpTeW6vzZramqxJbaCxseg6RZ8nh1qDwTCpzMd6liKA/HCs/eF9VW0Dxi32aGHt
dsMAaF8W0Dcvm+UE7xdPRwJoetzb1WsrGd9bcpCKpL53g5gUSVY=
=v68I
-----END PGP SIGNATURE-----
pgp5ydkHySuZn.pgp
Description: PGP signature
--- End Message ---
