** 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces
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
Touch seeded packages, which is subscribed to dbus in Ubuntu.
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
Touch seeded packages, which is subscribed to dbus in 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
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in
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
Touch seeded packages,
** 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
Touch seeded packages, which is subscribed to dbus in Ubuntu.
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
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
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
Touch seeded packages, which is subscribed
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
Touch seeded packages, which is subscribed to dbus in Ubuntu.
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
20 matches
Mail list logo
