Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 454993

Summary: print twice with HP Laserjet 4000 Series Postscript
Product: [Fedora] Fedora Reporter: Ivan Cheniot <ivan.cheniot>
Component: cupsAssignee: Tim Waugh <twaugh>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 9CC: david
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-08-24 03:32:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ivan Cheniot 2008-07-11 10:50:57 UTC
Description of problem:

print twice using HP Laserjet 4000 Series Postscript (recommended) on a HP
Laserjet 4000n connected on printer port (may have the same problem whatever the

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

How reproducible:

Steps to Reproduce:
1. connect a HP Laserjet 4000n to the printer port of your computer and turn it on
2. create a printer in cups. Select HP Laserjet 4000 Series Postscript (recommended)
3. print the Cups test page
Actual results:

print 2 Cups test pages

Expected results:

print 1 Cups test page

Additional info:

Comment 1 Tim Waugh 2008-07-11 11:12:00 UTC
Please use the printing troubleshooter.  Select System->Administration->Printing
from the main menu, then Help->Troubleshoot from the menu bar.

It may give you the opportunity to save a 'troubleshoot.txt' file -- if so,
please attach that file to this bug report.

Comment 2 David Nalley 2008-08-24 03:32:55 UTC
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.