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 649143 - gsettings abort on unknown key
gsettings abort on unknown key
Status: RESOLVED NOTABUG
Product: glib
Classification: Platform
Component: gsettings
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Allison Karlitskaya (desrt)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2011-05-02 05:29 UTC by Hubert Figuiere (:hub)
Modified: 2011-05-28 12:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.91/3.0


Description Hubert Figuiere (:hub) 2011-05-02 05:29:05 UTC 
gsettings abort on unknown keys (in the schema). This is very consistent compared to the g_log() output when passed bad gobject.
Comment 1 Rui Matos 2011-05-27 09:39:17 UTC 
Is this a request for gsettings to not abort?
Comment 2 ecyrbe 2011-05-27 10:05:05 UTC 
yes, gsettings should not abort. aborting is a terrible decision to make. The program can't even alert the user that something is problemativ or allow the programmer to log the error.
is this set in stone or an error can still be emitted without breaking all the api?
Comment 3 Hubert Figuiere (:hub) 2011-05-27 15:15:29 UTC 
I was actually requesting that it puts the computer on fire. To punish the user for having to a programming error.
Comment 4 Matthias Clasen 2011-05-28 12:22:58 UTC 
This is working as designed