Same problem, can't print over network. USB printer is on gutsy Dell Dimension with HPLIP driver and works fine locally but dual-boot Dell Inspiron 500m laptop XP/gutsy and another dual-boot Acer Win2k/gutsy can't print from either OS using SAMBA/CUPS. When I set it up and check accessibility, printer installer reports that printer is accessible, job gets queued, printing starts but then stalls. It's then impossible to cancel the job - even restarting cups on the server doesn't clear the job. I have to reinstall the printer on the server to get it working even locally again.
dmesg on Dell laptop: [ 230.780000] audit(1202646801.294:3): type=1503 operation="inode_permission" requested_mask="a" denied_mask="a" name="/dev/tty" pid=4666 profile="/usr/sbin/cupsd" on Dell Dimension where printer is installed: dmesg: [146446.790557] audit(1202650477.701:5): type=1503 operation="inode_permission" requested_mask="a" denied_mask="a" name="/dev/tty" pid=16096 profile="/usr/sbin/cupsd" cups error log: E [10/Feb/2008:13:21:09 +0000] Resume-Printer: Unauthorized E [10/Feb/2008:13:21:10 +0000] Pause-Printer: Unauthorized var/log/syslog: output of /var/log/syslog: Feb 10 13:20:49 puter cupsd[15877]: *** WARNING *** The programme 'cupsd' uses the Apple Bonjour compatiblity layer of Avahi. Feb 10 13:20:49 puter cupsd[15877]: *** WARNING *** Please fix your application to use the native API of Avahi! Feb 10 13:20:49 puter cupsd[15877]: *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=cupsd> Feb 10 13:20:49 puter kernel: [145619.432996] audit(1202649649.105:4): type=1503 operation="inode_permission" requested_mask="a" denied_mask="a" name="/dev/tty" pid=15877 profile="/usr/sbin/cupsd" tried sudo aa-complain cupsd but it didn't resolve it. No idea how I might 'fix my application' for the native API of Avahi or whether this would help? Try *which* package in gutsy-proposed? HPLIP? -- AppArmor profile breaks printing with hplip https://bugs.launchpad.net/bugs/131470 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
