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 581880 - gconf_client_key_is_writable: assertion failed: (entry != NULL)
gconf_client_key_is_writable: assertion failed: (entry != NULL)
Status: RESOLVED WONTFIX
Product: GConf
Classification: Deprecated
Component: gconf
2.26.x
Other Linux
: Normal critical
: ---
Assigned To: GConf Maintainers
GConf Maintainers
gnome[unmaintained]
: 582031 582151 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-05-08 14:59 UTC by Marcin Banasiak
Modified: 2018-08-17 13:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
Fix assert in gconf-client code (1004 bytes, patch)
2009-05-10 19:59 UTC, Joe Marcus Clarke
none Details | Review

Description Marcin Banasiak 2009-05-08 14:59:49 UTC
After upgrading to GConf 2.26.1 I get the following message while trying to run Evolution Preferences dialog:

GConf:ERROR:gconf-client.c:1202:gconf_client_key_is_writable: assertion failed: (entry != NULL)

and application crashes.
Comment 1 Nathaniel Gephart 2009-05-10 02:13:25 UTC
I'm getting the same error when trying to open Evolution's Preferences. It also occurs when trying to run Nautilus file manager windows in browser mode (but not in spacial mode).

I'm using Arch Linux 64-bit
Kernel: 2.6.29-ARCH
Evolution version: 2.26.1.1
Nautilus version: 2.26.2

Running Evolution from a Terminal window yields the following messages:

** (evolution:7218): DEBUG: mailto URL command: evolution %s
** (evolution:7218): DEBUG: mailto URL program: evolution
**
GConf:ERROR:gconf-client.c:1202:gconf_client_key_is_writable: assertion failed: (entry != NULL)
Comment 2 Philip Withnall 2009-05-10 06:59:53 UTC
*** Bug 582031 has been marked as a duplicate of this bug. ***
Comment 3 Joe Marcus Clarke 2009-05-10 19:58:35 UTC
I fixed this bug with the attached patch.  The other g_asserts need to be removed, and the NULL condition needs to be handled more gracefully.
Comment 4 Joe Marcus Clarke 2009-05-10 19:59:05 UTC
Created attachment 134363 [details] [review]
Fix assert in gconf-client code
Comment 5 Jonh Wendell 2009-05-19 13:03:23 UTC
*** Bug 582151 has been marked as a duplicate of this bug. ***
Comment 6 Mike Auty 2009-06-23 22:53:49 UTC
This looks related to bug 582865.  It looks as though it's a change in the way gconf_client_lookup works (it can now return TRUE even if entry is NULL, which never used to happen).
Comment 7 André Klapper 2018-08-17 13:54:23 UTC
GConf has been deprecated since 2011.

GConf is not under active development anymore. Its codebase has been archived:
https://gitlab.gnome.org/Archive/gconf/commits/master

dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info.

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 a recent + supported version of dconf/gsettings. Thanks!