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 594821 - [xsettings] GConf:ERROR:gconf-client.c:2021:gconf_client_lookup: assertion failed: (last_slash != NULL)
[xsettings] GConf:ERROR:gconf-client.c:2021:gconf_client_lookup: assertion fa...
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: plugins
2.27.x
Other Linux
: Normal minor
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2009-09-11 01:13 UTC by Chris Coulson
Modified: 2009-09-12 12:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Chris Coulson 2009-09-11 01:13:50 UTC 
This was reported at https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/424421. Changing the gconf key "/apps/gnome_settings_daemon/gtk-modules/gail:atk-bridge" to an empty string causes the following assertion in gnome-settings-daemon (the value of that key was originally another key name - "/desktop/gnome/interface/accessibility"):

GConf:ERROR:gconf-client.c:2021:gconf_client_lookup: assertion failed: (last_slash != NULL)

+ Trace 217483

  • #0 raise
    from /lib/libc.so.6
  • #1 abort
    from /lib/libc.so.6
  • #2 IA__g_assertion_message
  • #3 IA__g_assertion_message_expr
    at /build/buildd/glib2.0-2.21.6/glib/gtestutils.c line 1312
  • #4 gconf_client_lookup
    at gconf-client.c line 2021
  • #5 get
    at gconf-client.c line 1260
  • #6 gconf_client_get_full
    at gconf-client.c line 1326
  • #7 gconf_client_get_bool
    at gconf-client.c line 1561
  • #8 get_gtk_modules
    at gsd-xsettings-manager.c line 731
  • #9 gtk_modules_callback
    at gsd-xsettings-manager.c line 765
  • #10 notify_listener_list
    at gconf-listeners.c line 590
  • #11 ltable_notify
    at gconf-listeners.c line 656
  • #12 gconf_listeners_notify
    at gconf-listeners.c line 185
  • #13 notify_one_entry
    at gconf-client.c line 2469
  • #14 gconf_client_flush_notifies
    at gconf-client.c line 2509
  • #15 notify_idle_callback
    at gconf-client.c line 2403
  • #16 g_main_dispatch
    at /build/buildd/glib2.0-2.21.6/glib/gmain.c line 1960
  • #17 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.21.6/glib/gmain.c line 2513
  • #18 g_main_context_iterate
    at /build/buildd/glib2.0-2.21.6/glib/gmain.c line 2591
  • #19 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.21.6/glib/gmain.c line 2799
  • #20 IA__gtk_main
    at /build/buildd/gtk+2.0-2.17.11/gtk/gtkmain.c line 1205
  • #21 main
    at main.c line 489 






Comment 1


Jeremy Nickurak





          2009-09-11 01:38:34 UTC
        



I was the original submitter. I never explicitly set that key to the empty string, it got to that stage somehow automatically.

This setting did not cause troubles under g-s-d 2.26.x, it was only under 2.27.x that it caused crashes.






Comment 2


Jens Granseuer





          2009-09-12 12:55:06 UTC
        



commit 2638abb2360606e37517513a65932bab125d9068
Author: Jens Granseuer <...>
Date:   Sat Sep 12 14:41:42 2009 +0200

    [xsettings] Validate GConf keys read from the configuration
    
    The xsettings plugin uses user-supplied values as GConf keys.
    Validate those keys before actually trying to use them so we
    don't cause assertions in GConf. Closes bug #594821.