As subject line. Verified a second time by checking a pre-UP7 installation using the same procedure as set out below, which worked fine, applying UP7, then seeing it fail as described below.
Environment: Linux [machine_name] 3.10-2-amd64 #1 SMP Debian 3.10.5-1 (2013-08-07) x86_64 GNU/Linux, Pluma 1.6.0 and Mozilla Firefox 24.0
Steps to reproduce: (Pluma is only used as an easy example of an application that should be able to print to file. This problem isn't specific to Pluma. Printing to PDF fails in the same or similar way with any application that doesn't have its own PDF print driver.)
1. Open Pluma, type some text.
2. Select File - Print - "General" tab - Output format: PDF
3. Enter a file name and select a directory to generate it in.
4. Click Print. File is generated as expected. So far so good.
5. Delete the PDF file just generated.
6. Again, select File - Print - "General" tab - Output format: PDF. File name and output directory will still be the same as in step 3.
7. Click Print.
Expected behaviour: PDF file is generated in the same way as it was in step 4. Observed behaviour: No PDF file is generated, and Pluma raises a model dialog box saying: "Error printing Operation not supported"
8. Close the modal dialog box.
9. Select File - Print - "General" tab.
Expected behaviour: Pluma raises the "Print" dialog box, shows the file name used in steps 3 and 6 in the "Name" field and the directory used in steps 3 and 6 in the "Save in folder:" dropdown. Observed behaviour: "Name" field is empty, "Save in folder:" dropdown shows "(None)".
10. Manually enter same filename and select same directory as in steps 3 and 6, then click "Print". PDF file will be generated again.
11. Go to step 5, lather, rinse, repeat.
To summarize: Every *second* attempt to print to PDF will fail, no matter whether the specified file already exists or not.
Another application with which to easily demonstrate this is Mozilla Firefox, which will also fail on the second and every subsequent attempt to print, but silently, without any error message.
This is extremely confusing to users, particularly in case of silent failures. Any ideas on how to fix it would be appreciated.