cups-daemon upgrade generates warnings about "rules not enforced"

Bug #1267880 reported by Richard Elkins
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Whenever the trusty cups-daemon package is upgraded, I can see a few warning lines about "rules not enforced". This does not appear to impact the cups operations.

Note that this does not occur in saucy where the cups-daemon version currently is 1.7.0~rc1-0ubuntu5.1.

For example, I just executed the following re-installation of the cups-daemon:

$ sudo apt-get install --reinstall cups-daemon
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 0 B/268 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 220095 files and directories currently installed.)
Preparing to replace cups-daemon 1.7.1-1 (using .../cups-daemon_1.7.1-1_amd64.deb) ...
cups stop/waiting
Unpacking replacement cups-daemon ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Processing triggers for ufw ...
Setting up cups-daemon (1.7.1-1) ...
Warning from /etc/apparmor.d/usr.sbin.cupsd (/etc/apparmor.d/usr.sbin.cupsd line 180): profile /usr/sbin/cupsd dbus rules not enforced
Warning from /etc/apparmor.d/usr.sbin.cupsd (/etc/apparmor.d/usr.sbin.cupsd line 180): profile /usr/lib/cups/backend/cups-pdf network rules not enforced
Warning from /etc/apparmor.d/usr.sbin.cupsd (/etc/apparmor.d/usr.sbin.cupsd line 180): profile /usr/sbin/cupsd network rules not enforced
cups start/running, process 18890

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups-daemon 1.7.1-1
ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
Uname: Linux 3.13.0-1-generic x86_64
ApportVersion: 2.12.7-0ubuntu6
Architecture: amd64
CupsErrorLog:

CurrentDesktop: XFCE
Date: Fri Jan 10 08:34:43 2014
InstallationDate: Installed on 2013-12-13 (27 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131213)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
Papersize: letter
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=0c647a78-7280-4913-8705-85f1aa784f42 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: MUCDT10N.86A.0069.2012.0323.1358
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D2550MUD2
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG73892-600
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrMUCDT10N.86A.0069.2012.0323.1358:bd03/23/2012:svn:pn:pvr:rvnIntelCorporation:rnD2550MUD2:rvrAAG73892-600:cvn:ct3:cvr:

Revision history for this message
Richard Elkins (texadactyl) wrote :
description: updated
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

pitti, did something change with AppArmor in Trusty? Or any other idea?

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

This appears to be a result of booting a non-Ubuntu kernel without the AppArmor compat patches.

Revision history for this message
Richard Elkins (texadactyl) wrote :

Regarding message #3, please see the attached logs. The subject machine is running the latest up-to-date Xubuntu trusty (14.04). There are absolutely no customized alterations to Xubuntu 14.04.

$ uname -a
Linux mudpc 3.13.0-2-generic #17-Ubuntu SMP Fri Jan 10 12:14:30 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l 'appar*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
ii apparmor 2.8.0-0ubuntu37 amd64 User-space parser utility for AppArmor

Revision history for this message
Richard Elkins (texadactyl) wrote :

I just recalled that there was a major upgrade yesterday, including the kernel and several armor files. So, I retried the cups-daemon re-installation and the warnings have disappeared since this upgrade.

Attached is a log of the apt-get upgrade process with the status messages filtered out.

Changed in cups (Ubuntu):
status: New → Fix Released
affects: cups (Ubuntu) → apparmor (Ubuntu)
Revision history for this message
asgard2 (kamp000x) wrote :

same problem if I use xubuntu 13.10 with
3.12.7-031207-generic #201401091657 SMP Thu Jan 9 21:59:37 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.