https://bugzilla.novell.com/show_bug.cgi?id=683476 https://bugzilla.novell.com/show_bug.cgi?id=683476#c1 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID Summary|cups can print test page, |Canon's proprietary driver |but attempts to print with |for MF4370dn printer no |apps cause printer data |longer works (worked with |error instead of printing |11.2) --- Comment #1 from Johannes Meixner 2011-03-30 08:19:06 UTC --- I am afraid, we cannot do anything here because you use a proprietary third-party driver from Canon. We neither have such a printer model to reproduce it nor do we test proprietary third-party drivers. A German Canon web page lists for a "i-SENSYS MF4370dn" (I hope this is the exact model name of your printer) the printer language "UFRII-LT" which is not a known standard printer language so that such a printer is a so called "GDI printer". Nobody - except the manufacturer - can provide support for such kind of hardware because nobody - except the manufacturer - knows how such kind of hardware works, see http://en.opensuse.org/SDB:GDI_Printers Therefore all you can do is to contact Canon for help with their proprietary driver. Some best-guess hints: Your /var/log/cups/error_log in attachment #421956 does not show any error related to processing a print job. Have a look at "If problems are encountered" in http://en.opensuse.org/SDB:CUPS_in_a_Nutshell how to get CUPS debug information while processing one particular print job. The YaST test page /usr/share/YaST2/data/testprint.ps is a very small and simple generic PostScript document. In contrast applications usually produce more complex and much bigger PostScript printing output. This indicates that something fails when processing usual PostScript documents but without meaningful CUPS debug information this is only a blind guess. You may try if simple plain text printing using echo Hello | lp -d and simple PostScript printing using echo Hello | a2ps -1 -o- | lp -d also works. The issue must be somehow caused by Canon's proprietary driver because usual printing from usual applications works with the usual free software drivers which are included in openSUSE 11.4. Because the issue is caused by proprietary third-party software, the bug report is "invalid" for us. Nevertheless if you get meaningful CUPS debug information for a _single_(!) print job which fails to print, you could attach it as MIME type "text/plain" to this bug and I will have a look - but I assume I cannot help in this case even if I have meaningful CUPS debug information. In any case contact Canon and ask them for support for their proprietary driver software. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=683476 https://bugzilla.novell.com/show_bug.cgi?id=683476#c3 --- Comment #3 from Johannes Meixner 2011-03-30 12:55:04 UTC --- All the time something changes in free software from version to version. There are of course changes in CUPS and e.g. in Ghostscript and in zillions of other free software packages. Even if a change in CUPS or in Ghostscript or wherever lets Canon's driver no longer work, only Canon could adapt their proprietary driver to work again with the current versions of free software packages and only Canon could check if a change in whatever free software package would be actually a bug and report such a bug to the appropriate free software project because only Canon knows how their proprietary driver works. But I didn't notice any such participation of Canon in CUPS so that it seems Canon does what all GDI printer manufacturers usually do: They make their own stuff isolated only on their own so that nobody else can help if something goes wrong with their selfmade closed-up proprietary stuff. Meaningful /var/log/cups/error_log debug information might show what lets their proprietary driver no longer work. Perhaps there is a chance to adjust something so that their driver works again. A blind guess: See "Various printout failures with CUPS default RIPCache 8m" at http://en.opensuse.org/Portal:Printing Does it perhaps help to add in /etc/cups/cupsd.conf a line RIPCache 128m or even up to RIPCache 1024m (the latter only if you have at least 2GB main memory) and restart the cupsd afterwards? I know that some manufacturers label their GDI printer boxes as "supported by Linux" because they provide a proprietary driver. But then - from my point of view (but I am not a lawyer) - such manufacturers must do what they promised on their boxes and actually provide support for Linux in general. I am afraid, I don't know how to contact Canon regarding support for their drivers for Linux. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=683476 https://bugzilla.novell.com/show_bug.cgi?id=683476#c5 --- Comment #5 from Johannes Meixner 2011-03-30 14:22:33 UTC --- Oops - I overlooked "Connection type: IP" in comment #0. Please connect it via USB for a test to get whatever possible network issues out of the way for now and configure a new print queue for your printer via USB. I only need /var/log/cups/error_log but I need it with debug messages, see "If problems are encountered" in http://en.opensuse.org/SDB:CUPS_in_a_Nutshell I.e. do: 1. Set the "LogLevel debug" in /etc/cups/cupsd.conf 2. Stop cupsd 3. Move /var/log/cups/error_log* to another location (or delete it) in order to avoid having to search through gigantic log files 4. Start cupsd 5. Submit a single print job (e.g. print one small page from Firefox) 6. Wait one minute and then attach /var/log/cups/error_log as MIME type "text/plain" to this bug -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=683476 https://bugzilla.novell.com/show_bug.cgi?id=683476#c7 --- Comment #7 from Johannes Meixner 2011-04-01 09:49:28 UTC --- What is of interest in attachment #422347 regarding processing a print job: ----------------------------------------------------------------------- I [30/Mar/2011:22:18:50 -0400] [Job 1] Started filter /usr/lib/cups/filter/pstops (PID 13967) I [30/Mar/2011:22:18:50 -0400] [Job 1] Started filter /usr/lib/cups/filter/pstoufr2cpca (PID 13968) I [30/Mar/2011:22:18:50 -0400] [Job 1] Started backend /usr/lib/cups/backend/cnusb (PID 13969) .. D [30/Mar/2011:22:18:50 -0400] PID 13967 (/usr/lib/cups/filter/pstops) exited with no errors. ----------------------------------------------------------------------- But up to [30/Mar/2011:22:19:20 -0400] there are no further messages what happened to Canon's driver (PID 13968) and Canon's backend (PID 13969). It seems about half a minute later Canon's driver and Canon's backend are still running - otherwise the cupsd would have reported something regarding "PID 13968" and "PID 13969". There are also no messages which indicate an error while Canon's driver and Canon's backend are running. When it fails the same with Fedora 15 it indicates that Canon's proprietary stuff may depend on whatever details of previous versions of whatever open source software (e.g. Ghostscript or whatever else might be used by Canon) so that Canon's driver should be adapted accordingly. I assume sooner or later Canon may notice this and then Canon may provide an update of their driver.

From my point of view I cannot do anything more here.

Nevertheless I would appreciate it if you coud provide feedback what came out at the end because I am interested in which way Canon actually supports their proprietary driver for Linux. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=683476 https://bugzilla.novell.com/show_bug.cgi?id=683476#c9 --- Comment #9 from Johannes Meixner 2011-04-01 14:36:15 UTC --- I assume you noticed the variuos LICENSE files which Canon provides therein. Some parts are free software - this is usual. But other parts are not and this makes it non-free software. Usually the non-free parts contain the actual driver (usually in one or a few binary-only libraries) but I didn't check all their files in detail. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=683476 https://bugzilla.novell.com/show_bug.cgi?id=683476#c12 --- Comment #12 from Felix Miata 2011-07-08 18:53:24 UTC --- Still no change, but on doing 'zypper up MozillaFirefox-3.6.18' the following messages appeared: .. Installing: MozillaFirefox-3.6.18-2.1 [done] Additional rpm output: Error in file "/opt/kde3/share/applications/kde/printers.desktop": "print/manager" is an invalid MIME type ("print" is an unregistered media type) Error in file "/opt/kde3/share/applications/kde/printers.desktop": "print/manager" is an invalid MIME type ("print" is an unregistered media type) Any possibility this media type error is related to the problem? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=683476 https://bugzilla.novell.com/show_bug.cgi?id=683476#c14 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Canon's proprietary driver |Canon's proprietary driver |for MF4370dn printer no |for MF4370dn printer no |longer works (worked with |longer works (worked with |11.2) |11.3) --- Comment #14 from Felix Miata 2011-07-26 16:40:42 UTC --- It's now nearly 8 months since Canon updated its driver last. It's latest works also in 11.3, fails also in 12.1M3. I brought this bug up on the cups-bugs mailing list 3 weeks ago, and got 0 responses. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=683476 https://bugzilla.novell.com/show_bug.cgi?id=683476#c16 --- Comment #16 from Felix Miata 2011-08-06 00:58:06 UTC --- URL field refuses to accept upstream http://www.cups.org/str.php?L3916 because it is not a Bugzilla tracker. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=683476 https://bugzilla.novell.com/show_bug.cgi?id=683476#c18 --- Comment #18 from Felix Miata 2011-11-21 19:10:32 UTC --- In every case of an openSUSE that I tried to get the printer to work but failed, booting that installation wakes the printer and causes it to be unavailable for printing by systems that do work, until such time as I power cycle the printer. The only way I know to prevent this corruption is to go into /var/cache/cups/ and /var/spool/cups/ and delete job.cache* and [a-z]#####* before booting any system that the printer won't work properly in. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.