Please describe the problem:
Using Gimp 2.6.6 on Ubuntu 8.04 (Hardy) Linux.

(In my experience) When creating (saving new, untitled) TIFF (.tif) files, the files are being created with permissions of Creating as 644 (rw-r--r--) when should be 664 (rw-rw-r--).

=== 

On Gimp-developer list, 10 April 2009, Martin Nordholts stated the following in reply to my query on this problem:

"This happens to me as well and from looking at the code it also happens 
for gbr, gih, pat, pnm and raw which opens a file for writing like this:

  fd = g_open (filename, O_CREAT | O_TRUNC | O_WRONLY | _O_BINARY, 0644);

E.g png instead uses

  fp = g_fopen (filename, "wb");

This inconsistency doesn't make any sense, feel free to open a bug 
report. The latter is identical to the former apart from the 
permissions, so we probably want to use the latter for all plug-ins."

===

On two different workstations, being run by two different login users, creating files in various different directories, Gimp is creating the files with permissions that are incorrectly too restrictive:

  Gimp is making as 644:

  -rw-r--r--  1 jay jsa  1919194 2009-03-31 12:10 tmp.tif

  When it should be making as 664:

  -rw-rw-r--  1 jay jsa  1919194 2009-03-31 12:10 tmp.tif

Only Gimp is doing this.

Creating files in the exact same manner and saving them to test.png or test.jpg results in _correct_ permissions.  (It only is a problem with .tif files so far in my testing, but above Martin Nordholts reports the problem with certain other filetypes as well.)

a) The directories that the files are being created in have perms of 6775:

   drwsrwsr-x  3 jay     jsa     4096 2007-05-28 15:57 testdir

   Files created in a directory with those perms are _supposed_ to be
created as 664 which is rw-rw-r--.

b) When any other program, such as vi or touch, makes a file in the very same directory, it is making the perms correctly (664).

c) I have double checked the user's umask which is correctly 0002 which would result in correct file creation as 664.

d) We have never had this problem with any other program (when the directory perms are correct, which they are in this case).

e) An associate on a completely different, but virtually identically configured Ubuntu linux system (all same versions). has been able to replicate the exact same problem.

Steps to reproduce:
1. Create a new image file in Gimp.

2. Save the image file as a TIFF .tif file, in a directory that has perms that would normally cause a file to be created with perms of 664 rw-rw-r--. 



Actual results:
The file is saved with perms of 644 or rw-r--r--.

Expected results:
The file should be saved with perms of 664 or rw-rw-r--.

Does this happen every time?
Yes for .tif files.  Another reporter (see above) says that it is also happening for: gbr, gih, pat, pnm and raw. 

Other information:
In a multi-user workflow, this is a major annoyance as files cannot be edited by the next user without first changing permissions.