[Gutsy Tribe4] Can not found Canon printers

Bug #131521 reported by Patrice Vetsel
6
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Fix Released
High
Martin Pitt

Bug Description

Binary package hint: cupsys

May be it's a foomatic problem as foomatic-gui have https://bugs.launchpad.net/ubuntu/+source/foomatic-gui/+bug/115612

WIth cupsys web interface, or system-config-printer i do not have any Canon printers available.
I found this bug when i was using hal-cups-utils that configure my Canon iP3000 but with a wrong driver, so going to choose one, i can not found CANON drivers.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Can you do "lpinfo -m | grep -i canon"?

Changed in cupsys:
status: New → Incomplete
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

kagou@satori:~$ lpinfo -m | grep -i canon
kagou@satori:~$

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

I'v this in /var/log/syslog

Aug 10 13:42:26 satori kernel: [ 7887.156000] audit(1186746146.905:69): REJECTING m access to /usr/lib/perl/5.8.8/auto/Encode/Encode.so (foomatic(7062) profile /usr/sbin/cupsd active /usr/sbin/cupsd)
Aug 10 13:42:27 satori kernel: [ 7887.276000] audit(1186746146.905:70): REJECTING m access to /usr/lib/gutenprint/5.0.1/modules/color-traditional.so (gutenprint.5.0(7064) profile /usr/sbin/cupsd active /usr/sbin/cupsd)
Aug 10 13:42:27 satori kernel: [ 7887.276000] audit(1186746146.905:71): REJECTING m access to /usr/lib/gutenprint/5.0.1/modules/print-canon.so (gutenprint.5.0(7064) profile /usr/sbin/cupsd active /usr/sbin/cupsd)
Aug 10 13:42:27 satori kernel: [ 7887.276000] audit(1186746146.905:72): REJECTING m access to /usr/lib/gutenprint/5.0.1/modules/print-escp2.so (gutenprint.5.0(7064) profile /usr/sbin/cupsd active /usr/sbin/cupsd)
Aug 10 13:42:27 satori kernel: [ 7887.280000] audit(1186746146.905:73): REJECTING m access to /usr/lib/gutenprint/5.0.1/modules/print-lexmark.so (gutenprint.5.0(7064) profile /usr/sbin/cupsd active /usr/sbin/cupsd)
Aug 10 13:42:27 satori kernel: [ 7887.280000] audit(1186746146.905:74): REJECTING m access to /usr/lib/gutenprint/5.0.1/modules/print-olympus.so (gutenprint.5.0(7064) profile /usr/sbin/cupsd active /usr/sbin/cupsd)
Aug 10 13:42:27 satori kernel: [ 7887.280000] audit(1186746146.905:75): REJECTING m access to /usr/lib/gutenprint/5.0.1/modules/print-pcl.so (gutenprint.5.0(7064) profile /usr/sbin/cupsd active /usr/sbin/cupsd)
Aug 10 13:42:27 satori kernel: [ 7887.280000] audit(1186746146.905:76): REJECTING m access to /usr/lib/gutenprint/5.0.1/modules/print-ps.so (gutenprint.5.0(7064) profile /usr/sbin/cupsd active /usr/sbin/cupsd)
Aug 10 13:42:27 satori kernel: [ 7887.284000] audit(1186746146.905:77): REJECTING m access to /usr/lib/gutenprint/5.0.1/modules/print-raw.so (gutenprint.5.0(7064) profile /usr/sbin/cupsd active /usr/sbin/cupsd)

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

/var/log/syslog

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

AppArmor is blocking the libraries needed by the PPD generators /usr/lib/cups/driver/foomatic and /usr/lib/cups/driver/gutenprint. This prevents all Canon and many other PPDs from getting listed.

Changed in cupsys:
assignee: nobody → pitti
importance: Undecided → High
status: Incomplete → Confirmed
Revision history for this message
fenrig (maregt0) wrote :

Hi, i have this problem too. I tried deleting, reinstalling, removing all cups deb's and gutenprint deb's

Revision history for this message
fenrig (maregt0) wrote :

I found a solution:

Do
sudo aa-complain cupsd
to deactivate the AppArmor protection of CUPS temprarily, then you should be able to print again.
(from bug #131470)
https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/131470

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

Last cupsys upgrade seems to solve this bug :)

Changed in cupsys:
status: Confirmed → Fix Released
Revision history for this message
zcat (zcat) wrote :

Not for me.

zcat@fluffy:~$ tail /var/log/cups/error_log
E [28/Oct/2007:22:48:40 +0000] PID 7241 (/usr/lib/cups/filter/foomatic-rip) stopped with status 3!
E [28/Oct/2007:22:48:42 +0000] [Job 6] Job stopped due to filter errors.
E [28/Oct/2007:22:49:57 +0000] PID 7287 (/usr/lib/cups/filter/foomatic-rip) stopped with status 3!
E [28/Oct/2007:22:49:59 +0000] [Job 7] Job stopped due to filter errors.
E [28/Oct/2007:22:51:07 +0000] PID 7344 (/usr/lib/cups/filter/foomatic-rip) stopped with status 3!

end of dmesg:
[ 2332.932189] audit(1193612374.712:26): type=1502 operation="inode_permission" requested_mask="rw" denied_mask="rw" name="/dev/tty" pid=7810 profile="/usr/sbin/cupsd"
[ 2333.100171] audit(1193612374.712:27): type=1502 operation="inode_permission" requested_mask="rw" denied_mask="rw" name="/dev/tty" pid=7813 profile="/usr/sbin/cupsd"
[ 2333.230959] audit(1193612375.212:28): type=1502 operation="inode_permission" requested_mask="r" denied_mask="r" name="/etc/pnm2ppa.conf" pid=7817 profile="/usr/sbin/cupsd"

This is on a box that was recently upgraded from feisty, and the printer was working perfectly.
No difference between gnome interface or web localhost:631(?)

Printer doesn't get detected by 'add new printer'

After manually choosing port and printer details, printer immediately moves all jobs to "Stopped"

Same problem happens for every printer I have available, PPT or USB.

sudo aa-complain cupsd has made the problem go away, for now at least.

Let me know if you want any more details.

Revision history for this message
zcat (zcat) wrote :

BTW; why the change from nice friendly gnome-cups-manager to the hideously awful system-config-printer ?!!! It's like something out of Slackware FFS!!

Somebody please change this back, or give me a really good reason why I shouldn't use the old system!

Revision history for this message
mackiecc (tiloem) wrote :

I have exactly the same problem like "zcat". I'm using gutsy with all updates installed and a hp 710c printer. greets mackie

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.