GNOME Bugzilla – Bug 100590
schemas should be removed from gconf-editor or fixed
Last modified: 2018-08-17 18:41:16 UTC
When gconf-editor is logged in as root the schemas folder should be editable.
Schemas should not be modified, even as root. defaults and mandatory, sure, but schemas are defined by the software only.
Sorry, are defaults different than schemas? Changing summary to "defaults should be editable as root"
Changing titile to: "schemas should be removed from gconf-editor or fixed" After more thought I think that editing defaults belongs in a yet to be writting gnome administration program, and so should not be in gconf-editor. So, coming back to schemas - they cannot and should not be edited and so should not be in the gconf-editor. The only reason I can think for having them there is to be able to view them - but at the moment that is impossible because they are all set to <schema> so all you can see is which schemas exist. All in all I think that schemas are not part of the users editable gconf tree and so should be removed.
Hidding schemas makes sense for me.
*** Bug 146773 has been marked as a duplicate of this bug. ***
GConf has been deprecated since 2011. Hence GConf-Editor is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gconf-editor/commits/master GConf's successors are dconf and gsettings. dconf-editor exists. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to dconf-editor (not: gconf-editor). Thanks!