Per my upstream MR, this is a bug in GLib, not dconf [1]. I've opened & pushed through [2], which has been graciously picked to debian/latest (thanks Jeremy).
[1] https://gitlab.gnome.org/GNOME/gvdb/-/merge_requests/27 [2] https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4607 [3] https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4608 ** Changed in: glib2.0 (Ubuntu Oracular) Status: New => Triaged ** Changed in: glib2.0 (Ubuntu Oracular) Assignee: (unassigned) => Wesley Hershberger (whershberger) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed 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: Triaged 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 ``` The mode of `/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@test-jammy-01:/etc/dconf/db# dconf update root@test-jammy-01:/etc/dconf/db# ls -l local -rw-r--r-- 1 root root 61 Jul 9 12:27 local root@test-jammy-01:/etc/dconf/db# umask 0022 root@test-jammy-01:/etc/dconf/db# umask 0077 root@test-jammy-01:/etc/dconf/db# umask 0077 root@test-jammy-01:/etc/dconf/db# dconf update root@test-jammy-01:/etc/dconf/db# ls -l local -rw------- 1 root root 61 Jul 9 12:28 local root@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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
