Comment 9 for bug 242842

Craig, you are right that my problem most certainly is not a duplicate of the bug discussed here, but a separate problem.

Even though it might be totally unrelated to your problem, I do not think my test is invalid in general, because it results in world-writable files that most certainly are not intended. It should thus probably be moved to a separate thread.

The thing I wanted to demonstrate is:
- after loggin in the umask is set to 022 because it is set to 022 in /etc/profile and not changed somewhere else. my somewhat incompetent way of determining this is to open a terminal and run umask.
- then i open my home folder in thunar and create a new folder using the right-click menu. i think thunar is responsible for creating the directory at this point, but i might be mistaken because i am a gnome user usually.

and from that point on the problem is:
1) when creating further folder/files using right-click-menu they are created world-writable
2) when trying to determine my umask as described above, i find it is 000 now

1) this is a bug. even if my theory about the umask is complete nonesense, this is a obvious, serious, plain bug.
2) i do not know how bad my method of determining the umask is, but i think the reason that i get 000 there is that it actually is 000 and bash (zsh to be precise) inherited it from xfce terminal that inherited it from thunar. and i dont know where thunar got it from, but that is what i postulate to be the underlying bug. this theory is supported by the observation that if i launch a gnome-terminal from the xfce terminal and run umask there i get 022 again, because this breaks the chain of inheritance somehow.