** 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:
@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
** 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
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:
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
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.
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
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
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
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
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
** 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
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
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:
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
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
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
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.
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:
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
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
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.
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
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
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
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
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
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
** 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:
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,
** 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
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
** 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:
$ 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
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
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
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:
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
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
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
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
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
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
43 matches
Mail list logo
