Print range does not default back to "all" for each seperate document resulting in blank pages being printed

This is for sure not a problem of gnome-cups-manager. gnome-cups-manager is a printer setup tool. It is for configuring a printer (connection type, driver, default settings, ...). If you choose "Print" in an application, the application's printing dialog is opened. So the bug is either in the application (if the dialog is part of the application) or part of some library providing a printing dialog to the application. We need to with which applications the problem occurs for you so that we can find out in which package the bug has to get fixed.

The print range should really not saved on an application/user/system-wide basis. It can be saved as an attribute of the document perhaps. This needs to be fixed in the printing dialog.

Sorry for the confusion. I guess it only happens in evince or, as you suggest, whatever library they use to print.

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=485521

comment on the upstream bug

"Print settings are persistent, like in many other apps. However, I agree evince
shouldn't print blank pages when an invalid range is used. It should be fixed
in trunk and gnome-2-20 branches now.

Thanks for reporting. "

 evince (2.20.1-0ubuntu1) gutsy-proposed; urgency=low
 .
   * New upstream release:
     - Bug fixes:
       - Printing multiple pages per sheet fixes
       - Respect ranges order during print (LP: #137241, #150940)
       - Silently ignore unknown form fields (LP: #140907)
       - Do not show the toolbar in fullscreen mode if the main toolbar
         is not visible
       - Give priority to form fields over images
     - Translations: ko, it, fi, da
   * debian/patches/80_from_svn_fullscreen_respect_toolbar_option.patch:
     - Dropped as got fixed upstream
   * debian/patches/81_from_svn_edit_images_forms.patch:
     - Dropped as got fixed upstreamg

the gutsy-proposed upload has been moved to gutsy-updates now

This bug is definitely fixed now. Unfortunately, the solution is almost as bad - now there's no notification when an invalid range is specified. I've had issues with my printer in the past (stupid proprietary driver) so I started looking there when nothing printed. It took me a while to realize that I was trying to print page two of a one-page document. An error message would be appreciated.

I don't think this is fixed, unless there is a new version that hasn't come through the update channels yet. If this is the case, please let me know how to get the fixed version.

There's no reason why if I choose to print pages 34-52 of one document that it should be assumed that I want to print the same range of a completely new document. What ends up happening is the next time I try to print an entire document but don't notice that my previous range was saved and only that range prints out, so I have to go back in and set a new range of all the pages that didn't print the first time. It ends up going like this forever until I learn to check each time. It would be one thing if this were a systemwide standard that the settings are preserved, but the fact is that it isn't.

Shoofy is absolutely right and I don't think that anyone would ever want the print range to be remembered particularly not for a completely new document. I am not aware of any other application that remembers the page range.

I've added a comment upstream about the range storing

upstream commented saying that the settings are stored by document, do you think it makes sense in this context?

It certainly makes more sense than storing them globally, but making the print setting persistent per document seems to me to be a change that should be made globally across all relevant Gnome apps or not at all. It doesn't make any more sense in evince than it does in OpenOffice.org or any other app that prints documents, so for the sake of user comfort I think adding this feature just to Evince would be confusing.

the bug should be fixed in hardy, feel free to reopen if you still get the issue using the new versions though