Genicom Microlaser 210 driver not detected or supplied

[Alan Pope 🍺🐧🐱 🦄]

Binary package hint: system-config-printer

The Genicom Microlaser 210 (ML210) networked printer is detected and works perfectly with the "Generic PostScript Printer" (recommended) driver, but the printer configuration tool doesn't offer this as a suggested driver, instead I must manually select Generic -> Postscript Printer every time I install the printer on a new system.

Please could the Genicom Microlaser 210 be listed as a printer which works with that driver.

The following information is taken from the built in web page on the printer. I hope it's useful:-

Product Name: GENICOM microLaser 210 Product Version: 1.69
Printer Name: GENICOM microLaser 210 PostScript/PCL 5e Version: 3010.106
Installed Memory: 32 Mbytes Network 1 Version: 1.0/17(010503)
Engine Version: 1.23 (4DB6-29) Serial Number: ZCS-nnn-nnnnn

I also checked out the manufacturers website and note they have PPD drivers available if that helps:-

http://www.tallygenicom.com/support/laser/IP-PPD-drv.htm
http://www.tallygenicom.com/support/laser/IP-UNIX-drv.htm

These also seem to work well.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: system-config-printer-gnome 1.1.3+git20090218-0ubuntu7
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: system-config-printer
Uname: Linux 2.6.28-9-generic i686

[Till Kamppeter (till-kamppeter)]

Can you run the following two commands

/usr/lib/cups/backend/snmp
/usr/lib/cups/backend/dnssd

lpinfo -l -v

so that we can see which printer information CUPS captures and and supplies to system-config-printer?

[Alan Pope 🍺🐧🐱 🦄 (popey)]

alan@wopr:~$ /usr/lib/cups/backend/snmp
network socket://192.168.129.99 "GENICOM microLaser 210" "GENICOM microLaser 210 192.168.129.99" ""

alan@wopr:~$ /usr/lib/cups/backend/dnssd
alan@wopr:~$

alan@wopr:~$ lpinfo -l -v
Device: uri = socket
        class = network
        info = AppSocket/HP JetDirect
        make-and-model = Unknown
        device-id =
Device: uri = beh
        class = network
        info = Backend Error Handler
        make-and-model = Unknown
        device-id =
Device: uri = socket://192.168.129.99
        class = network
        info = GENICOM microLaser 210 192.168.129.99
        make-and-model = GENICOM microLaser 210
        device-id =
Device: uri = hal
        class = direct
        info = Hal printing backend
        make-and-model = Unknown
        device-id =
Device: uri = hpfax
        class = direct
        info = HP Fax (HPLIP)
        make-and-model = Unknown
        device-id =
Device: uri = hp
        class = direct
        info = HP Printer (HPLIP)
        make-and-model = Unknown
        device-id =
Device: uri = http
        class = network
        info = Internet Printing Protocol (http)
        make-and-model = Unknown
        device-id =
Device: uri = ipp
        class = network
        info = Internet Printing Protocol (ipp)
        make-and-model = Unknown
        device-id =
Device: uri = lpd
        class = network
        info = LPD/LPR Host or Printer
        make-and-model = Unknown
        device-id =
Device: uri = scsi
        class = direct
        info = SCSI Printer
        make-and-model = Unknown
        device-id =
Device: uri = smb
        class = network
        info = Windows Printer via SAMBA
        make-and-model = Unknown
        device-id =

[Till Kamppeter (till-kamppeter)]

Thank you for posting this output. It shows that the printer does not give any hint that it is a PostScript printer when detected through the network. If it would tell that it is a PostScript printer, system-config-printer would select the generic Postscript printer automatically.

So only explicit adding of this model to the OpenPrinting database would make it set up automatically.

[Dafydd Crosby (dcrosby)]

An XML printer profile has been made upstream.

[Till Kamppeter (till-kamppeter)]

Printer added in foomatic-db upstream.

[Launchpad Janitor (janitor)]

This bug was fixed in the package foomatic-db - 20090617-0ubuntu1

---------------
foomatic-db (20090617-0ubuntu1) karmic; urgency=low

  * New upstream release
    - Many new printer models added (Fixes: LP: #10871, LP: #83960,
      LP: #114681, LP: #121060, LP: #258058, LP: #273975, LP: #343444,
      LP: #371737).
    - More user-friendly UI strings for the "Print Quality" option in some
      Brother PPD files (LP: #141487).
    - Replaced broken PPD for the Kyocera FS-9100DN by the one for the
      FS-9120DN (LP: #344691).
    - Added "*cupsFilter:" lines to all PCL-XL PPD files from Ricoh and OEM
      so that they accept PDF as input format. This assures that always the
      most straightforward CUPS filter chain gets used and interferences
      between filters (like LP: #361772) get avoided.
    - Removed "Black and White" Color Mode (1 bit per pixel) from the
      "cdj550" driver. This mode is not supported by the driver (LP: #337133).
    - DesignJet driver assignement fixes, new "cdnj500" driver.
    - Correction of auto-detection strings.
    - Addition of CUPS custom option definitions to the PPDs from Ricoh
      family and OEM.
    - New "pxldpl" driver entry for the Dell 3010cn and Dell DPL printers
      in general.
  * Merge from debian unstable, remaining changes:
    - Driver entries removed for drivers which are not shipped by Ubuntu
    - Fixed manufacturer-supplied PPDs: "*CloseUI <option>" ->
      "*CloseUI: <option>", "*1284DeviceId" -> "*1284DeviceID".
    - openprinting-ppds-extra package with PPDs from Ricoh family and OEM
      and non-English PPDs from Kyocera
    - Linked PPD files with Foomatic database, so that links in the Foomatic
      XML files keep working.
    - Removed link into /usr/share/cups/model, it makes PPDs appearing
      twice.
    - debian/patches/bjc600-bjc800.patch: Removed workaround for Ghostscript
      crashing when feeding bjc600/bjc800 drivers with PDF. The Ghostscript
      shipped by Ubuntu is fixed.
    - foomatic-filters-ppds discontinued upstream, updated debian/control
      appropriately.
    - foomatic-db does not make sense without foomatic-db-engine and
      foomatic-filters, made the Recommends: a Depends:.

 -- Till Kamppeter <email address hidden> Wed, 17 Jun 2009 23:34:49 +0200