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 636880 - can't set enum keys
can't set enum keys
Status: RESOLVED FIXED
Product: dconf-editor
Classification: Other
Component: general
0.5.x
Other Linux
: Normal normal
: ---
Assigned To: dconf-editor maintainer(s)
dconf-editor maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-12-09 14:45 UTC by Bill Nottingham
Modified: 2015-02-22 12:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
dconf-editor 0.7.3 output when trying to change an enum value (10.31 KB, text/plain)
2011-03-27 14:31 UTC, Andre "Osku" Schmidt 		Details

Description Bill Nottingham 2010-12-09 14:45:45 UTC 
I can't set enum keys with dconf-editor; it just shows an empty option list.

Example would be org.gnome.settings-daemon.plugins.power, key 'lid-close-batter-action'.

dconf-editor-0.5.1-2.x86_64
Comment 1 Robert Ancell 2011-03-10 05:03:32 UTC 
Enumerations are working for me, closing assumed fixed in 0.7. If not please reopen.
Comment 2 Andre "Osku" Schmidt 2011-03-27 14:30:30 UTC 
i'm experiencing this exact same issue with dconf 0.7.3.

i also get this multiple times in terminal:

** (dconf-editor:1901): CRITICAL **: enum_model_construct: assertion `schema_enum != NULL' failed
Comment 3 Andre "Osku" Schmidt 2011-03-27 14:31:10 UTC 
Created attachment 184365 [details]
dconf-editor 0.7.3 output when trying to change an enum value
Comment 4 Robert Ancell 2011-03-29 05:53:44 UTC 
Ah, found it.  There are some enums defined in /usr/share/glib-2.0/schemas/*.enums.xml that weren't being loaded.  Fixed in master now.
Comment 5 André Klapper 2015-02-22 12:22:46 UTC 
[moving dconf>editor tickets to dconf-editor product. See bug 744791]