GNOME Bugzilla – Bug 407066
Landscape printing doesn't work as expected
Last modified: 2009-08-13 01:04:38 UTC
Please describe the problem: Print preview doesn't respect page orientation setting, and printing doesn't take full advantage of the whole printable area. Steps to reproduce: 1. configure printing as paper=A4, feed orientation=straight, page orientation=landscape 2. choose "print preview" and check that preview is showing content in portrait orientation 3. choose "print"; content actually follows landscape orientation, but gets truncated Actual results: Print preview shows the page itself in landscape orientation, but content is shown in portrait orientation (see screenshot). Going ahead and printing the page actually prints content in landscape orientation (different from the preview), but it gets truncated at the same limit shown on the preview (it doesn't take advantage of the whole printable area). Choosing "feed orientation" as "rotated 90 degrees" corrects preview behavior, but on the other hand prints on paper following portrait orientation, despite the "landscape" setting. Expected results: Print preview should have shown content following landscape orientation, and content should have taken advantage of the whole printable area available. Does this happen every time? Yes Other information: This has been tested on Planner 0.14.1 running on Ubuntu 6.10 (Edgy)
Created attachment 82383 [details] Print preview screenshot showing rotated and truncated content
Created attachment 82384 [details] Print settings used
Confirmed in Ubuntu Feisty, recently upgraded (0.14.2), with Letter-sized sheet.
Confirmed here too with Ubuntu Gutsy, planner 0.14.2.
Since two other people confirmed this (actually, three if you read bug 503562), can anyone change the status of this bug to CONFIRMED? Also, I found one (ugly) workaround: - leave page orientation as "portrait" - set page size as "custom" - manually swap dimensions (i.e. length <--> width)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the development version. The next release will contain this fix. *** This bug has been marked as a duplicate of 385680 ***
*** Bug 572331 has been marked as a duplicate of this bug. ***