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 516380 - Profile editor attempts to set unchanged palette in gconf
Profile editor attempts to set unchanged palette in gconf
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
2.18.x
Other All
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-14 08:33 UTC by Josh Triplett
Modified: 2009-03-10 21:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Josh Triplett 2008-02-14 08:33:19 UTC
Please describe the problem:
In gnome-terminal, opening the profile editor attempts to set the gconf key /apps/gnome-terminal/profiles/${PROFILE_NAME}/palette .  If that option exists 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 key /apps/gnome-terminal/profiles/Default/palette in ~/.gconf.shared, perhaps using
gconftool-2.
4. Open gnome-terminal, and use the Default profile.
5. Choose the menu item Edit->Current Profile.

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 `/apps/gnome-terminal/profiles/Default/palette' set in a read-only source at the front of your configuration path

Expected results:
No error dialog pops up when opening the profile editor.  Instead, the palette controls simply don't allow changes.

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

Other information:
Comment 1 Christian Persch 2008-05-29 21:31:09 UTC
Should be fixed in svn trunk, please re-test.
Comment 2 Christian Persch 2008-06-28 18:22:36 UTC
No response; closing INCOMPLETE.
Comment 3 Christian Persch 2009-03-08 23:57:26 UTC
Why did you reopen this without adding a comment? Can you reproduce this using g-t >= 2.24.0 ?
Comment 4 Josh Triplett 2009-03-10 21:07:24 UTC
Reopened to add a comment and change resolution, but apparently that second change didn't go through, just the reopening.

Now that I've run gnome-terminal 2.24, I can confirm that it seems to have fixed the problem.  Opening the profile editor no longer gives me an error dialog.  Marking as RESOLVED FIXED.