GNOME Bugzilla – Bug 664672
Print settings are not saved on a per printer base
Last modified: 2018-05-22 14:24:37 UTC
I use Xubuntu 11.10 (64bit), the printing system is cups 1.5.0-8ubuntu4. I have an postscript HP color laserjet printer with duplex option. To avoid unnecessary color or non-duplex prints I have four printers configured in CUPS (duplex/non-duplex - color/gray). Whenever I do a modification in the printer settings (e.g. a color option), this has not only effect on the currently selected printer but on all other printers as well. This means, with the next execution of Evince this modified setting is still present - even if I do not want it. Example: I have modified the paper tray with my COLOR-DUPLEX printer. This will not only change the paper tray setting but also the color setting for my GRAY-NON-DUPLEX printer with the next print. For me it looks as if the printer configuration in the file ~/.config/evince/print-settings does not hold its information on a per printer base. This means, when modifying the paper tray this leads also to entries that are related to color settings. But this is not what I was attended to modify... My proposal is now: It should be possible to skip the saving of the printer configuration. The general printer configuration is done with CUPS and this should fit. With Evince I do only special modifications of the printer configuration that are related to specific documents. This modification of the printer configuration never claims to be general for other documents. Or it should be possible to save the printer configuration on a per printer base. Thanks for any support on that issue! Best regards Mathias
Bug 773458 was marked a duplicate of this. A slight difference was that I was asking for a way to prevent settings being remembered at all, not just to remember then on a per-printer basis.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/253.