Package Details: brother-mfc-j6510dw 3.0.0-5

Git Clone URL: https://aur.archlinux.org/brother-mfc-j6510dw.git (read-only, click to copy)
Package Base: brother-mfc-j6510dw
Description: LPR and CUPS driver for the Brother MFC-J6510DW
Upstream URL: http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/index.html
Keywords: brother cups driver printer
Licenses: unknown
Submitter: lswest
Maintainer: lswest
Last Packager: lswest
Votes: 4
Popularity: 0.003697
First Submitted: 2011-10-18 16:06
Last Updated: 2021-01-18 15:08

Pinned Comments

lswest commented on 2021-01-13 16:43

I just set this up on a new computer, and lpadmin kept crashing when trying to add a printer using this driver.

Edit on 18th of Jan: Thanks to mossblaser, I've implemented a fix in the PKGBUILD (3.0.0-5) which should allow this driver to continue to work with Arch's version of CUPS.

Alternatively, you can use the printer with the IPP Everywhere driver, and the URI ipp://<IP>:631/ipp.

Replace <IP> with the IP of your printer. I'm leaving this comment here for posterity, and for anyone who runs into a similar issue.

Latest Comments

1 2 3 Next › Last »

lswest commented on 2021-01-18 15:04

Hi mossblaser, thanks for the kind words and taking the time to outline a fix! I've just implemented your fix in the PKGBUILD and published a new pkgrel.

I'll also update the pinned comment to make it clear that the package should work with the Arch version of CUPS.

mossblaser commented on 2021-01-18 13:57

Hi lswest, thanks for your maintenance of this package over the years! Like you I recently discovered that cups would crash when attempting to use this driver. After some debugging I've managed to work out what was going wrong and have a fix to contribute.

According to a note I spotted in the wiki In November 2020, Arch switched away from Apple's CUPS to a fork maintained by the OpenPrinting project which is apparently better maintained. It is this change which has set off the problems for this driver.

Specifically, the PPD file supplied by Brother (both in their source, RPM and DEB releases of the driver) contains a commented out block which isn't completely commented out:

From src/mfcj6510dw/opt/brother/Printers/mfcj6510dw/cupswrapper/brother_mfcj6510dw_printer_en.ppd:

*%=== Reverse Printing ================================
*%OpenUI *BRReverse/Reverse Printing: PickOne
*%OrderDependency: 30 AnySetup *BRReverse
*%DefaultBRReverse: OFF
*%BRReverse OFF/Off: "          "
*%BRReverse ON/On: "          "
*CloseUI: *BRReverse

Spot the missing % in the CloseUI line.

In the Apple version of CUPS, the PPD parser silently ignored this extraneous CloseUI line, however the OpenPrinting fork now used by Arch segfaults (it appears to be missing a NULL check).

To fix this package, we simply need to patch in the missing % from the PPD file. This can be done by adding the following as the penultimate line in build() in the PKGBUILD:

perl -i -pe 's#\*CloseUI: \*BRReverse#*%CloseUI: *BRReverse#g' ./cupswrapper/brother_mfcj6510dw_printer_en.ppd || return 1

After making this change, the driver comes back to life.

While the IPP Everywhere driver solution is better than nothing; I would suggest that this driver is the better overall option since it more fully supports the printer's capabilities.

lswest commented on 2021-01-13 16:43

I just set this up on a new computer, and lpadmin kept crashing when trying to add a printer using this driver.

Edit on 18th of Jan: Thanks to mossblaser, I've implemented a fix in the PKGBUILD (3.0.0-5) which should allow this driver to continue to work with Arch's version of CUPS.

Alternatively, you can use the printer with the IPP Everywhere driver, and the URI ipp://<IP>:631/ipp.

Replace <IP> with the IP of your printer. I'm leaving this comment here for posterity, and for anyone who runs into a similar issue.

lswest commented on 2018-02-06 09:33

I've updated the PKGBUILD to remove the deb2targz dependency. I've also removed a2ps from the dependencies, and added lib32-glibc (on namcap's recommendation).

I did have to reconfigure my printer after updating the package, but since then everything is working as expected. If you run into issues, please let me know!

lswest commented on 2018-02-06 08:18

@tuxayo: deb2targz has always been listed as a dependency (admittedly, not a build dependency). However, as it's also an AUR package, so you'll need to install that first via makepkg or yaourt or whatever your choice is for that.

If by the coming weekend I've gotten a chance to go over the PKGBUILD again, I may update it with some tweaks and adjustments. There shouldn't be anything stopping you from installing the package though.

tuxayo commented on 2018-02-05 22:33

deb2targz should be added as a build dep.

==> Making package: brother-mfc-j6510dw 3.0.0-3 (Mon Feb 5 23:30:40 CET 2018)

==> Checking runtime dependencies...

==> Checking buildtime dependencies...

==> WARNING: Using existing $srcdir/ tree

==> Removing existing $pkgdir/ directory...

==> Starting build()...

/home/victor/.cache/pacaur/brother-mfc-j6510dw/PKGBUILD: line 19: deb2targz: command not found

lswest commented on 2017-08-18 15:10

@Fandekasp I'm not really sure what the problem could be. The only time I experienced something similar was when the paper type was set to US Letter with A4 loaded. Are you sure you are using/have loaded A4? If I remember correctly, doesn't Japan use different paper sizes (B-series)?

Besides that, I'd suggest posting on the forum - it could be there's something non-driver-specific going on. Good luck!

Oh, and the "unable to locate printer" error doesn't surprise me, as LPD expects an IP (or possible a local domain name), and BRW0080928378F wouldn't fulfil those requirements. I'd definitely stick to using the IP address.

Fandekasp commented on 2017-08-18 03:09

Unable to print anything using this driver on a Brother MFC-J6510DW printer in Japan.

http://i.imgur.com/vM6GTcO.png


The printer is discoverable by default and created the connection lpd://BRW0080928378F/BINARY_P1 , but when trying to print something I'll get the following error:

> Unable to locate printer "BRW0080928378F".

I then tried all connections I could think of, like lpd://192.168.100.18/BINARY_P1, socket://192.168.100.18:9100 or http://192.168.100.18:631/ipp/ , but when trying to print something with these, it would auto-finish without raising any warning/error

I can access my print web admin via http://192.168.100.18/net/net/service_detail.html (and the printer was discovered by cups), so there is no problem with the network.

Any idea what could be wrong ?

ElMastro commented on 2017-03-24 17:27

Thanks, I'll have to ask in the forum, as it seems my laptop has some misconfiguration

lswest commented on 2017-03-23 21:03

It works here - I printed something as recently as two days ago. I even use it shared via Google CloudPrint. Make sure your page settings are correct - I find the printer won't do anything if it's expecting A4 paper when Letter is loaded.

I've put the settings I use here: http://pastebin.com/hcTMw8jr

Ah, I also had to recently re-enable the cups service since the name appears to have changed. Try running sudo systemctl start org.cups.cupsd.service (and enable).