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 105884 - gconf-editor doesn't notice new keys are added
gconf-editor doesn't notice new keys are added
Status: RESOLVED WONTFIX
Product: gconf-editor
Classification: Applications
Component: general
git master
Other All
: Normal minor
: ---
Assigned To: Gconf Editor Maintainers
Gconf Editor Maintainers
gnome[unmaintained]
: 338239 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-02-12 15:42 UTC by Brian Cameron
Modified: 2018-07-01 08:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Brian Cameron 2003-02-12 15:42:46 UTC 
The problem can be reproduced with these steps:

1. launch gnome-terminal 
2. Iaunch gconf-editor and open [apps]->[gnome-terminal]->[profiles]
   on the side panel.
3. Add new gnome-terminal profile.
--> gconf-editor does not notice and add the new profile dynamically.
    User must re-launch gconf-editor to see this change.

gconf-editor should notice and update when new profiles are created
in gnome-terminal.
Comment 1 Fernando Herrera 2004-01-15 17:11:26 UTC 
Closing and reopening profiles key would show the new profile (adding
a notification for all keys will result in a big overload for
gconf-editor). The problem is that doing this two times crashs
gconf-editor for the refconuting problem of bug #124662

But after resolving that bug, I think the best aproach would be adding
a refresh menuentry. What do you think about this?
Comment 2 Fernando Herrera 2004-05-28 01:35:13 UTC 
Now I have a patch listening to every preloaded dir... needs a bit of testing.
Comment 3 Manoj 2005-05-04 10:57:18 UTC 
Adding a Reload [CTRL+R] button  menu entry should solve the error. But careful
about the crash, it must not accur.
Comment 4 Teppo Turtiainen 2007-12-27 21:32:23 UTC 
*** Bug 338239 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2018-07-01 08:39:31 UTC 
gconf-editor is not under active development anymore and has not seen code changes for six years. 
Its codebase has been archived: https://gitlab.gnome.org/Archive/gconf-editor/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.