My current system is 12.1 x86_64/KDE 4.9
I recently purchased a Canon MF3010 Laser all in one.
I downloaded and installed version 2.5 of their ufr2 driver from Canon web site.
Installed driver with YAST, then installed the printer with YAST.
The printer is actually connected to a WinXP print server, shared via Samba.
From Linux, test pages print OK
From Linux LibreOffice text and drawings print well.
From Linux Inkscape complex svg prints OK.
From Linux, any application that will open a pdf file (okular, gimp, Libreoffice imported to .odg) hangs - the print job just sits in CUPS queue.
Same pdf transferred as file to the WinXP box, opens and prints through the Windoze driver. So File is OK, I think. Multiple files have been tried.
I suspect the driver, but am not sure.
I am presently downloading ver 2.4 of the driver to give it a try.
Any other experiences to share?
This seems to be a nice, compact Laser + scanner for around $100US, very fast, when it does work.
There are too many PDFs in life, I have to fix this!
I have seen other threads on this topic concerning PDF printing, so you may want search for those first.
Review the errors (if any) reported in /var/log/cups/error_log ( and share the output here if you need further assistance).
If necessary, you can increase the verbosity of CUPS by editing the ‘LogLevel’ entry in /etc/cups/cupsd.conf, changing it from ‘warn’ to ‘debug’
LogLevel warn
Great idea.
I looked in /var/log/cups and there was just a bunch of mostly old stuff, and nothing appeared useful.
Cleaned up old info and ran a controlled experiment.
The only log showing any action is /var/log/cups/access_log
I annotated it below:
Here I opened a LibOff spreadsheet and printed it - with Good results
localhost - - [08/Sep/2012:19:30:06 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 255 Create-Job successful-ok
localhost - - [08/Sep/2012:19:30:06 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 56228 Send-Document successful-ok
Here I opened a B&W Scan with okular that was output to a PDF
It did print, first pdf I have had print ! So Perhaps B&W is an important part of the puzzle
localhost - - [08/Sep/2012:19:32:13 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 839 Create-Job successful-ok
localhost - - [08/Sep/2012:19:32:13 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 91613 Send-Document successful-ok
Here I opened a pdf output from a color scan with okular.
Started print to the MF3010. Job appeared on the CUPS Job list, but was hung
The only record in /var/log/cups/*.log was this line, when I canceled the job in CUPS at local:631 interface.
localhost - - [08/Sep/2012:19:34:11 -0400] "POST /jobs HTTP/1.1" 200 140 Cancel-Job successful-ok
So I went back to the LO spreadsheet that printed (first three rows of the log), changed a row font color to red. It printed OK in Greyscale, here:
localhost - - [08/Sep/2012:20:36:11 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 255 Create-Job successful-ok
localhost - - [08/Sep/2012:20:36:11 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 56260 Send-Document successful-ok
So it is not just color, or should I say color to greyscale done correctly.
To narrow my issue down, I made three new simple scans of the same color image.
I use VueScan.
File 1.PDF - A scan set for color picture 24bpp
File 2.PDF - An output of the first scan, with output type reset to BW (16bpp grey scale)Picture.
File 3.PDF - A scan set to scan BW (16bpp greyscale) picture
Caution when reading below - I printed them in reverse order.
Additional lines from /var/log/cups/access.log
First I opened file 3 in okular - Printed OK
localhost - - [08/Sep/2012:20:48:08 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 863 Create-Job successful-ok
localhost - - [08/Sep/2012:20:48:08 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 121545 Send-Document successful-ok
Next I opened file 2 in okular - Printed OK
localhost - - [08/Sep/2012:20:48:33 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 853 Create-Job successful-ok
localhost - - [08/Sep/2012:20:48:33 -0400] "POST /printers/CanonMF3010 HTTP/1.1" 200 146035 Send-Document successful-ok
Finally, I opened file 1 in okular, attempted print. As sort of expected, hung, until I killed it.
localhost - - [08/Sep/2012:20:49:07 -0400] "POST /jobs HTTP/1.1" 200 140 Cancel-Job successful-ok
So from this I will restate my problem:
When content opened in a color PDF format, the print process hangs, no useful error information in /var/log/cups/*.log
When content opened in a BW(1bpp or 16bit greyscale) PDF format, printing is successful.
So I am off to look around for color PDF issues,
Hmmm… I don’t know the definitive answer here, but your post reminded me of a recognised issue concerning the default cache size CUPS uses
Portal Printing - openSUSE
Here’s an openSUSE bug report concerning the same
https://bugzilla.novell.com/show_bug.cgi?id=628233
In particular, comment #23 onwards, discusses how some users found success by increasing the RIPCache value to cope with large PDF files.
echo >> /etc/cups/cupsd.conf RIPCache 128m
Others had reported finding success using even larger values! (eg RIPCache 1024m)
You can set this value permanently in /etc/cups/cupsd.conf,
or temporarily (for test purposes) via CLI (as root)
cupsctl RIPCache=1024MB
Interesting read.
I tried
cupsctl RIPCache=1024MB
This did not help
As it it very quiet in the early AM, I did note that my variable speed cpu fan was spinning a bit harder.
I noted in System Monitor that the driver module cnpkmoduleufr2 had one core (of 4) fully pegged at 100%.
I have done a little more experimenting as well.
Again playing with my scanner and Vuescan, I created jpeg and tiff images of the same image used for files 1,2 and 3 in both B&W and color.
I call these test 4 bw.jpg, test 4 bw.tif and test 5 clr.jpg, test 5 clr.tif.
None of these 4 files will print when opened with okular, all have than same hang signature described above - 1 core 100% in use.
So issues is not PDFs in color, rather some part algorithm common to color PDFs, jpeg color or b&w and tiff color or b&w printing.
Seems fairly clear to me that this issue is in the Canon hosted ufr2 driver.
My only other printer is a CanonPro9000 with a Turboprint driver, prints all these OK.
I need to figure out how to report this to the driver folks at Canon.
I find no other drivers (e.g. Turboprint) that support this Canon.
At this point I am fairly sure the problem is the driver.
There is no direct way to log a bug with Canon that I can find, so I wrote a product review making note if it, hoping someone at Canon might notice.
They make it fairy clear that Linux drivers are “best effort”.
I tried one other experiment, looking at drivers available for similar vintage Canon imageClass Laser printers.
Many specified the driver I am already trying.
There was one other, which I downloaded and installed.
It processed a “test Page” from the Yast interface, the file passed thru the Windows spooler (I watched) but nothing happened at the printer.
So I am back to ver 2.5 of the original driver and at the moment can’t print certain content.
The driver is the UFRII printer driver for Linux version 2.50, correct?
You could try contacting Canon by email:
Canon U.S.A. : Service & Support
Correct, also tried Ver 2.40, same result
You could try contacting Canon by email:
Canon U.S.A. : Service & Support
Will do that as well.
Shame on me, I simply forgot that Canon’s Linux support is lacking.
Found that out two years ago with my PRO9000; Turbo print saved me there, but they have nothing for this unit.