Bug 743747

Summary: Unable to print from Brother MFC-8840D test print after clean install of opensuse 12.1
Product: [openSUSE] openSUSE 12.1 Reporter: Robert Koppelhuber <rkoppelh>
Component: OtherAssignee: Robert Koppelhuber <rkoppelh>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: jsmeix, rkoppelh
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Brother support investigation into problem. Recreated - confirmed cups bug.
Log files created during print test page failures
text version of log file submitted originally.

Description Robert Koppelhuber 2012-01-27 09:36:49 UTC
Created attachment 472988 [details]
Brother support investigation into problem. Recreated - confirmed cups bug.

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1

Following clean install of opensuse12.1 on Lenovo T61p (6459-A12) installed for printer Brother MFC-8840D its drivers using brother supplied installer  linux-brprinter-installer-1.0.3-1 which installed without error messages.

Note printer used to work fine using same hardware on Opensuse 11.3.

I suspect this bug exists since opensuse 11.4.

I initially working opensuse 11.3  to 11.4. Printer did not work (no 
test page printed and printer not connected message via cups or yast printer 
install utility. Spent two weeks installing and uninstalling with same error.

Error was Printer not connected. Will retry in 30 seconds.

Could cat files > /dev/usb/lp0 OK.
Couldn't print any other way

Consequently decided to do clean install with Opensuse 12.1 after reading that 
11.4 had trouble with usb printers of varying models due to problems with 
conflict in new kernel libusb and cups >=1.4.6.

Now getting varying errors of "Printer not connected. Will retry in 30 
seconds". or "Unable to open print file: No such file or directory" via cups 
homepage.

lsusb detects printer
lpinfo -l -v does not show usb mFC printer.

Did driver install with linux-brprinter-installer-1.0.3-1 which installed 
without error messages.

Inquired yesterday with support suggesting re-install lpr driver and then 
wrapper using rpm -ihv ......

Did that ... not change.

Uninstalled the MFC8840D driver lpr and cups package.

Repeated manual install using rpm -ihv with lpr then cupswrapper drivers.

Attached are some debug files

I have been trying to solve this issue for three months.

When initially on opensuse 11.3 installed printer had some trouble and then 
suddenly it all worked.

When searching web there are similar reported problems for 12.1 and brother 
MFC-8840D. Analysis suggests driver new kernel and new cups interaction bugs 
for some printer models. POssible problems with backend and kernel .

Printers and linux in general are very painfull and spoiling the linux 
experience which I think is a very good OS.

Reproducible: Always

Steps to Reproduce:
1.Clean install of opensuse 12.1 (or upgrade from 11.3 to 11.4)
2. Connect printer to usb and power on
3. lsusb detects printer ok
2.Install printer driver using linux-brprinter-installer-1.0.3-1
3. Using cups print test page
4. Error was "Printer not connected. Will retry in 30 seconds." on cups
5. lpinfo - l -v does not show printer ever. No change printer connected or not
6. To set printer to idle cancel via cups page print job, pause printer and resume.
7. Next attempt to print test page same problem again.
Actual Results:  
See above.

never lists the usb printer when it should particularly lsusb detects it correctly.

Additionally can cat files or echo text to /dev/usb/lp0 and it prints.

See attachment. Brother Australia recreated the problem at their factory. They suggested problem with usblp support in cups 1.5.0.

Expected Results:  
lpinfo -l -v should list usb printer when connected.

Test page should print.


See attachement

Normal Oxygen theme in use.

Basically cups hangs printer with error message

Printer not connected. Will retry in 30 seconds.

USB printing unusable. Unknow if other usb printer models affected.
Comment 1 Robert Koppelhuber 2012-01-27 09:42:25 UTC
Created attachment 472989 [details]
Log files created during print test page failures

Collection of concated log files.
Comment 2 Johannes Meixner 2012-01-27 13:53:31 UTC
In comment #0
-----------------------------------------------------------------
Could cat files > /dev/usb/lp0 OK.
...
lsusb detects printer
lpinfo -l -v does not show usb mFC printer.
-----------------------------------------------------------------
indicate that the CUPS backend cannot communicate
with the printer device.

What kind of file type is your attachment #472989 [details]
-------------------------------------------------------------
$ file bug-743747_log_files
bug-743747_log_files: Microsoft Office Document
-------------------------------------------------------------
Microsoft Office Document is an inappropriate format.
Please provide log files as plain text files.

The issue looks very much like a duplicate of bug #679488
"CUPS cannot detect USB printer Brother MFC 8420"

See in particular
https://bugzilla.novell.com/show_bug.cgi?id=679488#c14
for a possible workaround.

A matching CUPS upstream report is

http://www.cups.org/newsgroups.php?gcups.general+T+Q%22How+can+I+configure+a+Brother+MFC-8420%22

*** This bug has been marked as a duplicate of bug 679488 ***
Comment 3 Johannes Meixner 2012-01-27 14:12:52 UTC
Regarding comment #0
"Brother support investigation ... - confirmed cups bug."

If it is a CUPS bug, please report the issue directly
to CUPS upstream via
  http://www.cups.org/

We cannot reproduce it because we do not have such kind
of printer model (we have no Brother MFC device at all)
so that we cannot really help here.

There is nothing changed in our cups packages regarding
USB printer access or USB printer detection in general
(neither do we have any patches which change the CUPS upstream
behaviour for USB or parallel port etc. or printer detection).

"Responsibility for a bug is said to lie upstream when it
is not caused through the distribution's porting efforts."
see "UPSTREAM" at
https://bugzilla.novell.com/page.cgi?id=fields.html#status
Comment 4 Johannes Meixner 2012-01-27 14:40:23 UTC
In your attachment #472988 [details]
from Brother support they wrote:
-----------------------------------------------------------------------
The issue is CUPS 1.5.0 seems to not have support for usblp printing.
-----------------------------------------------------------------------

This is plain wrong.

Therefore don't file a bug report regarding this particular case
at upstream CUPS.

This does not mean there is no issue in CUPS why it cannot detect
your particular printer - there could still be another issue
in CUPS or elsewhere why it cannot detect those kind of Brother
printers since some time.

CUPS 1.5.0 in openSUSE has support for usblp printing:
--------------------------------------------------------------------
root@host# rpm -q cups
cups-1.5.0-76.2

root@host# /usr/lib/cups/backend/usb
direct usb://HP/LaserJet%201220 "HP LaserJet 1220" ...

root@host# rmmod usblp

root@host# /usr/lib/cups/backend/usb

root@host# modprobe usblp

root@host# /usr/lib/cups/backend/usb
direct usb://HP/LaserJet%201220 "HP LaserJet 1220" ...
--------------------------------------------------------------------
I.e. the CUPS backend "usb" in CUPS 1.5.0 in openSUSE
uses the usblp kernel module for printing, and this works
well for my printer and for very most other printers too,
except since some time for some particular Brother devices.

One can configure CUPS via the configure option --enable-libusb
to use libusb for USB printing instead of the traditional
method via usblp kernel module but in CUPS 1.5.0 in openSUSE
we do intentionally not yet use the new libusb method because
there are issue reports at upstream CUPS regarding libusb.

Perhaps
http://www.cups.org/str.php?L3884
is somehow related - but it seems this one is also about libusb.
Comment 5 Robert Koppelhuber 2012-01-27 23:08:19 UTC
Created attachment 473118 [details]
text version of log file submitted originally.

 Send log_files.txt as requested.

Agree bug 679488 is similar. But it also got a similar run around with no one claiming ownership. 

Brother can recreate the problem and believe its a problem with cups.

679488 clearly suggests other printers also involved and problem occurs since 11.4.

I agree with 679488 - I have a paperweight printer!