After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 550804 - Multipage memo only prints first page
Multipage memo only prints first page
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Memos
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-09-04 09:19 UTC by Nick Jenkins
Modified: 2009-02-17 04:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Nick Jenkins 2008-09-04 09:19:25 UTC
Please describe the problem:
In Evolution 2.22.3.1, I have a memo with a list of passwords and web sites for use when traveling, and this memo runs for two or 3 pages. When printed, only the first page of the memo gets printed. The rest of the memo is not printed / is cropped off / is lost.

Steps to reproduce:
1. create or find a memo that runs for several pages.
2. Right click on the memo and choose "print".
3. Observe that only the first page is printed (at least for me).


Actual results:
Only one page is printed.

Expected results:
All of the pages to be printed.

Does this happen every time?
It seems to be reproducible. I have tried it 3 times now, and it happens every time.

Other information:
In the print dialog, under "Print Pages", I have "All" selected, and do not have "Current" or "Range" selected.
Comment 1 Matthew Barnes 2009-02-17 02:24:29 UTC
Worked fine for me with Evolution 2.25.91.  All pages printed.

Can you please retest with 2.24 or later?
Comment 2 Nick Jenkins 2009-02-17 04:48:52 UTC
Yes, thank you for the heads up! Have retested on 2.24.3, and it works great (all pages print). Just to confirm I wasn't imagining stuff, I retested on the old version (2.22.3.1), and the same steps only give one page of printer output. I.e. looks like this was resolved at some stage between v2.22.3.1 and v2.24.3. Setting bug's status to Resolved / Fixed, and thanks once again.