© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Christian, thanks for your excellent summary.
Indeed, gnome-terminal is not at fault (and thanks for suggesting the bug be reassigned).
You've given a much better characterization of the bug than I have managed:
"The issue here is simply that .profile isn't involved in how systemd --user sets up the umask."
This is the bug that needs to be fixed: from a GNOME user's point of view, systemd is an implementation detail, which has now (unfortunately) become visible: a classic leaky abstraction.
So GNOME needs to be fixed so that the entire user session is always run in the scope of the user's .profile.
I would add once more that this is not just about the umask: environment variables, ulimit settings; in general, any and all environment settings that are normally respected should be preserved. I will retitle the bug to reflect this.