GNOME Bugzilla – Bug 597098
Number of saved copies should not be saved for next printing attempt.
Last modified: 2018-04-15 00:30:09 UTC
Dear GNOME hackers, I printed a document with Evince and choose three copies. Next time I wanted to print this document, I was surprised that it was printed several times. In my opinion, the numbers of copies should always be reset to 1, because the next startup, for example several days later, the user will not remember that he changed the number of copies. Note, the settings are saved per document by Evince. I do not know when this feature was introduced and if it is a feature of gnome-print or Evince. Please reassign, if it belongs to Evince. The same goes for the page to print also. I would always leave it to »All pages.«. Although one could argue, that this should just be reset per Evince/program session and not printing dialogue call. Thanks, Paul
Is this still an issue in GNOME 2.30/2.32?
(In reply to comment #1) > Is this still an issue in GNOME 2.30/2.32? Yes it is at least in GNOME 2.30 (Debian Sid/unstable). I easily reproduced it by opening a PDF document with Evince, printing three copies using CUPS PDF printer (not necessary anymore because printing to PDF is supported directly now), closing Evince and opening the same document. Three copies were now the default value for the number of copies in the print dialogue. PS: I cannot change the status to »unconfirmed« since I changed my address a while back und Bugzilla seems to have a bug and does not recognize this.
In 2.30 Evince uses gtk+ printing and not libgnomeprint anymore.
Paul any news?
(In reply to comment #4) > Paul any news? As written in comment #2. I am still able to reproduce this bug, but I am not able to change the status or reassign this ticket to gtk+ printing, since I do not have the rights to do so. You tried to change the Status field from NEEDINFO to UNCONFIRMED , but only the assignee or reporter of the bug, or a user with the required permissions may change that field. André, Fabio, could you please do that.
André I have a question you should reassign it to gtk? because the description of the bug exists. and also I think it should be a enhancement.
Assigning to GTK+. I also see this issue and I do think it's annoying. GTK+ Maintainers: Please set to NEW if this is an issue worth fixing or set to WONTFIX if not.
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new