After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 516328 - Appearance capplet attempts to set unchanged background options on startup
Appearance capplet attempts to set unchanged background options on startup
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] Appearance
2.20.x
Other All
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-14 01:04 UTC by Josh Triplett
Modified: 2008-02-19 07:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Josh Triplett 2008-02-14 01:04:15 UTC
Please describe the problem:
The appearance capplet attempts to set the background options /desktop/gnome/background/color_shading_type and /desktop/gnome/background/picture_options when started.  If those options exist in a mandatory gconf source, this results in an error dialog.

Steps to reproduce:
1. Check that /etc/gconf/2/path has 'include "$(HOME)/.gconf.path"' in it, before the readwrite source in $(HOME)/.gconf
2. Add the following to .gconf.path:
xml:readonly:$(HOME)/.gconf.shared
3. Set the keys /desktop/gnome/background/color_shading_type and /desktop/gnome/background/picture_options in ~/.gconf.shared, perhaps using gconftool-2.
4. Open the Appearance capplet via System->Preferences->Appearance.

Actual results:
An error dialog appears with the following error message:

Can't overwrite existing read-only value: Can't overwrite existing read-only value: Value for `/desktop/gnome/background/color_shading_type' set in a read-only source at the front of your configuration path
Can't overwrite existing read-only value: Can't overwrite existing read-only value: Value for `/desktop/gnome/background/picture_options' set in a read-only source at the front of your configuration path


Expected results:
No error dialog pops up when starting the appearance capplet.  Instead, the controls for those options simply don't allow changes.

Does this happen every time?
Yes, I can consistently reproduce this.

Other information:
Comment 1 Jens Granseuer 2008-02-14 18:39:03 UTC
Thanks for your bug. Should be fixed in trunk now.

2008-02-14  Jens Granseuer  <jensgr@gmx.net>

        * appearance-desktop.c: (wp_scale_type_changed): don't try to set shading
        and options in GConf when we're dealing with a read-only source (bug
        #516328)
Comment 2 Josh Triplett 2008-02-19 07:04:13 UTC
Thanks!