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 Desktop 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/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2072586/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
