Comment 4 for bug 383461

This is because a line in gconfd still references that directory. Whenever it receives a org.gnome.GConf.Default.SystemSet signal, it notifies listeners of that directory that it changed. But when it does so, if the directory is missing, it creates it with 0700 permissions (i.e. drwx------).

So two things are wrong there: (1) It should be referencing gconf.xml.defaults not .system and (2) it *seems* like it should be creating the directory with 0755 permissions. But issue (2) is moot if we fix (1). Still might be worth an upstream bug though.

Additionally, we should probably now add a line to the packaging fixing this issue for people that upgraded to Karmic by fixing the permissions on that directory. Also, the package should own/create that directory, since gconf-sanity-check doesn't like the directory to be missing if we're going to add it to our default path (as we do).