[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Tags removed: focal ** Summary changed: - gnome-terminal unduly forces umask=0022 + 'systemd --user' unduly forces umask=0022 ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Changed in: dbus (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-session Status: New => Invalid ** Changed in: nautilus Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: 'systemd --user' unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
@eurbah 245.4-4ubuntu1 fixed the issue in systemd. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
With systemd version 245.2-1ubuntu2 from Ubuntu 20.04 Beta (Focal Fossa), the issue is still the same. ** Tags added: eoan focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
I think it's an systemd issue, which is already reported on GitHub but not fixed yet: https://github.com/systemd/systemd/issues/6077 ** Bug watch added: github.com/systemd/systemd/issues #6077 https://github.com/systemd/systemd/issues/6077 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Hello, thanks but this setting only works in the terminal. Files or folders created from the GUI (GEdit, Nautilus ...) do not respect this UMASK :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Sven, here are the workaround steps (as root) : 1) Create the folder '/etc/systemd/user/gnome-terminal-server.service.d' (with usual mode 755). 2) In this newly created folder, create the 'umask.conf' file with following content : [Service] UMask= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
is there now a solution that works under Ubuntu 19.10? /etc/systemd/user/gnome-terminal-server.service.d/umask.conf The path from "gnome-terminal-server.service.d" does not exist here at all. The problem should be solved after such a long time :-( Is there a plan how the problem can be solved? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Launchpad has imported 57 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=780622. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-03-27T21:38:07+00:00 Reuben Thomas wrote: I set my umask in my .profile to 0027. When I run most applications in my GNOME session, e.g. Emacs, or another terminal, such as xterm, the umask within is 0027. When I run gnome-terminal (3.18.3, Ubuntu 16.04), my umask is 0002. As far as I can tell, I am starting gnome-terminal and xterm (also tried uxterm) in the same way. Both are configured not to start a login shell. If I run "umask" at the top of my .bashrc, in gnome-terminal it prints 0002, and in xterm, 0027. If I run xterm from within gnome-terminal, the umask remains 0002. Running gnome-terminal.real directly has the same effect. I tried killing gnome-terminal-server and running gnome-terminal: same result. If I set the umask in my .bashrc, then the setting is respected. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1685754/comments/0 On 2017-03-27T21:50:36+00:00 Chpe wrote: (In reply to Reuben Thomas from comment #0) > I set my umask in my .profile to 0027. [...] > Both are configured not to start a login shell. There's the solution: .profile is only sourced for login shells (at least on debian derived distributions). Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1685754/comments/1 On 2017-03-28T00:59:08+00:00 Reuben Thomas wrote: Thanks for your reply. I am sorry, I tried very hard to be clear, but obviously failed. .profile is run at login, and sets various environment variables. These are all correctly set in gnome-terminal and xterm. As I said previously, neither gnome-terminal nor xterm is configured to start a login shell. Yet in xterm both the environment variables (which are only set in .profile) and umask are correctly set, whereas in gnome- terminal only the environment variables are set correctly, and the umask has been changed to a different value. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1685754/comments/2 On 2017-03-28T01:08:04+00:00 Reuben Thomas wrote: Just to confirm: /etc/gdm/Xsession on my Ubuntu system contains the lines: # First read /etc/profile and .profile for file in /etc/profile "$HOME/.profile"; do if [ -f "$file" ]; then source_with_error_check "$file" fi done Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1685754/comments/3 On 2017-03-28T08:54:37+00:00 Reuben Thomas wrote: Some additional information, for the sake of clarity: umask(2) says: A child process created via fork(2) inherits its parent's umask. The umask is left unchanged by execve(2). I am assuming therefore that my umask having been set, by my .profile, by /etc/gdm/Xsession, that the same process will (eventually) start gnome-terminal-server (via gnome-terminal), and that therefore the umask I set should be inherited (as occurs with xterm). This is why I believe that something has changed the umask. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1685754/comments/4 On 2017-03-28T09:01:19+00:00 Egmont Koblinger wrote: Neither vte's nor gnome-terminal's code has any umask() calls. If I start gnome-terminal (no previous instance running) from my xterm with a weird one-off umask manually set in that xterm, my umask gets reset to my preferred value in g-t. If I start the server manually and then a client(*) then that weird umask is preserved. (*)The two commands shown at https://wiki.gnome.org/Apps/Terminal/Debugging, without the gdb bits. So it must have something to do with the dbus activation, it's probably dbus (or a closely related component) that decides on the umask. (Remotely reminds me of https://bugs.launchpad.net/terminator/+bug/1646034.) Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1685754/comments/5 On 2017-03-28T09:09:07+00:00 Egmont Koblinger wrote: Just for the record: Could you please check the umask of your gnome- terminal-server process? grep Umask /proc/$(pidof gnome-terminal-server)/status Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1685754/comments/6
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
i have the same problem in Ubuntu 19.10 :-( with best -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Is there any workaround for Nautilus? I tried with /etc/systemd/user/nautilus.service.d/umask.conf and /etc/systemd/user/Nautilus.service.d/umask.conf but nothing seems to work. Thanks in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Changed in: gnome-terminal Importance: Medium => Unknown ** Changed in: gnome-terminal Status: Confirmed => Unknown ** Changed in: gnome-terminal Remote watch: GNOME Bug Tracker #780622 => bugzilla.gnome.org/ #780622 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Thanks for your answer and prompt support. I tried again and find my mistake, i am using models for test that are just a copy of file without changing models permissions, without models and just create empty document and directory IT WORK :-). I confirm that the workaround is effective on 18.04.3 LTS and 19.04. Thanks again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
In order that gnome-terminal starts with the correct umask : Lot of thanks to Olivier JOLY for comment #27 : His workaround is effective. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
I move too Ubuntu 19.04 and we are still affected by this bug, into multi users professional environment we usually just use LTS, but try to solve this issue without success. ;-( Try also without success : === A workaround for those of us that need a solution now is to place [Service] UMask= in $HOME/.config/systemd/user/gnome-terminal-server.service.d/umask.conf for an individual user or in /etc/systemd/user/gnome-terminal-server.service.d/umask.conf == -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Ah, OK, thanks. No news since 2018-08 then - I was hoping the GNOME GitLab would have something new :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Currently, the upstream issue has NOT been migrated to GNOME GitLab yet, but is still being tracked at https://bugzilla.gnome.org/show_bug.cgi?id=780622 ** Bug watch added: bugzilla.gnome.org/ #780622 https://bugzilla.gnome.org/show_bug.cgi?id=780622 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Does anyone know where this bug is being tracked upstream now? GNOME has migrated from Bugzilla to GitLab, and I haven't been able to find the GitLab version of the Bugzilla bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Correction, I believe this is actually a bug in dbus. gnome-terminal, and others are not setting as it should, but as far as I know, dbus cannot support in a systemd environment due to the limitations mentioned in #21. ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
This is a bug in every GNOME application that uses systemctl --user to start itself. There is currently no sane fix because systemd is missing a feature of upstart, umask inheritance. GNOME could abuse systemd's instantiated services feature to pass the umask through this but this would be far from ideal. A workaround for those of us that need a solution now is to place [Service] UMask= in $HOME/.config/systemd/user/gnome-terminal-server.service.d/umask.conf for an individual user or in /etc/systemd/user/gnome-terminal-server.service.d/umask.conf for all users. This will set the umask only for gnome-terminal. To get most services set an override for dbus.service as well. However, there are quite a few services that are not directly launched by dbus (like gnome-terminal-server) and need their own overrides. A list of these can be obtained by: $ grep -rhoP '(?<=SystemdService=).*' /usr/share/dbus-1/services The only sane way I have come up with to deal with this is to create a single umask.conf and add a symlink to it from the .serivce.d/umask.conf overide for each service found above (as well as dbus). In this way, only two files must be edited to set system default umask, /etc/login.defs and umask.conf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
confirmed to affect user instance of gnome-terminal and nautilus. xterm, su, and commands run by alt+F2 are all unaffected. ** Changed in: nautilus Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
does not affect gedit instances which are launched via xterm or alt+F2, so I assume it's due to the systemd --user or the gnome-terminal user session. ** Changed in: gedit Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
In 16.04, I usually added `umask=0027` after `session optional pam_umask.so` in file `/etc/pam.d/common-session`. Not sure it was the appropriate place but worked for me. No longer working in 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
You can of course use pam_umask(8) on Ubuntu as well if you wish. → no longer works « globally » since 17.04, hence this dicussion. → before 17.04 just setting your favorite umask in /etc/login.defs did the job once and for all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
You can of course use pam_umask(8) on Ubuntu as well if you wish. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
fwiw → https://bugzilla.gnome.org/show_bug.cgi?id=780622#c44 → where security issue is also mentioned. And → https://bugzilla.gnome.org/show_bug.cgi?id=780622#c49 → in fedora we're going to start adding pam_umask to the default pam configuration so admins can edit /etc/login.defs Does it mean Ubuntu 18.04 may benefit from it - as an LTS release, it should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
In Ubuntu 18.04 beta 2 (Bionic), the issue is the same. ** Tags added: artful bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Changed in: gnome-terminal Status: Unknown => Confirmed ** Changed in: gnome-terminal Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Files created with Gedit don't apply expected 002 umask. But files ( or folders ) created with i.e. Gimp apply expected 002 umask. A foreseeable way of setting umask system wide and/or per session is very much needed in order to administrate 17.10 machines in local network ( school, library, business, anything… ) where people share files/folders, be it through samba or nfs… …that's not of low importance, it's a security issue. ** Also affects: gedit Importance: Undecided Status: New ** Also affects: nautilus Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Also affects: gnome-session Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Hello, That bug is not fixed in 17.10 ! For reference : https://forum.ubuntu- fr.org/viewtopic.php?pid=21823638#p21823638 tl;dr → umask is set at 002 in ~/.profile AND in /etc/login.defs but new folders created through Nautilus ( or terminal ) don't grant write permission for group. Unless if created in desktop folder ( why ? ). That's a big problem in multi-users environment. Other curiosity, I don't have that problem with Budgie 17.10 where setting umask at 002 in /etc/login.defs works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=780622 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
$ grep '^ *[^#].*pam_umask' /etc/pam.d/* /etc/pam.d/common-session:session optional pam_umask.so /etc/pam.d/common-session-noninteractive:session optional pam_umask.so Whatever sources of confusion : Even with 'umask=007' in the 'gecos' field of '/etc/passwd', 'gnome- terminal' currently starts with umask=022. I confirm that this issue is a security issue, which must be corrected. IMHO, the best fix would be that GNOME systematically uses the standard 'pam_umask' module. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Oh, one more possible confusion -- when a process's parent dies, it is reparented to pid 1. This guarantees that _some_ process will wait(2) on every dead child. So seeing 'ppid 1' in a process listing simply means the process's parent died before you looked for it. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
I believe even Gnome on 16.04 LTS is using the upstart user session rather than system user session. This could be part of why the Gnome bug discussion seemed to go around in circles. Other possible sources of confusion: - ~/.profile and ~/.bashrc are strictly for shells. Nothing else reads them. This might work if you start X via the startx(1) tool after logging in to the console, like the old days. - Setting umask via GECOS field requires pam_umask(8) to be in the PAM stack for the service in question. It may or may not be. Check /etc/pam.d/ files to be sure. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Yes, I think that this issue comes from the 'gnome-session' issue described at https://bugzilla.gnome.org/show_bug.cgi?id=780622 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Isn't this a gnome-session bug? In 17.04, setting umask in $HOME/.profile has no effect on the gnome- session. Setting umask at /.profile does work in 16.04 though. Setting umask in /.bashrc has an effect ONLY in gnome-terminal apps like nano and vi. But users still have no way to set default umask for gnome apps like LibreOffice and gedit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Thanks to Seth Arnold for his advices to use the 'perf' or 'auditd' tools. Inside the above provided '/var/log/audit/audit.log', I do NOT find the 'umask' string. So, I prefer to begin installing and using the 'perf' tool : $ sudo apt-get install linux-tools-generic Close the graphical session. Record 'umask' for a Gnome session without doing anything - Switch to a console (tty2), and login. $ sudo perf record -ag -e syscalls:sys_enter_umask Switch to the 'gdm' login screen. Open a Gnome session, then immediately close it. Switch to the console (tty2). Press Ctrl-C. ... (325 samples) $ sudo perf script > gnome-umask.log Record 'umask' for a Gnome session with a Gnome terminal $ sudo perf record -ag -e syscalls:sys_enter_umask Switch to the 'gdm' login screen. Open a Gnome session. Inside the Gnome session, open a Gnome terminal with Ctrl-Alt-T. Close the Gnome terminal with Ctrl-D. Close the Gnome session. Switch to the console (tty2). Press (Ctrl C). ... (329 samples) $ sudo perf script > gnome-umask-with-gnome-terminal.log Additional traces triggered by Gnome terminal - Following command eases the discovery of the additional traces : $ diff -I '[0-9]* *\[ *[0-9]* *\] *[0-9.]*' gnome-umask.log gnome-umask-with-gnome-terminal.log > systemd-journal 360 [005] 10229.742513: syscalls:sys_enter_umask: mask: > 0x003f > f7907 __GI___umask (/lib/x86_64-linux-gnu/libc-2.24.so) > 0 [unknown] ([unknown]) > > systemd-journal 360 [005] 10229.742521: syscalls:sys_enter_umask: mask: > 0x0012 > f7907 __GI___umask (/lib/x86_64-linux-gnu/libc-2.24.so) > > (l-server) 12464 [003] 10229.742634: syscalls:sys_enter_umask: mask: > 0x0012 > f7907 __GI___umask (/lib/x86_64-linux-gnu/libc-2.24.so) > 8f2af [unknown] (/lib/systemd/systemd) > > bash 12472 [005] 10229.881381: syscalls:sys_enter_umask: mask: 0x0007 > f7907 __GI___umask (/lib/x86_64-linux-gnu/libc-2.24.so) >1e0e1a8 [unknown] ([unknown]) Interpretation of the additional traces triggered by Gnome terminal --- The 'bash' trace logically comes from the 'umask 007' command in my '.bashrc' file. Since 0022=0x12, the suspect for 'umask 022' hardcoding is '(l-server)'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Etienne, the upstream bug comments suggest it may not be limited to just gnome-terminal. You may have success finding what component / process is performing the umask() calls via perf or auditd: $ sudo perf record -e syscalls:sys_enter_umask -ag -in another terminal change umask- ^C[ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 1.009 MB perf.data (1 samples) ] $ sudo perf script bash 30279 [002] 801251.545434: syscalls:sys_enter_umask: mask: 0x0002 f62f7 umask (/lib/x86_64-linux-gnu/libc-2.23.so) OR $ sudo auditctl -a always,exit -S umask WARNING - 32/64 bit syscall mismatch, you should specify an arch -in another terminal change umask- $ sudo auditctl -d always,exit -S umask $ then find in your /var/log/audit/audit.log a line like: type=SYSCALL msg=audit(1493335707.490:34758): arch=c03e syscall=95 success=yes exit=2 a0=2 a1=ffd0 a2=0 a3=4b4 items=0 ppid=3738 pid=30444 auid=4294967295 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=pts29 ses=4294967295 comm="bash" exe="/bin/bash" key=(null) Fun fact: while testing this, I found both /usr/bin/man and /usr/bin/sudo changing umask. If you care about umask changing you might want to make this auditd rule permanent, of course addressing the 32/64 bit mismatch in 'real' use: -a always,exit -F arch=b64 -S umask -F key=umask -a always,exit -F arch=b32 -S umask -F key=umask Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Thanks to Emily Ratliff for
https://bugzilla.gnome.org/show_bug.cgi?id=780622
This permits me to provide following details :
$ GTS_PID=$(pidof gnome-terminal-server)
$ PARENT_PID=$(ps --no-header -o ppid $GTS_PID | sed -e 's/ //g')
$ ps n -fp $GTS_PID,$PARENT_PID
UID PID PPID C STIME TTY STAT TIME CMD
1001 2551 1 0 avril27 ? Ss 0:00 /lib/systemd/systemd --user
1001 4812 2551 0 avril27 ? Ssl0:10
/usr/lib/gnome-terminal/gnome-terminal-server
$ grep -e Name -e Umask /proc/{$GTS_PID,$PARENT_PID}/status | sort
/proc/2551/status:Name: systemd
/proc/2551/status:Umask:0007
/proc/4812/status:Name: gnome-terminal-
/proc/4812/status:Umask:0022
$ cat /usr/share/dbus-1/services/org.gnome.Terminal.service
[D-BUS Service]
Name=org.gnome.Terminal
SystemdService=gnome-terminal-server.service
Exec=/usr/lib/gnome-terminal/gnome-terminal-server
This proves that 'gnome-terminal-server' has the wrong 0022 umask,
although it is started by 'systemd' in user mode with the right 0007
umask.
This seems to point the bad 'umask=0022' hardcoding inside 'gnome-
terminal-server' and/or inside the method defined by the 'gnome-
terminal' package to start 'gnome-terminal-server' through the 'dbus'
service.
Anyway, this bad 'umask=0022' hardcoding, which must be corrected, is
somewhere inside the 'gnome-terminal' package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
There is a discussion about a related problem in the upstream bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=780622 Since the problem space is known, I'm making the bug public and subscribing the desktop team for further assistance. ** Information type changed from Private Security to Public Security ** Bug watch added: GNOME Bug Tracker #780622 https://bugzilla.gnome.org/show_bug.cgi?id=780622 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
