From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
I have a lexmark z605 USB Printer that isn't supported by any cups or
gimp-print drivers, but lexmark offers linux cups drivers, the package
contains a pair of RPMs which include needed lirbaries for the driver
and the driver with cups ppd.
After installing i load system-config-printer and configure the
printer, the printer is detected on USB (/dev/usb/lp0), but it won't
list the installed driver.
This may not seem like a bug or anything but for me is a big FLAW,
systems like Mandrake Control Center or Yast handles it fine, I have
to resort to the CUPS web interface to configure the printer, in this
case the driver and the printer are corrently detected without problems.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Plug Lexmark Z600 Series Printer
2.Install Lexmark Z600 Series printer driver for CUPS for RedHat Linux.
3.Try to configure with system-config-printer
Actual Results: Driver not available, not listed.
Expected Results: The driver list (on Lexmark section) should have
the Lexmark z600 Series available as an option. Should detect the new
installed backend and printer driver from CUPS.
Printer: Lexmark Z605 USB Printer
Driver: Lexmark Z600 Series CUPS driver for RedHat Linux 9.0, v.1.0-1
The system-config-printer utility was only ever intended to work with
foomatic, so if it's not there in foomatic it won't be listed in
Did you try 'Import PPD...' from the Action menu?
Yes, i tried "Import PPD" but the Lexmark PPD was gzipped (the same as
all other ppd files on /usr/share/cups/model) and
system-config-printer dosen't handle them compressed, no problem, i
gunziped and tried again, the ppd was imported ok, tried adding the
printer and still the printer dosen't showed up not in lexmark, not in
others or generic.
I restarted the program one more time, and gived me this output:
No match for USB device:
mfr "Lexmark "
model "Z600 Series"
desc "Lexmark Z600 Series"
Please report this message in Bugzilla:
Choose 'foomatic' as the component.
I tried anyways, and voila!, there it was, on Lexmark the "Z600
(PPD)", it whould be nice to import ppds without needed to restart the
program (maybe reopening the foomatic databases), handling gziped ppds
will be nice too, less hasle for newbies.
After adding the printer it asked me if i wished to print a test page,
ok print the test page, however there was an error, CUPS became
unresponsibe, i restared it (/etc/init.d/cups restart), deleted the
printer and tried again the whole thing, at the end the page was
sended but never printer.
The problem is that the Z600 series comes with a custom backend for
cups to comunicate to the printer and a custom rasterizer,
system-config-printer won't set the correct backend to comunicate, or
dosen't sets the correct rasterizer.
system-config-printer in rawhide now re-loads the foomatic database after
importing a PPD, and *ought* to behave a bit better with some third party
drivers. It still won't know about extra backends though unfortunately.
I have the same printer and followed the suggestions above.
The driver sees the printer because it wakes it up and then nothing happens. No
blank paper or anything.
The printer is on a Win98 Print Serve serving several other printers. Windows
apps can talk to the printer with no problem.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing per lack of response to previous request for information.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.