Brother DCP 7020 uses wrong printer drivers

Indeed. In ubuntu 8.04 everything seems fine with the automatically detected drivers except... nothing comes out on the printer.

Using the HL-1250 driver works.

Would you share with us how you found out that driver worked ?

And thank you for this report, I just happened to need printing on this particular model at this late time (12:35AM) and this saved me from more trouble :)

It's been broken for a long time. Ubuntuforums thread.

This bug is still present in Ubuntu 8.10.

I'm going to test Jaunty alpha 3 for this bug in a few weeks, but I just realized that
'Indeed' ~Fabián Rodríguez
constitutes a confirmation.

Jaunty Alpha 3.

I plug my printer in and it immediately selects the wrong driver. Unlike, say, a Human Being, I know it's wrong. I set it to the HL-1250 Driver as I do with every Ubuntu release with this same old lingering bug. I print a test page and, of course, it works.

I open xsane.
Failed to open device 'v4l:/dev/video0': Invalid argument
As usual.

You try to run XSane as ROOT, that really is DANGEROUS!
Do not send any bug reports when you have any problems while running XSane as root: YOU ARE ALONE!

Gee thanks, XSane. I didn't already know that. I've seen that every time I've gone to scan something for the last two years, I'm alone and unloved, I think I've got it by now.
Ope, same error. I guess I've got to navigate Brother's site and download their Completely GPL licensed, already .deb packaged, fully functional and stable printer scanner. I don't have time for that right now. Next bug.

Low hanging fruit if I ever saw it. Cleanup in Aisle 12.

scanner driver, blehh.
Years of frustration does murder to a person's spelling.

As usual, I will provide any and all information from my machine anyone needs, not that anyone needs any. The DCP-7020 is simply not in the list that Ubuntu uses to set up Brother printers and scanners. It just needs to be added to that list; I can't do it, but for someone out there it has got to be trivial.

Ethana2, the actual forums URLs would be helpful, (unlike your comments). Developers rarely pay attention to bugs where they'll get this kind of feedback.

I've tested this in Jaunty 3 with the same results.

If you have an issue with the DCP-7020 scanner functionality, please open a separate bug.

Yes, I know, I'm sorry...

http://ubuntuforums.org/showthread.php?p=4026344#post4026344
There's the Ubuntuforums thread.

/me files a separate bug on the scanner drivers.

I tested this in Jaunty alpha 4 with the same results. The issue here is that the required packages are still in multiverse despite these drivers being GPL:

- brother-cups-wrapper-laser
- brother-lpr-drivers-common
- brother-lpr-drivers-laser

Even after their proper installation the automatic detection & configuration tool indicates there are no suitable drivers (see attached screenshot) and its Search option proposes a " Generic " driver.

I had to invoke the printer configuration from commnd line:
gksudo system-config-printer

Workaround:
1- Install brother-cups-wrapper-laser package via Synaptic package manager
2- From a terminal window:
gksudo system-config-printer

3- HIghlight your (wrongly) configured DCP-7025 printer if it exists.
4- Righclick your (wrongly) configured DCP-7025 printer, choose Properties
5- ON the " Make & Model " line, click the " Change... " button
6- Leave "Select Printer from Database" chosen, make sure " Brother" is selected in the list, click " Forward"
7- " DCP7020 for CUPS" should now be in the list, select it and click "Forward"
8- In the next dialog, choose " Use the new PPD (Postscript Printer Description) as is." , click "Apply"
9- Print a test page, it should come out as expected with the Ubuntu logo and test patterns

Same problem / workaround in Jaunty alpha 6.

Tested again in Jaunty beta, same problem still present, same workaround applies.

I, too, have been watching this bug and confirm that nothing has changed in Jaunty. SO let's do something about it!

I also notice that the bug must be reported against the wrong package, because a) libprinterconf is in Universe and b) it's not even installed on my Jaunty system. SO let's figure out what package is being called. dbus refers to com.redhat.NewPrinterNotification, which apparently refers to the system-config-printer package.

I will set this bug to point to that package. (If it's wrong eventually someone will set it straight, but we know libprinterconf is definitely wrong.) On this system I have system-config-printer-common and system-config-printer-gnome ... so that must be on the right track.

Now that I'm looking at the package I see Bug #234822 -- it's a wishlist item for Ubuntu to detect and install the right drivers for a Brother printer. HOWEVER I know that even WITH the appropriate drivers installed the wrong driver gets chosen.

So this bug or Bug #234822 might be considered a duplicate, or maybe they're just related bugs. One of us can have a look at them and add appropriate comments as needed.

[I'm also wondering how to debug a similar problem -- I looked at Bug #131990, for instance. When I get back to my office with the Brother DCP-7020 printer I will tinker with it and see if I can tell what it says when it gets plugged in and what it says once I have everything installed.]

I believe the bug was originally reported against the wrong package.

Thanks!

Bug still present on Ubuntu 9.10 alpha 2.
...same workaround applies.
....cept for the scanner, I can't figure that out.

Confirming that this is a One Hundred Paper Cuts bug, it only needs to add the printer to foomatic-db, so that the "hl1250" driver gets auto-selected.

Very few Ubuntu users use a Brother DCP-7020, so this bug does not affect a significant number of users; it is not a paper cut.

Added printer to Foomatic database upstream.

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