Your message dated Sun, 4 Jun 2023 14:35:38 +0100
with message-id <04062023142947.e4eddfc00...@desktop.copernicus.org.uk>
and subject line Re: Bug#970327: cups: make apparmor abort at startup
has caused the Debian Bug report #970327,
regarding cups: make apparmor abort at startup
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 ow...@bugs.debian.org
immediately.)
--
970327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cups
Version: 2.2.10-6+deb10u3
Severity: normal
Dear Maintainer,
When looking for apparmor "denied" messages I found that apparmor is not
running ant cannot start as an error lies in the usr.bin.cups file. When I use
the simple parser :
apparmor_parser -vQ usr.sbin.cupsd
I get the message :
AppArmor parser error for usr.sbin.cupsd in usr.sbin.cupsd at line 173: syntax
error, unexpected TOK_CLOSE, expecting TOK_END_OF_RULE
If I try to start apparmor through systemctl I get an abort, as "normal"
nothing to see in systemctl status apparmor, except that something get wrong
...
I remove "usr.bin.cupsd" from /etc/apparmor.d and all is clear ...
systemctl restart apparmor is clean and apparmor is running.
Regards
JP P
-- System Information:
Debian Release: 10.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cups depends on:
ii cups-client 2.2.10-6+deb10u3
ii cups-common 2.2.10-6+deb10u3
ii cups-core-drivers 2.2.10-6+deb10u3
ii cups-daemon 2.2.10-6+deb10u3
ii cups-filters 1.21.6-5
ii cups-ppdc 2.2.10-6+deb10u3
ii cups-server-common 2.2.10-6+deb10u3
ii debconf [debconf-2.0] 1.5.71
ii ghostscript 9.27~dfsg-2+deb10u4
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libc6 2.28-10
ii libcups2 2.2.10-6+deb10u3
ii libcupsimage2 2.2.10-6+deb10u3
ii libgcc1 1:8.3.0-6
ii libstdc++6 8.3.0-6
ii libusb-1.0-0 2:1.0.22-2
ii poppler-utils 0.71.0-5
ii procps 2:3.3.15-2
Versions of packages cups recommends:
pn avahi-daemon <none>
ii colord 1.4.3-4
ii cups-filters [ghostscript-cups] 1.21.6-5
ii printer-driver-gutenprint 5.3.1-7
Versions of packages cups suggests:
ii cups-bsd 2.2.10-6+deb10u3
pn foomatic-db-compressed-ppds | foomatic-db <none>
pn hplip <none>
ii printer-driver-cups-pdf [cups-pdf] 3.0.1-5
pn printer-driver-hpcups <none>
ii smbclient 2:4.9.5+dfsg-5+deb10u1
ii udev 246.4-1~bpo10+1
-- debconf information:
cupsys/backend: lpd, socket, usb, snmp, dnssd
cupsys/raw-print: true
--- End Message ---
--- Begin Message ---
No further interaction from the issue submitter. Hence closing.
Cheers,
Brian.
--- End Message ---
