Comment 11 for bug 134671

Patrice Vetsel suggested to change Label 0 to Label 1, which works as expected, it adds the Job number to the file name.

What it doesn't tell you is that the job number is not guaranteed to be unique as far as I know, so there is a possibility of the same job and file name overwriting, which is going to be extremely hard to notice because it won't likely happen that often.

Personally I think that the preference should be:
Overwrite 0 - no, never overwrite an existing file, create a unique name
Overwrite 1 - yes, if a file exists with the same name, overwrite it

The biggest challenge in all these discussions are that it is likely that Server users and Workstation users have different requirements. Likely they'll conflict - for example, a Workstation user has access to a notification method like d-bus, but I'm pretty sure that there is no mechanism for a Server process to notify a user on their workstation - given that the workstation could be running any OS.

From reading reports about this and related issues I can only suggest that the issue is not if the behaviour is buggy or not, rather that each person has a different expected behaviour. As I see it, fixing this bug is one of "Expectation Management", rather than fixing an actual bug - other than the unexpected behaviour I've documented above.