After some discussion on IRC it turned out that Dustin Kirkland has
linked /tmp to /dev/shm (shared memory, something like a RAM disk).
AppArmor is blocking the access to /dev/shm as it is not explicitly
allowed in /etc/apparmor.d/usr.sbin.cupsd (See below). So there is no
bug in upstream CUPS or in our AppArmor configuration.
The new foomatic-rip works around the problem by trying several
temporary file locations. Especially it starts with CUPS' own temporary
file directory, usually
/var/spool/cups/tmp
So you either need to install the new foomatic-filters package or edit
your /etc/apparmor.d/usr.sbin.cupsd giving the same permissions to
/dev/shm as to /tmp.
Closing CUPS task.
----------------------------
/var/log/syslog:
Oct 6 12:38:52 t61p kernel: [ 9486.969802] type=1503
audit(1223314732.763:5): operation="inode_create" requested_mask="a::"
denied_mask="a::" fsuid=7 name="/dev/shm/foomatic-kzhZaS" pid=14140
profile="/usr/sbin/cupsd"
/var/log/messages:
Oct 6 12:38:52 t61p kernel: [ 9486.969802] type=1503
audit(1223314732.763:5): operation="inode_create" requested_mask="a::"
denied_mask="a::" fsuid=7 name="/dev/shm/foomatic-kzhZaS" pid=14140
profile="/usr/sbin/cupsd"
** Changed in: cups (Ubuntu)
Status: Triaged => Invalid
--
P2POutputStream: write error
https://bugs.launchpad.net/bugs/276573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
