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 ? Ssl 0: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
Desktop Bugs, which is subscribed to gnome-terminal in 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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
