Your message dated Sun, 30 Mar 2025 13:49:17 +0000
with message-id <[email protected]>
and subject line Bug#1100515: fixed in ejabberd 24.12-3
has caused the Debian Bug report #1100515,
regarding ejabberd: apparmor profile breaks apparmor currently
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.)


-- 
1100515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100515
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ejabberd
Version: 24.12-2
Severity: important

        My apparmor service was breaking just now after an unstable
upgrade due to ejabberd it seems:
---
# systemctl status apparmor.service
× apparmor.service - Load AppArmor profiles
     Loaded: loaded (/usr/lib/systemd/system/apparmor.service; enabled; preset: 
enabled)
     Active: failed (Result: exit-code) since Fri 2025-03-14 11:19:55 PDT; 3min 
36s ago
 Invocation: da1d076348064bab8de71653da20c45c
       Docs: man:apparmor(7)
             https://gitlab.com/apparmor/apparmor/wikis/home/
    Process: 117596 ExecStart=/lib/apparmor/apparmor.systemd reload 
(code=exited, status=1/FAILURE)
   Main PID: 117596 (code=exited, status=1/FAILURE)
   Mem peak: 5.8M
        CPU: 265ms

Mar 14 11:19:55 king.bitgnome.net systemd[1]: Starting apparmor.service - Load 
AppArmor profiles...
Mar 14 11:19:55 king.bitgnome.net apparmor.systemd[117596]: Restarting AppArmor
Mar 14 11:19:55 king.bitgnome.net apparmor.systemd[117596]: Reloading AppArmor 
profiles
Mar 14 11:19:55 king.bitgnome.net apparmor.systemd[117699]: profile has merged 
rule with conflicting x modifiers
Mar 14 11:19:55 king.bitgnome.net apparmor.systemd[117699]: ERROR processing 
regexs for profile su, failed to load
Mar 14 11:19:55 king.bitgnome.net apparmor.systemd[117596]: Error: At least one 
profile failed to load
Mar 14 11:19:55 king.bitgnome.net systemd[1]: apparmor.service: Main process 
exited, code=exited, status=1/FAILURE
Mar 14 11:19:55 king.bitgnome.net systemd[1]: apparmor.service: Failed with 
result 'exit-code'.
Mar 14 11:19:55 king.bitgnome.net systemd[1]: Failed to start apparmor.service 
- Load AppArmor profiles.

# cd /etc/apparmor.d; grep -r 'su '
usr.sbin.ejabberdctl:   profile su flags=(attach_disconnected) {
---

        After removing ejabberd entirely, apparmor was happy again.  I
figured I'd at least report this since the number of folks actively
running ejabberd at this point is probably fairly small.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.17-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 ejabberd depends on:
ii  adduser                     3.137
ii  debconf [debconf-2.0]       1.5.89
ii  erlang-asn1                 1:27.2.4+dfsg-1
ii  erlang-base [erlang-abi]    1:27.2.4+dfsg-1
ii  erlang-base64url            1.0.1-8+b1
ii  erlang-crypto               1:27.2.4+dfsg-1
ii  erlang-goldrush             0.2.0-9+b1
ii  erlang-idna                 6.1.1-5+b1
ii  erlang-inets                1:27.2.4+dfsg-1
ii  erlang-jiffy                1.1.2-1+b1
ii  erlang-jose                 1.11.10-1+b1
ii  erlang-lager                3.9.2-3+b1
ii  erlang-mnesia               1:27.2.4+dfsg-1
ii  erlang-odbc                 1:27.2.4+dfsg-1
ii  erlang-os-mon               1:27.2.4+dfsg-1
ii  erlang-p1-acme              1.0.25-1
ii  erlang-p1-cache-tab         1.0.31-2
ii  erlang-p1-eimp              1.0.23-4
ii  erlang-p1-mqtree            1.0.17-2
ii  erlang-p1-pkix              1.0.10-2
ii  erlang-p1-stringprep        1.0.30-2
ii  erlang-p1-stun              1.2.15-1
ii  erlang-p1-tls               1.1.22-1
ii  erlang-p1-utils             1.0.26-2
ii  erlang-p1-xml               1.1.55-1
ii  erlang-p1-xmpp              1.9.4-1
ii  erlang-p1-yaml              1.0.37-2
ii  erlang-p1-yconf             1.0.17-1
ii  erlang-p1-zlib              1.0.13-2
ii  erlang-public-key           1:27.2.4+dfsg-1
ii  erlang-ssl                  1:27.2.4+dfsg-1
ii  erlang-syntax-tools         1:27.2.4+dfsg-1
ii  erlang-unicode-util-compat  0.7.0-5+b1
ii  erlang-xmerl                1:27.2.4+dfsg-1
ii  init-system-helpers         1.68
ii  openssl                     3.4.1-1
ii  ucf                         3.0050

ejabberd recommends no packages.

Versions of packages ejabberd suggests:
ii  apparmor             4.1.0~beta5-3
ii  apparmor-utils       4.1.0~beta5-3
pn  ejabberd-contrib     <none>
pn  erlang-luerl         <none>
pn  erlang-p1-mysql      <none>
pn  erlang-p1-oauth2     <none>
pn  erlang-p1-pam        <none>
pn  erlang-p1-pgsql      <none>
pn  erlang-p1-sip        <none>
pn  erlang-p1-sqlite3    <none>
pn  erlang-redis-client  <none>
pn  imagemagick          <none>
pn  libunix-syslog-perl  <none>
pn  yamllint             <none>

--- End Message ---
--- Begin Message ---
Source: ejabberd
Source-Version: 24.12-3
Done: Philipp Huebner <[email protected]>

We believe that the bug you reported is fixed in the latest version of
ejabberd, 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.
Philipp Huebner <[email protected]> (supplier of updated ejabberd 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: Sun, 30 Mar 2025 15:24:44 +0200
Source: ejabberd
Architecture: source
Version: 24.12-3
Distribution: unstable
Urgency: medium
Maintainer: Ejabberd Packaging Team <[email protected]>
Changed-By: Philipp Huebner <[email protected]>
Closes: 1100515
Changes:
 ejabberd (24.12-3) unstable; urgency=medium
 .
   [ Carles Pina i Estany ]
   * Added po-debconf Catalan translation
 .
   [ Philipp Huebner ]
   * Dropped unmaintained AppArmor profile as it breaks AppArmor 4
     (Closes: #1100515)
   * Updated FSF address in debian/copyright
   * Updated Standards-Version: 4.7.2 (no changes needed)
Checksums-Sha1:
 b15dc9072e613269a9d76d7afe49a5f43ff61535 3022 ejabberd_24.12-3.dsc
 7c13d0204dc90dab7c9d221ee4e9d1368b41bc3b 72412 ejabberd_24.12-3.debian.tar.xz
 9e0b16b974532ac7fd0b09b62fd06bcf90dcce4c 15403 ejabberd_24.12-3_amd64.buildinfo
Checksums-Sha256:
 a61a233dfae110da8a5ff48b5a9c4191655803c3c958f9c2b867a1706b1df784 3022 
ejabberd_24.12-3.dsc
 abdee2482652124b5b21a13cb47b33cdf84dfc2df2fb4ab89f68e8fa4c96aff6 72412 
ejabberd_24.12-3.debian.tar.xz
 a79dd03c318842afbf3bcd0f3df0917594cb1dd1637673061138ac3f49ab9385 15403 
ejabberd_24.12-3_amd64.buildinfo
Files:
 967e5adc9abdc9a14c7df559f393443b 3022 net optional ejabberd_24.12-3.dsc
 3c4681a1134b137e00a0760e0cea1b46 72412 net optional 
ejabberd_24.12-3.debian.tar.xz
 9392904cc0b265395a5c30591398bee1 15403 net optional 
ejabberd_24.12-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJJBAEBCgAzFiEECEGLvkRyDy26xQXsunokltrkDRwFAmfpSbwVHGRlYmFsYW5j
ZUBkZWJpYW4ub3JnAAoJELp6JJba5A0cr8QQANaVZ7mxXacT4Ni0q76SbwNx8HKW
DHpWWadQCn3YT+S3ScB2lJbLrVS5b9WrHH87RS+NZRxYBFGZgSAUU9nCKX7ORLuX
O5HZIEWBmSaR1Zw1Rr1Xv5owWZrwcbccibYGvGJ0BMj+Yfx95JeScgRnEv/VD6nO
Qc3ScNC/RfTOqZAJB90gEc1nm2WqdqLKkKQiV09mbEVUlMq871BQogHMNrKw+sla
2vygE2AsrSKFdUPNUYey1vhmIzPTqk72q94WkxahOetv5Doqd0h4fdx7/qlmu/zh
MMxuwhZXzqA8/srkmePeXpRm1tzUzpqsxu+Z+aWq6F+yuP/jt8EtjvRjeAjZ5QqH
/UTA3rL68+JY0MVNafcea5feKFNfbcpZJbw7I0M3Du6dIbtZpFMoL4BNeqs+hLcA
uoRuRGJufuQ766Kzxm7r+B+dTgeSDDFl4nBc2Gg9ziKxMBy8O4EE6IamKpey8gW9
UPObBpSHFpye+TCwH9zeS3kecVAJSsXOXaP4OaUD2Sn7GoWZFuSbGupsfRdv803e
yySfuMqlbzsq8073piFY8FMxKVWkCyc1SFa5ZqmWv8wBFg/9y6SLFofm/FNKV+vW
GR5OUEzaQX7xhPC1IzBnFViMdvxyW0Mo2P1BOy9qL832b/yJp3UW58IZToqFzUxz
AL8NKJuOgxD9K1r8
=A7qY
-----END PGP SIGNATURE-----

Attachment: pgpxxBcfRJKxC.pgp
Description: PGP signature


--- End Message ---

Reply via email to