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.