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 496745 - Print "range" does not reset on closing a document.
Print "range" does not reset on closing a document.
Status: RESOLVED DUPLICATE of bug 488806
Product: evince
Classification: Core
Component: printing
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-14 13:54 UTC by Aidan Delaney
Modified: 2007-12-17 21:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Aidan Delaney 2007-11-14 13:54:20 UTC
When printing a document, say A.pdf, I may choose to print a range of pages numbered 7-13.  After closing the instance of evince holding A.pdf, I open an instance containing B.pdf.  I click print.  This prints the range 7-13 of B.pdf (even if B is only one page long i.e. it prints nothing).

This is confusing.  I'd expect
a) print ranges are associated with documents, or preferably
b) the default option of "All" is selected instead of "Range" i.e. the range of pages to print is only set for one session when I'm working with the document.

(b) is my preferred option as I regularly work with the same PDF/PS documents (my thesis) and want to print the whole thing one day, and just a range the next.  If I print a range today and then don't open it untill next week, I'll have forgotten that the range is selected and expect the whole document to be printed.

Ubuntu 7.10 (Gutsy Gibbon).
Comment 1 Carlos Garcia Campos 2007-12-17 21:55:24 UTC
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. It should be solved in the next software version. You may want to check for a software upgrade.


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