Description of problem: Driver for Canon Pixma Pro 9000 Mk ii does not print at all. In the log files there are references to a path, "/System/Library", that does not exists in Linux. Version-Release number of selected component (if applicable): cups-1.5.0-22.fc16.i686 How reproducible: every time Steps to Reproduce: 1.Print test page. 2. 3. Actual results: it feeds a blank page through. Expected results: Test page printed Additional info: portion of error_log for /var/log/cups W [30/Dec/2011:20:03:29 -0500] failed to find device: cups-Photosmart_C6200_series__DECC96_ W [02/Jan/2012:10:56:37 -0500] failed to find device: cups-HP-Photosmart-C6200-series W [02/Jan/2012:10:56:41 -0500] failed to find device: cups-Pro9000II_series W [02/Jan/2012:10:56:41 -0500] no access to /System/Library/ColorSync/Profiles/sRGB Profile.icc W [02/Jan/2012:10:56:41 -0500] no access to /System/Library/ColorSync/Profiles/sRGB Profile.icc W [02/Jan/2012:10:56:41 -0500] no access to /System/Library/ColorSync/Profiles/Generic CMYK Profile.icc W [02/Jan/2012:10:56:41 -0500] failed to find device: cups-AdobePDF9 W [02/Jan/2012:10:56:41 -0500] failed to find device: cups-HP_LaserJet_CM1415fnw__C23EBD_ W [02/Jan/2012:10:56:41 -0500] failed to find device: cups-hp_psc_1310_series W [02/Jan/2012:10:56:41 -0500] failed to find device: cups-Officejet_Pro_L7600__172_16_1_11___Fax_ W [02/Jan/2012:10:56:41 -0500] failed to find device: cups-Photosmart_C6200_series__DECC96_.1.13 E [02/Jan/2012:10:56:41 -0500] Unable to bind socket for address [v1.::1]:631 - Address already in use. W [02/Jan/2012:10:58:11 -0500] no access to /System/Library/ColorSync/Profil W [02/Jan/2012:10:58:11 -0500] no access to /System/Library/ColorSync/Profil W [02/Jan/2012:10:58:11 -0500] no access to /System/Library/ColorSync/Profilc W [02/Jan/2012:10:58:11 -0500] failed to CreateProfile: org.freedesktop.Colofile id 'Pro9000II_series-Gray..' already exists W [02/Jan/2012:10:58:11 -0500] failed to CreateProfile: org.freedesktop.Colofile id 'Pro9000II_series-RGB..' already exists W [02/Jan/2012:10:58:11 -0500] failed to CreateDevice: org.freedesktop.Colorce id 'cups-Pro9000II_series' already exists W [02/Jan/2012:10:58:11 -0500] no access to /System/Library/ColorSync/Profil W [02/Jan/2012:10:58:11 -0500] no access to /System/Library/ColorSync/Profil W [02/Jan/2012:10:58:11 -0500] no access to /System/Library/ColorSync/Profilc W [02/Jan/2012:10:58:11 -0500] failed to CreateProfile: org.freedesktop.Colofile id 'Pro9000II_series-Gray..' already exists W [02/Jan/2012:10:58:11 -0500] failed to CreateProfile: org.freedesktop.Colofile id 'Pro9000II_series-RGB..' already exists W [02/Jan/2012:10:58:11 -0500] failed to CreateDevice: org.freedesktop.Colorce id 'cups-Pro9000II_series' already exists W [02/Jan/2012:11:01:58 -0500] failed to find device: cups-AdobePDF9 W [02/Jan/2012:11:01:58 -0500] failed to find device: cups-HP_LaserJet_CM141 W [02/Jan/2012:11:01:58 -0500] failed to find device: cups-hp_psc_1310_serie W [02/Jan/2012:11:01:58 -0500] failed to find device: cups-Officejet_Pro_L76 W [02/Jan/2012:11:01:58 -0500] failed to find device: cups-Photosmart_C6200_13 W [02/Jan/2012:11:09:08 -0500] failed to find device: cups-HP_OFFICEJET_REFL W [02/Jan/2012:11:09:09 -0500] failed to find device: cups-hp_psc_1300_serie W [02/Jan/2012:11:09:10 -0500] failed to find device: cups-hp_psc_1300_serie W [02/Jan/2012:11:09:33 -0500] failed to find device: cups-HP_OFFICEJET_REFL W [02/Jan/2012:11:09:33 -0500] failed to find device: cups-hp_psc_1300_serie W [02/Jan/2012:11:09:33 -0500] failed to find device: cups-hp_psc_1300_serie
The quoted messages are not relevant to the problem. The "no access to" and "failed to" messages are about ICC profiles, which do not affect the ability to print (just the colour correctness). The "Unable to bind" message doesn't seem to be causing the problem either, as you are able to get CUPS to tell the printer to do something, even if just feeding through a sheet. Please run the printing troubleshooter: https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter You should end up with a troubleshoot.txt file. Please attach that here using the "Add an attachment" link above.
Created attachment 550583 [details] Troubleshooter output
Strangely, although the troubleshooter thinks you enabled debug logging, it doesn't appear in the error_log file. Please enable it manually like this: su -c 'cupsctl --debug-logging' Print your file again, then turn off debug logging again: su -c 'cupsctl --no-debug-logging' Finally, attach /var/log/cups/error_log. Thanks.
Support for Canon PIXMA Pro9000 Mk.II was added in gutenprint-5.2.7 and has been marked as EXPERIMENTAL, meaning that it had actually not been tested.
The foomatic driver for this printer doesn't work due to https://bugs.linuxfoundation.org/show_bug.cgi?id=982
(In reply to comment #3) > Strangely, although the troubleshooter thinks you enabled debug logging, it > doesn't appear in the error_log file. > > Please enable it manually like this: > > su -c 'cupsctl --debug-logging' > > Print your file again, then turn off debug logging again: > > su -c 'cupsctl --no-debug-logging' > > Finally, attach /var/log/cups/error_log. Thanks. In light of comment #5 do you still need the above steps?
Yes, it would still be useful. Note: you use gutenprint driver, not foomatic. I should have probably make the comment #5 private as it was info mainly for Tim and me.
Created attachment 550793 [details] attached error_log with debug enabled Try to print just 2 simple lines of text.
(In reply to comment #8) > Try to print just 2 simple lines of text. D [04/Jan/2012:21:06:19 -0500] [Job 81] Request file type is application/pdf. seems more like PDF to me. Anyway, I can't find anything strange in the error_log. Everything, maybe except this line: D [04/Jan/2012:21:06:19 -0500] Get-Printer-Attributes client-error-not-found: The printer or class does not exist. looks good. See: D [04/Jan/2012:21:06:22 -0500] [Job 81] Gutenprint: Done printing page 1 I [04/Jan/2012:21:06:22 -0500] [Job 81] Rendering completed D [04/Jan/2012:21:06:22 -0500] PID 10793 (/usr/lib/cups/filter/gstoraster) exited with no errors. D [04/Jan/2012:21:06:22 -0500] [Job 81] Gutenprint: Ending job D [04/Jan/2012:21:06:22 -0500] [Job 81] Gutenprint: Printed total 41116 bytes D [04/Jan/2012:21:06:22 -0500] [Job 81] Gutenprint: Used 2.570 seconds user, 0.200 seconds system, 3.125 seconds elapsed D [04/Jan/2012:21:06:22 -0500] PID 10794 (/usr/lib/cups/filter/rastertogutenprint.5.2) exited with no errors. D [04/Jan/2012:21:06:22 -0500] PID 10795 (/usr/lib/cups/backend/usb) exited with no errors. I have no idea what else we could do here.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.