Bug 155323 - Duplex not working on HP Lasterjet 2300
Duplex not working on HP Lasterjet 2300
Status: CLOSED DUPLICATE of bug 151645
Product: Fedora
Classification: Fedora
Component: foomatic (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2005-04-19 03:56 EDT by Dennis Björklund
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-20 10:06:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dennis Björklund 2005-04-19 03:56:16 EDT
Description of problem:

Duplex printing does not work on HP Lasterjet 2300 using the latest upgrade of
foomatic for FC3. The original version works fine.

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

works:       foomatic-3.0.2-3.i386.rpm
do not work: foomatic-3.0.2-13.3.i386.rpm

How reproducible:


Steps to Reproduce:

1. Start system-config-printer-gui
2. Select the printer (laserjet 2300)
3. Select menu "Test->Duplex test"
Actual results:

2 pages printed

Expected results:

1 page printed with text on both sides, aka duplex printing :-)

Additional info:

The printer is configured to use postscript 3.
Comment 1 Tim Waugh 2005-04-19 11:34:48 EDT

Please save this attachment and copy it to:


Does this solve the problem?
Comment 2 Tim Niemueller 2005-04-19 12:34:11 EDT
The same here for an HP 4200dtn, duplex printing is not working. The duplex test
prints two pages instead of one. If works if I reinstall the original foomatic
version that came with the FC3 release.

# rpm -q foomatic

The changed Postscript.xml file does not cure the problem for me.
Comment 3 Tim Waugh 2005-04-19 12:35:20 EDT
I forgot to mention: after copying the file, please rebuild the queues using
this command as root:

/usr/sbin/printconf-backend --force-rebuild

Does the problem still persist?
Comment 4 Tim Niemueller 2005-04-19 12:41:59 EDT
Copying the file and calling the rebuild fixes the problem. Thanks!
Comment 5 Dennis Björklund 2005-04-20 02:43:34 EDT
That solved it for me as well. Great!
Comment 6 Tim Waugh 2005-04-20 10:06:03 EDT

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

Note You need to log in before you can comment on or make changes to this bug.