Bug 262197

Summary:	mail-client/evolution-2.22.3.1: Page size when printing always reverts to A4 when printing
Product:	Gentoo Linux	Reporter:	Dan Ost <danost>
Component:	Current packages	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Dan Ost 2009-03-11 20:47:09 UTC

Any time I attempt to print an email from evolution v2.22.3.1, it sets the page size to A4. When I go into File->PageSetup, the page size is always set to A4. Changing the page size to 'US Letter' (or anything else) and hitting 'Apply' seems to work (if I open PageSetup again, it shows my selection), but as soon as I attempt to print, it reverts back to A4 (the printer complains that there is no A4 paper loaded and A4 is the page size shown in PageSetup).

I use CUPS for printing and each of my printers has 'Letter' as the Media Type.



Reproducible: Always

Steps to Reproduce:
1. select email to print
2. set page size to 'US Letter' in file->page setup
3. attempt to print


Actual Results:  
Check file->page setup and see that page size has reverted back to A4.
Alternatively, check your printer. If you don't have A4 paper loaded, it is likely complaining.

Expected Results:  
file->page setup should still list page size as 'US Letter' and if you successfully printed anything, it should have been on Letter paper.

Comment 1 Gilles Dartiguelongue (RETIRED) gentoo-dev

2009-03-14 22:22:43 UTC

I think this bug is specific to 2.22 (or was it 2.20) and happened due to incomplete migration to GtkPrint API. It should be fixed in 2.24 at least.

Comment 2 Dan Ost 2009-03-16 15:50:48 UTC

(In reply to comment #1)
> I think this bug is specific to 2.22 (or was it 2.20) and happened due to
> incomplete migration to GtkPrint API. It should be fixed in 2.24 at least.
> 

I can verify that it is fixed in 2.24.5

Comment 3 Dan Ost 2009-03-17 18:54:37 UTC

Out of curiosity, when will this bug be closed? It's fixed in 2.24 (which is now stable), so is the plan to let this bug remain open until 2.22 is retired from portage?

I'm assuming that there will be no effort made to actually fix 2.22.

Comment 4 Rémi Cardona (RETIRED) gentoo-dev

2009-03-17 19:15:26 UTC

Closing then.

Thanks for the follow up.