Bug 795824

Summary: Postscript error on first document printed on a Brother MFC7820N printer
Product: [Fedora] Fedora Reporter: John Mellor <john.mellor>
Component: foomaticAssignee: Tim Waugh <twaugh>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 20CC: jochen.wiedmann, jpopelka, twaugh
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:35:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
The relevant ppd file, as requested by Tim
none
testpage.ps
none
Simple file that demonstrates the error
none
A pdf file also demonstrating the error none

Description John Mellor 2012-02-21 15:43:58 UTC
Description of problem: Postscript error in first printed document.  Subsequent prints are normal.


Version-Release number of selected component (if applicable):
 cups-1.5.0-22.fc16.x86_64


How reproducible:
 Every time.


Steps to Reproduce:
 1. Turn on printer, allow it to come online.
 2. Print something.
 3. Note the postscript error output.
 4. Print it again.  Note that it now prints correctly.
  
Actual results:
 Single page always printed stating:
    ERROR NAME;
       configurationerror
    COMMAND;
       setpagedevice
    OPERAND STACK;
       --dicttype--

Expected results:
 Normal printed document, as happens on subsequent prints.


Additional info:
 Printer is a popular Brother MFC7820N b/w laser printer/fax/scanner/copier multifunction printer, connected via USB.  Printer works well after the failing first document after initialization.  Platform is a fresh-install of untainted Fedora-16 x86-64 on AMD, fully updated.  Issue did not occur in Fedora-14.

Comment 1 Tim Waugh 2012-02-22 16:24:43 UTC
There are two available drivers for the Brother MFC7820N, as well as the available generic drivers.

What does 'grep ^*NickName: /etc/cups/ppd/*.ppd' say?

Whichever driver you are using, please try using the other:
* Brother MFC-7820N BR-Script3
* Brother MFC-7820N Foomatic/Postscript

You can change the driver using system-config-printer.
https://fedoraproject.org/wiki/How_to_debug_printing_problems#Which_driver_am_I_using.3F

Does using the other driver have any effect?

Comment 2 John Mellor 2012-02-22 17:42:37 UTC
Printer was configured to use the Brother MFC-7820N BR-Script3 ppd file.
Switched to Brother MFC-7820N Foomatic/Postscript ppd, and printed an email.
No change in behaviour.  Both ppd files give the same error on first print.

Comment 3 Tim Waugh 2012-02-23 12:50:57 UTC
Does it happen with everything you print?

Please attach the PPD file from the /etc/cups/ppd/ directory.

Comment 4 John Mellor 2012-02-23 13:50:43 UTC
Created attachment 565306 [details]
The relevant ppd file, as requested by Tim

Comment 5 John Mellor 2012-02-23 13:54:39 UTC
Tim asked:
> Does it happen with everything you print?

It only happens on the first document printed after powering up the printer.  After that, it prints normally.  It also happens the same when using both the postscript and the brotherscript ppd files.  The only difference that I can discern is that the postscript error is printed as text only, and the brotherscript error prints the same error message in a light grey background box.

Comment 6 Tim Waugh 2012-02-27 11:32:32 UTC
Created attachment 566017 [details]
testpage.ps

Please try printing this as the first document after the printer powers on, using the command line below. Does that behave in the same way?

lp -dMFC-7820N -oraw testpage.ps

Comment 8 John Mellor 2012-02-27 13:46:47 UTC
Test file results: That correctly printed the CUPS printer test page, with no error.

Comment 9 Tim Waugh 2012-02-27 14:45:39 UTC
Thanks.  Could you please attach a document that fails when it's the first job the printer receives?

Comment 11 John Mellor 2012-02-27 16:55:17 UTC
Created attachment 566095 [details]
Simple file that demonstrates the error

As requested by Tim: Simple quarter-page text document that demonstrates the problem.  It prints incorrectly the first time, and then works correctly on any subsequent print.

Comment 12 John Mellor 2012-02-27 17:02:22 UTC
Created attachment 566096 [details]
A pdf file also demonstrating the error

Downloaded pdf file that also demonstrates the problem, printed from the gnome document viewer.  To reduce paper use, only print one page.

Comment 13 John Mellor 2012-02-27 17:08:49 UTC
Interesting note: Postscript documents from the Gnome document viewer, such as Tim's CUPS testpage, print correctly on first print.  Pdf, text, or other formats requiring conversion, do not print correctly on first print.

Comment 14 Jochen Wiedmann 2012-03-14 21:01:21 UTC
Had the same issue. According to

   https://bugs.launchpad.net/ubuntu/+source/cups/+bug/306401

I changed the diver to Brother MFC8440D BR-Script 3 and now it seems to work?

Comment 15 Jochen Wiedmann 2012-03-14 21:09:35 UTC
Sorry, the exact driver is (quoting from /etc/cups/printers.conf)

    MakeModel Brother MFC-8440 BR-Script3

Comment 16 Fedora End Of Life 2013-01-16 20:28:13 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 17 Fedora End Of Life 2013-02-13 23:52:00 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 18 John Mellor 2013-02-15 02:13:54 UTC
Problem is still occurring in F18.  Reopening.

Comment 19 Jochen Wiedmann 2013-04-16 16:06:56 UTC
Confirming for F18.

Comment 20 Fedora End Of Life 2013-12-21 15:00:35 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 21 Jochen Wiedmann 2014-01-03 19:28:51 UTC
Please reopen this bug for Fedora 20. Sorry!

Also note the following workaround: Printing works with the following driver:

  HP LaserJet 4050 Series Postscript

Comment 22 Fedora End Of Life 2015-05-29 08:42:58 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 23 Fedora End Of Life 2015-06-30 00:35:26 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.