[cups.bugs] [LOW] STR #3916: Canon's proprietary driver for MF4370dn printer no longer works

[jsmeix.suse]

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR Closed w/o Resolution]

FYI,
some quotes from
https://bugzilla.novell.com/show_bug.cgi?id=683476
-----------------------------------------------------
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.
..
..
..
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.
..
..
..
I assume the CUPS software developers also cannot do
anything when non-free driver software is used
-----------------------------------------------------

Link: http://www.cups.org/str.php?L3916
Version: 1.4.6
Fix Version: Third-party