Bug 506708

Summary: brother hl-1430 printer is unable to print
Product: [Fedora] Fedora Reporter: cornel panceac <cpanceac>
Component: foomaticAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: josep.puigdemont, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-21 08:53:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
foomatic-rip.ps
none
foomatic-rip.log none

Description cornel panceac 2009-06-18 12:56:51 UTC
Description of problem:
in fedora 11 i'm no longer able to print on brother hl-1430 printer.

Version-Release number of selected component (if applicable):
$ rpm -q cups
cups-1.4-0.b2.18.fc11.i586


How reproducible:
always

Steps to Reproduce:
1.try to print anything
2.
3.
  
Actual results:
printer warms but nothing is printed

Expected results:


Additional info:

Comment 1 cornel panceac 2009-06-18 12:59:31 UTC
Created attachment 348434 [details]
foomatic-rip.ps

Comment 2 cornel panceac 2009-06-18 13:00:41 UTC
Created attachment 348435 [details]
foomatic-rip.log

Comment 3 Tim Waugh 2009-06-18 17:08:35 UTC
Did it work in Fedora 10?

Comment 4 cornel panceac 2009-06-18 17:12:57 UTC
worked perfectly. it's still working on windows xp, on same computer (and another one).

Comment 5 Tim Waugh 2009-06-19 10:21:10 UTC
So the 'Brother HL-1430 Foomatic/gutenprint-ijs-simplified.5.2' driver fails in Fedora 11.  Let's try the native CUPS gutenprint driver to eliminate foomatic from the equation.

Select System->Administration->Printing, double-click on HL-1430-series and click on the 'Change...' button next to the 'Make and Model' label.

Now select a driver that says 'Brother HL-1430 CUPS+Gutenprint v5.2.3 Simplified' and click Forward, then Apply.

Finally, print a test page -- does that give any better result?

If that fails, please try the driver named 'Brother HL-1430 Foomatic/hl1250' (this one was the default driver in Fedora 10).

If that still fails, try the others.

Let me know which driver gives the best results.

Comment 6 Josep 2009-06-19 14:28:39 UTC
Same problem here. I tried the suggestions in comment #5, and here I my results:

* gutenprint-ijs-simplified.5.2: doesn't print, the "data LED" blinks for a while, but then it stops and nothing is printed. This was the default driver selected, by the way.
* gutenprint-ijs.5.2: same as previous one.
* hpijs: works.
* hl1250: reports printer as stopped.
* lj4dith: does not work, the printer does feed a paper but nothing is printed on it.
* ljet4: same lj4dith.

Briefly: hpijs is the only driver that works, the rest don't.
It's strange that the hl1250 doesn't work as it was the one I used to have configured in F10.

Comment 7 Tim Waugh 2009-07-03 10:59:08 UTC
I think the reason the hl1250 driver wasn't working was foomatic: see bug #496521.  Perhaps you could try the "test update" foomatic package (4.0.2-3.fc11) and report whether the hl1250 driver works once again?

http://koji.fedoraproject.org/koji/buildinfo?buildID=112804

Comment 8 cornel panceac 2009-07-15 07:49:03 UTC
ok, i was three weeks in holiday so now, back to office, i can confirm the report from #6.

i will download from koji and report more.

Comment 9 cornel panceac 2009-07-15 08:24:35 UTC
ok, with foomatic 4.0.2-3.fc11.i586, hl1250 works, hpijs works, ljet4 "prints" a blank page as before, and the others (guten*{simplified}* and lj4dith) send data but nothing gets printed.

thank you.

Comment 10 Tim Waugh 2009-07-15 13:05:55 UTC
Great.  So the only remaining problem is that foomatic thinks those other drivers are able to work with this device.

Comment 11 Tim Waugh 2009-08-21 08:53:36 UTC
This is essentially the same as bug #513667.

*** This bug has been marked as a duplicate of bug 513667 ***