[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2018-04-11 Thread dino99
** Tags added: artful bionic trusty xenial ** Summary changed: - 17.04 (Zesty) does not source ~/.profile for umask + does not source ~/.profile for umask -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2018-04-11 Thread Coeur Noir via ubuntu-bugs
fwiw → https://bugzilla.gnome.org/show_bug.cgi?id=780622#c44 → where security issue is 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

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2017-11-11 Thread Coeur Noir
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,

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2017-11-11 Thread Coeur Noir
** 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/1701757 Title: 17.04 (Zesty) does not source ~/.profile for umask To manage

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2017-11-10 Thread Coeur Noir
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 don't grant write permission for group. Unless if created in

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2017-08-18 Thread Marc Deslauriers
** Changed in: gnome-session (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/1701757 Title: 17.04 (Zesty) does not source ~/.profile for umask To manage

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2017-07-12 Thread Greg Williams
Excuse me, but is it fair to rank this bug as "Low" importance? There appears to be no way to change the default umask on account of this bug. Umask setting carries privacy and security considerations depending on environment. I think it of considerable importance to at least make sure this bug

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2017-07-06 Thread Greg Williams
Ubuntu bug 1685754 seems specific to gnome-terminal. The bug I reported is for all gnome-session apps. Gnome-terminal can be made to work if a umask is added to .bashrc. This is not the case for other gnome apps like gedit. These bugs may be the same, but I don't know enough to be able to make

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2017-07-05 Thread Seth Arnold
Greg, Sebastien, does this look like a duplicate of bug 1685754? It's tough for me to tell. Of course ~/.profile is only used by some shells, nothing else, so this may not be a bug at all. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2017-07-05 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at

[Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

2017-07-03 Thread Greg Williams
** Summary changed: - 17.04 (Zesty) does not source ~/.profile + 17.04 (Zesty) does not source ~/.profile for umask ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.