value displayed when resetting a key doesn't match the real one

Hi Phil,

I can't reproduce this. Can you tell me what:
$ grep -r splash.png /etc/gconf
produces?

Thanks.

Nothing at all it seems.

However:

$ grep -r splash.png /usr/share/gconf/
/usr/share/gconf/schemas/gnome-session.schemas: <default>splash/gnome-splash.png</default>
/usr/share/gconf/defaults/10_gnome-session:/apps/gnome-session/options/splash_image splash/ubuntu-splash.png

The revelant place is probably /usr/share/gconf if you want to look for the default. Note than we don't modify the upstream schemas but Debian,Ubuntu packages can set a default that is registered during the installation, it makes easy for CDD distributions to change a key by example. The gnome-session one is /usr/share/gconf/defaults/10_gnome-session and it lists "/apps/gnome-session/options/splash_image splash/ubuntu-splash.png", so if there is an issue that's likely to be a gconf distro specifc one rather that due to gnome-session

does reinstalling gnome-session fix your problem?

No, no change...

is your system a stock Ubuntu installation or an upgrade for debian? Did you change /etc/gconf/2/path? What does that file contain (could you copy that to a comment)?

Does "sudo update-gconf-defaults" run fine? Do you have a /var/lib/gconf/debian.defaults/%gconf-tree.xml? What does it contain?

I'm starting to think this must be a freak thing, 'cause I still see it after upgrading to breezy, with almost all the packages replace; so, if you want to drop this, I don't mind.

For the sake of completeness though:
1. It's an ubuntu install, probably started as dapper.
2. I don't think I have ever knowingly changed /etc/gconf/2/path, the non-comments in it are:
xml:readonly:/etc/gconf/gconf.xml.mandatory
include /etc/gconf/2/local-mandatory.path
include "$(HOME)/.gconf.path.mandatory"
include $(ENV_MANDATORY_PATH)
include "$(HOME)/.gconf.path"
xml:readwrite:$(HOME)/.gconf
include "$(HOME)/.gconf.path.defaults"
include $(ENV_DEFAULTS_PATH)
include /etc/gconf/2/local-defaults.path
xml:readonly:/etc/gconf/gconf.xml.defaults
xml:readonly:/var/lib/gconf/debian.defaults
xml:readonly:/var/lib/gconf/defaults
3. Looks like it runs:
phil@explicit:~$ sudo update-gconf-defaults
Password:
phil@explicit:~$ echo $?
0
4. The only splash reference in my /var/lib/gconf/debian.defaults/%gconf-tree.xml, is:
<dir name="gnome-session">
        <dir name="options">
                <entry name="splash_image" mtime="1167835470" type="string">
                        <stringvalue>splash/ubuntu-splash.png</stringvalue>
                </entry>
        </dir>
</dir>

I'll try and grep through the gconf settings files to see if I can find anything, but as I said before, if this only affects me, I have no problem with you marking it notabug or something.

Do you have a /usr/share/pixmaps/splash/ubuntu-splash.png file? What does "gconftool -g /apps/gnome-session/options/splash_image" print?

$ file /usr/share/pixmaps/splash/ubuntu-splash.png
/usr/share/pixmaps/splash/ubuntu-splash.png: symbolic link to `ubuntu-slick.png'

I've actually just reinstalled from scratch (a herd 2 cd image.) I'm not sure the situation is exactly as it was, but it still isn't right.

It seems that the only way to make the problem happen is specifically using the gconf-editor. If I use that to set the key to, for example, "error", then:

$ gconftool -g /apps/gnome-session/options/splash_image
error
$ gconftool -u /apps/gnome-session/options/splash_image
$ gconftool -g /apps/gnome-session/options/splash_image
splash/ubuntu-splash.png

And everything works correctly. If I then open gconf-editor, navigate to the key, and select "unset" from the context menu, the screen will then show "splash/gnome-splash.png". However:

$ gconftool -g /apps/gnome-session/options/splash_image
splash/ubuntu-splash.png

Starting gconf-editor again, the key is now shown as "splash/ubuntu-splash.png" again, so it looks like the context menu option doesn't actually set the key wrong, it just displays the wrong text.

I guess this is actually just a gconf-editor bug?

might be a problem with gconf-editor, did you open the bug because gconf-editor was not displayed the expected value or because you had a wrong image on login?

To be honest, I can't remember; it was very long time ago... Regardless, since reinstalling the only problem seems to be with gconf-editor, so that's the only part that's still current now.

I've checked the gnome-session 2.17.90.1 source and looked for a reference in patches, postinst, and rules for ubuntu-splash.png but found none, even in libgnome 2.17.90, the debian/changelog doesn't indicate the changes on how the splash screen image is set, I'm curious, how does ubuntu apply the gconf settings for the splash screen?

I've found some reference on how ubuntu-splash.png is set, I think this is during hoary, http://www.google.com/codesearch?hl=en&q=+ubuntu-splash.png+show:h1D1iStZHqQ:avSeUxXdgkU:pJYpjWpxz2Y&sa=N&cd=1&ct=rc&cs_p=http://archive.ubuntu.com/ubuntu/pool/main/g/gnome-session/gnome-session_2.10.0.orig.tar.gz&cs_f=gnome-session-2.10.0.orig/debian/patches/07_ubuntu-theme.diff#a0
it patches the gnome-session.schemas.in.in file to set the splash,
I wonder what happened to this method?

Closing the gnome-session task then and opening a gconf-editor one. On feisty the Ubuntu splash is defined by /usr/share/gconf/defaults/16_ubuntu-artwork which is shipped by the ubuntu-artwork package

Updated the current task instead

I've sent the bug upstream, http://bugzilla.gnome.org/show_bug.cgi?id=441178