update-gconf-defaults permissions on create

[Metabaronen]

Binary package hint: gconf2

Ubuntu 9.10
gconf2 2.28.0-0ubuntu2

update-gconf-defaults relies on users umask when creating new files.
I think that the tool should know that the files must be readable by all users to set their policy.
I encountered this problem using cfengine that executes update-gconf-defaults with umask 700.
-----
umask 077

cat > /usr/share/gconf/mandatory/90_gnome-screensaver <<EOF
/apps/gnome-power-manager/lock/blank_screen true
/apps/gnome-power-manager/lock/use_screensaver_settings false
/apps/gnome-screensaver/idle_delay 20
/apps/gnome-screensaver/lock_enabled true
/apps/gnome-screensaver/logout_enabled true
/desktop/gnome/session/idle_delay 18
EOF
chmod 644 /usr/share/gconf/mandatory/90_gnome-screensaver

update-gconf-defaults --manatory

ls -s /var/lib/gconf/debian.mandatory/%gconf-tree.xml
-rw------- 1 root root 741 2010-04-28 16:37 /var/lib/gconf/debian.mandatory/%gconf-tree.xml

-----

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.