[Bug 2072586] Re: Running "dconf update" with different umask affects the permissions of dconf databases in /etc/dconf/db/

[Jeremy Bícha]

** Package changed: dconf (Ubuntu) => glib2.0 (Ubuntu)

** Changed in: glib2.0 (Ubuntu)
       Status: Confirmed => Triaged

** Also affects: glib2.0 (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: glib2.0 (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: glib2.0 (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Also affects: glib2.0 (Ubuntu Oracular)
   Importance: Undecided
       Status: New

** Changed in: glib2.0 (Ubuntu Jammy)
       Status: New => Triaged

** Changed in: glib2.0 (Ubuntu Noble)
       Status: New => Triaged

** Changed in: glib2.0 (Ubuntu Plucky)
       Status: New => Triaged

** Changed in: glib2.0 (Ubuntu Jammy)
     Assignee: (unassigned) => Wesley Hershberger (whershberger)

** Changed in: glib2.0 (Ubuntu Plucky)
     Assignee: (unassigned) => Wesley Hershberger (whershberger)

** Changed in: glib2.0 (Ubuntu Noble)
     Assignee: (unassigned) => Wesley Hershberger (whershberger)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2072586

Title:
  Running "dconf update" with different umask affects the permissions of
  dconf databases in /etc/dconf/db/

Status in glib2.0 package in Ubuntu:
  Triaged
Status in glib2.0 source package in Jammy:
  Triaged
Status in glib2.0 source package in Noble:
  Triaged
Status in glib2.0 source package in Oracular:
  New
Status in glib2.0 source package in Plucky:
  Triaged

Bug description:
  [ Test Plan ]

  ```
  sudo apt-get install dconf-cli
  mkdir -p /etc/dconf/db/database.d
  cat >/etc/dconf/db/database.d/test <<EOF
  [test]
  hello='world'
  EOF
  dconf update
  ls -la /etc/dconf/db/database
  umask 0077
  dconf update
  ls -la /etc/dconf/db/database
  ```

  /etc/dconf/db/database should be 0644 after the second `dconf update`.

  
  [ Original Description ]

  Is it possible to include this [1] upstream fix in Jammy and Noble?

  Steps to reproduce:
  ```
  root at test-jammy-01:/etc/dconf/db# dconf update
  root at test-jammy-01:/etc/dconf/db# ls -l local
  -rw-r--r-- 1 root root 61 Jul  9 12:27 local
  root at test-jammy-01:/etc/dconf/db# umask
  0022
  root at test-jammy-01:/etc/dconf/db# umask 0077
  root at test-jammy-01:/etc/dconf/db# umask
  0077
  root at test-jammy-01:/etc/dconf/db# dconf update
  root at test-jammy-01:/etc/dconf/db# ls -l local
  -rw------- 1 root root 61 Jul  9 12:28 local
  root at test-jammy-01:/etc/dconf/db# apt-cache policy dconf-cli
  dconf-cli:
    Installed: 0.40.0-3
    Candidate: 0.40.0-3
    Version table:
   *** 0.40.0-3 500
          500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
          100 /var/lib/dpkg/status
  ```

  Danger of unexpected misconfiguration is great: others require read
  access to dconf-databases or their dconf-settings will not update as
  expected.

  [1] - https://gitlab.gnome.org/GNOME/dconf/-/issues/25

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2072586/+subscriptions