[nylug-talk] Ubuntu: Not Connected? Printer may not be connected

[Chris Knadle]

A friend passed along further info on the problem.

On Tuesday 01 January 2008, pachai1 at optonline.net wrote:
> /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/usblp.c: usblp0:
> removed [106913.976000] audit(1199162454.259:24):  type=1503
> operation="inode_permission" requested_mask="rw" denied_mask="rw"
> name="/dev/tty" pid=10268 profile="/usr/sbin/cupsd" [106913.992000]
> audit(1199162454.259:25):  type=1503 operation="inode_permission"
> requested_mask="rw" denied_mask="rw" name="/dev/tty" pid=10271
> profile="/usr/sbin/cupsd"
>
> [135563.240000] audit(1199191103.809:26):  type=1503
> operation="inode_permission" requested_mask="rw" denied_mask="rw"
> name="/dev/tty" pid=13004 profile="/usr/sbin/cupsd" [135563.288000]
> audit(1199191103.809:27):  type=1503 operation="inode_permission"
> requested_mask="rw" denied_mask="rw" name="/dev/tty" pid=13007
> profile="/usr/sbin/cupsd"

   Turns out these entries are relevant; as Kevin mentioned Ubuntu now runs 
AppArmor, and unfortunately at this point AppArmor has some issues with CUPS.

   Below is what Joe from MHVLUG [Joe Apuzzo <japuzzo at gmail.com> ("Gnu-Joe")] 
passed along.  The first page contains what looks like a workaround:

=-=-=-=-=-=-=

from http://www.ubuntu.com/getubuntu/releasenotes/710
Printing with AppArmor

Ubuntu 7.10 introduces an additional security layer called AppArmor,
whose support for CUPS printing is not yet complete. This will result in
printing failures in certain corner cases described below. The
workaround in each of these cases is to disable the AppArmor CUPS
profile by running sudo aa-complain cupsd. AppArmor support may be
re-enabled by running sudo aa-enforce cupsd.

* Printing to bluetooth printers does not work with AppArmor enabled.
Bug #147800
* Many third-party printer drivers (especially from printer
manufacturers) do not work. Bug #152537

https://help.ubuntu.com/community/AppArmor

=-=-=-=-=-=-=

   Some of this is to be expected; Fedora had trouble with their first couple 
of relases with SELinux active, too.

   -- Chris

-- 

Chris Knadle
Chris.Knadle at coredump.us