Thunar sets wrong permissions for new files and directories (666, 777)
Bug #391969 reported by
stitch
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Thunar File Manager |
Unknown
|
Unknown
|
|||
thunar (Ubuntu) |
Fix Released
|
Medium
|
Lionel Le Folgoc |
Bug Description
Ubuntu Jaunty: When creating a new directory with thunar the first time during an X session, the permission is 755. But if the second directory is created, its permission is 777 and now, file permissions for new files are 666. Using a terminal, the expected permissions (755 and 644) are used. Starting thunar from the terminal does not solve the problem.
visibility: | private → public |
Changed in thunar (Ubuntu): | |
status: | Triaged → Fix Committed |
assignee: | nobody → Lionel Le Folgoc (mrpouit) |
To post a comment you must log in.
This is confirmed on Karmic. Steps to reproduce:
1. create a toplevel directory under $HOME (eg 'foo')
2. create a file in the 'foo' directory
$ ls -ld /home/jamie/foo/ /home/jamie/foo/bar
drwxrwxrwx 2 jamie jamie 4096 2009-06-26 10:06 /home/jamie/foo/
-rw-rw-rw- 1 jamie jamie 0 2009-06-26 10:06 /home/jamie/foo/bar
$ umask
0022
At the very least, thunar should honor umask.