Bug 194580 - Since upgrading from FC4 to FC5 "lpr file" always prints in Landscape
Summary: Since upgrading from FC4 to FC5 "lpr file" always prints in Landscape
Keywords:
Status: CLOSED DUPLICATE of bug 195532
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 5
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC6Target
TreeView+ depends on / blocked
 
Reported: 2006-06-14 07:48 UTC by Kern Sibbald
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-06-20 10:14:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kern Sibbald 2006-06-14 07:48:57 UTC
Description of problem:
If I send a file to my Postscript printer directly with "lpr filename", it 
always prints the output in Landscape orientation rather than Portrait.


Version-Release number of selected component (if applicable):
FC5
cups-1.2.1-1.9

How reproducible:
Print any file using the "lpr" command.  Note, if I print using OpenOffice or 
Konqueror, the output is formatted correctly.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
This is a network printer Dell 3100cn, and in checking all the places I know 
(control panel, web access to the printer) for setting the orientation, they 
are all set to Portrait, including the values stored in the printer.  The 
printer has worked perfectly fine for a long time under FC4.

I defined this same printer on a different FC5 that was installed rather than 
upgraded, and it works just fine, so that implies something got messed up in 
the upgrade.

I removed /etc/cups, reinstalled all the cups rpms using --force, and 
redefined the printer using the ppd from the FC5 system where printing works 
correctly, but the problem still exists -- all "lpr filename" commands print 
in Landscape.

Comment 1 Tim Waugh 2006-06-20 10:14:52 UTC

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


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