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 564051 - "Page Setup" printer configuration has no effect
"Page Setup" printer configuration has no effect
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Printing
2.14.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-12-10 23:37 UTC by Bogdan Calmac
Modified: 2018-02-10 03:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bogdan Calmac 2008-12-10 23:37:53 UTC
Please describe the problem:
The changes to printer selection and printer properties from the "Page Setup" dialog are not saved. When you open it a second time the same defaults appear.

On a related note, printer configuration done through "Print" is also not persisted from one menu invocation to the next (while in the same document)

Steps to reproduce:
1. Open File->Page Setup->Printer
2. Select a printer other than the default (or change printer properties)
3. OK
4. Open File->Page Setup->Printer again
5. The changes made earlier are lost


Actual results:
Printer configuration is lost (and you end up wasting photo paper by using the default text printing configuration)

Expected results:
Printer configuration changes made through "Page Setup" or "Print" should be preserved at least for the life of the current document.

Does this happen every time?
Yes.

Other information:
It happens with any printer, real or virtual (like PDF Creator). It is not a system issue. Doing the same thing with Photoshop works as expected. 

The environment is WindowsXP SP2
Comment 1 Michael Schumacher 2008-12-11 11:02:54 UTC
Yes, confirming. They should at least be kept for the current session.
Comment 2 Bogdan Calmac 2008-12-11 15:12:51 UTC
Also, adding to the above, the printer configuration changes are discarded even during a single invocation of the "Print" dialog:

1. Open File -> Print
2. Change printer settings for photo
3. OK

The photo will be printed with the default properties. To sum it up, the printer configuration cannot be changed at all.
Comment 3 Sven Neumann 2008-12-14 18:46:41 UTC
Everything is saved across sessions. If this doesn't work for you, then this is a problem on the Windows platform. Are you sure this is not just a duplicate of bug #505123 or one of the many other bug reports on the GTK+ product?
Comment 4 Sven Neumann 2008-12-14 19:11:14 UTC
You can check what's saved in ~/.gimp-2.6/print-page-setup. As far as I know the printer selection is not supposed to be saved. Only the paper selection is relevant.
Comment 5 Bogdan Calmac 2008-12-14 19:22:52 UTC
Here is print-page-setup:


[print-page-setup]
PPDName=Letter
DisplayName=US Letter
Width=215.89999389648437
Height=279.39999389648438
MarginTop=2.9464000000000001
MarginBottom=2.9464000000000001
MarginLeft=2.9464000000000001
MarginRight=2.9464000000000001
Orientation=landscape


and also print-sttings:


[meta]
major-version=0
minor-version=4

[print-settings]
win32-paper-size=285
use-color=true
print-pages=all
media-type=stationery
dither=error-diffusion
collate=false
n-copies=1
printer=EPSON Stylus NX400 Series
default-source=auto
duplex=simplex
win32-driver-version=1296
win32-driver-extra=ABAJBEUAUABTAE8ATgAgAFMAdAB5AGwAdQBzACAATgBYADQAMAAwACAAUwBlAHIAaQBlAHMAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAwQFAQAAAAAAAAAAAAAAAAAABQABAAYABgABAP//AwBnAQAAAQACAAAABAAGANwABgAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAABwAAAAUAAAABAAAAAAEAAAEAAAAAAAAAAAAAAAYAAAAUAgAAyAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAE8AcABlAG4AIABjAGYAZwAgAGYAaQBsAGUAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAIAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABSAwAATAQAAAIAHQEAAAAA0AIAANACAADQCwAAuBEAAPQCAAD0AgAA0AsAAJYRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANALAAC4EQAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAIAAAAAAAAAaQAAAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
win32-media-type=359
win32-dither-type=5
orientation=portrait
win32-default-source=259


But the issue here is not really that the print settings are not saved from one session to the next, but rather that they are discarded completely. As I was saying before, if I open the print dialog, change the printer settings to use photo paper and print at high quality and then print, the result is like I used the defaults of regular paper and normal quality. The fact that I changed the printer setting during the process did not matter at all.

I don't have the expertise to say whether this is a GIMP or GTK+ issue, but it certainly is not a Windows or printer driver issue. When I do the same thing with the windows print wizard or Photoshop, everything works as expected.
Comment 6 Joachim Frieben 2009-01-10 15:56:42 UTC
In contrast with the original report, GTK 2.14.7 behaves differently for me: when opening the page setup dialog, "Any Printer" is the default setting which is much worse than pre-selecting the system default printer.
Comment 7 Vincent Untz 2009-01-20 16:43:56 UTC
openSUSE bug about this: https://bugzilla.novell.com/show_bug.cgi?id=465213
Comment 8 Wolfgang Rosenauer 2009-02-05 11:10:35 UTC
I've opened the report @ Novell and I propose to read the referenced link.
This issue stops me from being able to print to normal photo paper from Gimp which is quite a major issue.
I'm happy to provide whatever information is needed. But that's neither Windows only nor priority "Normal" IMHO.
Comment 9 Andreas J. Guelzow 2009-03-11 05:52:47 UTC
I would not be surprised if this were related to #423484: There seem to be several copies of the print settings in play.
Comment 10 Matthias Clasen 2018-02-10 03:25:57 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.