RSS/Atom feed Twitter
Site is read-only, email is disabled

File Creation Permission Problem ONLY for TIF files: Creating as 644 (rw-r--r--) when should be 664 (rw-rw-r--)

This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

1 of 1 message available
Toggle history

Please log in to manage your subscriptions.

File Creation Permission Problem ONLY for TIF files: Creating as 644 (rw-r--r--) when should be 664 (rw-rw-r--) Jay Smith 01 Apr 20:50
Jay Smith
2009-04-01 20:50:27 UTC (almost 16 years ago)

File Creation Permission Problem ONLY for TIF files: Creating as 644 (rw-r--r--) when should be 664 (rw-rw-r--)

Using Gimp 2.6.6 on Ubuntu 8.04 (Hardy) Linux.

TIFF ONLY ---- This problem seems *only* to be happening when creating/saving TIFF (.tif) files. If the filetype is something else, then the problem is not happening.

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).

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.

c) I have double checked the user's umask which is correctly 0002 which would result in 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.

???

1) Is this a (known?) bug?

2) Is this configurable somewhere in Gimp? I can't find it if it is.

3) Is this configurable somehow in the .gimp* rc files and/or from the command line?

Jay