dmesg reports: apparmor="DENIED" for cupsd
Bug #1031583 reported by
Kaulbach
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
Fix Released
|
Low
|
Jamie Strandboge |
Bug Description
Ubuntu quantal (development branch) , KDE 4.9.0
Upgraded continuously since Hardy Heron
64 bit 3.5.0-6-generic
apparmor version: 2.8.0-0ubuntu1
Changed in cups (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
importance: | Undecided → Low |
status: | Confirmed → In Progress |
To post a comment you must log in.
The specific rejection is:
[ 351.624338] type=1400 audit(134377557 1.688:27) : apparmor="DENIED" operation="capable" parent=1 profile= "/usr/sbin/ cupsd" pid=1361 comm="cupsd" pid=1361 comm="cupsd" capability=36 capname= "block_ suspend"
This capability was added in http:// repo.or. cz/w/linux- 2.6.git/ commit/ d9914cf66181b8a a0929775f5c6f67 5c6ebc3eb5 and governs the ability to block suspending (currently via the EPOLLWAKEUP flag). Reading the the discussion thread about the feature at http:// thread. gmane.org/ gmane.linux. kernel/ 1249726/ focus=1288990 , it's not entirely clear to me that cups needs this capability.
The cups apparmor profile is maintained in the cups package; moving there.