Red Hat Bugzilla – Bug 479724
F-Spot doesn't respect umask when it creates files
Last modified: 2009-07-30 15:22:53 EDT
When modifying files, the new files don't have my current umask (0002) and instead get created with a mode of 0620. This is problematic for me as the files need to be accessible to the group in order to be accessed.
Forgot to mention that I found a similar bug reported against Mono in Ubuntu that was fixed late last year, but it seems like that was in Mono 1.2:
I've tried to reproduce the problem on an F10 and F11 system (x86) but without success so far.
I did the following:
- start an xterm
- umask 0000
- edit a picture (e.g. use the Sepia Tone filter)
- check the newly created files - they should have 0666 as permission
So far the umask was always honored correctly.
Please can you provide some more information an/or do some tests?
1. Does it still happens on a fullly updated system?
2. Can you try whether it happens for you on a x86 (32bit) as well?
3. Try the attached test program:
- gmcs umask-test.cs
- umask 0000
- run the program - it will generate a file "umask-test.tmp":
- check the permissions of this file
Created attachment 353898 [details]
small mono test utility to check whether mono obeys the user's umask
Sorry, I'm not in a position to test this out any more. Feel free to close.