Bug 1250

Summary:	Brother printer won't print from USB
Product:	Mageia	Reporter:	Doug Laidlaw <laidlaws>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	doktor5000
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	udev	CVE:
Status comment:

Description Doug Laidlaw 2011-05-12 05:05:41 CEST

Description of problem:
My Brother MFC-490CW printer is not usable via the USB connection.  It is detected and configurable, but printing fails. This started under Mandriva with an MFC-240C; at first I needed to power down and restart the printer after sending it a job, then even that didn't work, so I upgraded to wireless networking with the 490CW under Mandriva.  I haven't tested the 240C under Mageia. Both printers work fine under Ubuntu.

I reported the problem to Brother Support.  They said that it was something in /lib/udev/rules.d, and gave up.  I wanted to copy Ubuntu's udev/rules.d entry across, but it doesn't seem to have the directory at all.

Version-Release number of selected component (if applicable):


How reproducible:
Every time I try to print via USB.


Steps to Reproduce:
1.
2.
3.

Comment 1 Ahmad Samir 2011-06-04 00:28:19 CEST

The MFC-490CW doesn't work even with the power off/on workaround?

It's probably indeed a udev issue, and it's probably Brother who should ship/offer a udev rule.

Source RPM: (none) => udev

Comment 2 Doug Laidlaw 2011-06-04 03:50:21 CEST

Noted.  Brother Support didn't seem inclined to offer a udev rule.  They simply said to avoid the USB connection.

Xsane detects the USB connection AND the network connection.  Support gave me the scanner rule which allows the scanner to be available to an ordinary user, with a suggestion that I try it!  That was already there.  I changed the one they gave me to refer to the printer instead, but that didn't help.

udev seems to be fussy about the initial number in the filename; yesterday I noticed in a README, a revised udev rule with a changed number.  I put the one I tried with the other printer rules.

lsusb gives the following:

Bus 002 Device 002: ID 04f9:01fb Brother Industries, Ltd 

That corresponds to the USB scanner showing in Xsane.

Comment 3 Doug Laidlaw 2011-06-04 18:25:15 CEST

This is embarrassing.  I just set "tail -f syslog", unplugged and replugged the printer to see what would happen.

The printer was recognised immediately, task-printer-server was installed, and I was able to add the USB printer and print a test page.

This MFC requires me to run a scanner config tool before the scanner is visible to SANE etc.  Perhaps that enabled the printer as well; I don't know.

Comment 4 Doug Laidlaw 2011-06-05 01:26:21 CEST

The USB printer was showing as idle on bootup next morning, but wouldn't print.  Switchoff/switchon enabled it.

I didn't configure the scanner until I needed it, which was only recently.  That may have changed things. The config tool is /usr/bin/brsaneconfig3, a binary file needing root permission.  That step wasn't required with the older MFC-210C.

Comment 5 Doug Laidlaw 2011-06-07 17:13:56 CEST

This is now solved for me, but I think that the udev issue is unaffected.

I reinstalled Mageia 1 from the DVD for other reasons.  I ran brsaneconfig3 first, then started printerdrake.  The printer was configured automatically as:

dnssd://Brother%20MFC-490CW._printer._tcp.local/

It has run perfectly ever since.  I believe that with that connection, the udev issue is avoided.

Comment 6 Florian Hubold 2011-09-12 13:23:47 CEST

Closing as WORKSFORME.

Status: NEW => RESOLVED
CC: (none) => doktor5000
Resolution: (none) => WORKSFORME