Does anybody know, this gnome/systemd bug of umask, it this something that I will have to wait for Debian 10 before it is fixed? Or will Debian 9 implement a fix when/if gnome/systemd issues a fix?
I was hoping to be able to move to Stretch, but it's looking unlikely now. ----- Original Message ----- From: "Dejan Jocic" <jode...@gmail.com> To: "Garrett R." <grtrbs...@unseen.is> Cc: debian-user@lists.debian.org Sent: Monday, August 7, 2017 2:32:30 PM Subject: Re: How to change default umask in Stretch? On 07-08-17, Garrett R. wrote: > No effect. > > I added "session optional pam_umask.so umask=0077" to the end of > /etc/pam.d/common-session. Then I confirmed /etc/login.defs has a umask > entry. Then I logged out and back in. > > A new gedit document still reports permission rw-r--r--. > Unfortunately. It looks like it is systemd thing indeed, according to this: https://unix.stackexchange.com/questions/254378/how-to-set-umask-for-the-entire-gnome-session#254923 and this https://github.com/systemd/systemd/issues/6077 It also looks like it does not have workaround. Except to touch file from terminal before editing it in gedit( if it is login shell, for gnome-terminal edit > profile preferences > command > run command as login shell ). Or even better launch gedit from that terminal, it will have right umask settings. Or, make custom shortcut that will launch terminal and gedit from it at same time, something like gnome-terminal -e gedit. Sorry, but not much more help with systemd involved, I'm afraid.
