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 731674 - gsettings chrash / doesn't warn about invalid schema extends
gsettings chrash / doesn't warn about invalid schema extends
Status: RESOLVED FIXED
Product: dconf-editor
Classification: Other
Component: general
git master
Other Linux
: Normal minor
: ---
Assigned To: dconf-editor maintainer(s)
dconf-editor maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-06-15 06:13 UTC by damianatorrpm@gmail.com
Modified: 2015-10-12 18:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch (3.31 KB, patch)
2015-04-01 21:12 UTC, Jan Alexander Steffens (heftig) 		none Details | Review

Description damianatorrpm@gmail.com 2014-06-15 06:13:26 UTC 
create a new schema with int values and set range min="1" but do not set max;
instead of throwing an error while compiling the schema, it will compile the schema but trying to open it in dconf editor or with gsetting get will result in a crash
Comment 1 damianatorrpm@gmail.com 2014-06-15 06:16:08 UTC 
Try this schema:
http://pastie.org/9291490
Comment 2 Jan Alexander Steffens (heftig) 2015-04-01 21:12:27 UTC 
Created attachment 300779 [details] [review]
patch

dconf-editor: Don't crash when encountering open ranges
    
Ranges can have either min or max unset. Handle this case properly.
Comment 3 Matthias Clasen 2015-04-02 12:29:14 UTC 
this is a dconf-editor patch. move the bug to the right product
Comment 4 Arnaud B. 2015-10-12 18:12:22 UTC 
Thanks! I pushed this patch (with little adaptations) to the “gnome-3-18” development branch, the correction is visible in the 3.18.1 release. On the “master” development branch, the problem is solved another way (as many changes happened); just hoping not to reintroduce the bug there at one point…