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 340834 - schemas registration issue with corrupted xml
schemas registration issue with corrupted xml
Status: RESOLVED WONTFIX
Product: GConf
Classification: Deprecated
Component: Markup backend
2.14.x
Other Linux
: Normal minor
: ---
Assigned To: GConf Maintainers
GConf Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-05-06 14:34 UTC by Sebastien Bacher
Modified: 2018-08-17 13:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sebastien Bacher 2006-05-06 14:34:46 UTC
That bug has been described on https://launchpad.net/distros/ubuntu/+source/control-center/+bug/41788

"...
GConf-Backends-ERROR **: file markup-tree.c: line 3377 (end_element_handler): assertion failed: (g_slist_length (info->local_schemas) == 1)
aborting...
...
I drilled a bit further down, and it turned out that the breakage was caused by the "/var/lib/gconf/defaults/%gconf-tree-cy.xml" file. Moving this file out of the way (if anyone wants to have a look...) brought the system back in line.
...
> Thank you for your bug and the debug work on that. Could you attach the broken .xml? That's a system configuration so it should not have any user data
...
http://librarian.launchpad.net/2428534/perc-gconf-tree-cy.xml
Original filename started with a '%' sign; I renamed that on moving
from /var/lib/gconf/defaults/%gconf-tree-cy.xml to a backup directory.
..."

with that xml the schemas registration is broken:

GConf-Backends-ERROR **: file markup-tree.c: line 3377 (end_element_handler): assertion failed: (g_slist_length (info->local_schemas) == 1)
aborting...

Program received signal SIGABRT, Aborted.

Thread NaN (LWP 32277)

  • #0 __kernel_vsyscall
  • #1 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #2 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #3 IA__g_logv
  • #4 IA__g_log
    at gmessages.c line 517
  • #5 IA__g_assert_warning
  • #6 end_element_handler
    at markup-tree.c line 3377
  • #7 IA__g_markup_parse_context_parse
    at gmarkup.c line 1603
  • #8 parse_tree
    at markup-tree.c line 3625
  • #9 load_schema_descs_for_locale
    at markup-tree.c line 1373
  • #10 ensure_schema_descs_loaded
    at markup-tree.c line 1454
  • #11 markup_entry_set_value
    at markup-tree.c line 1518
  • #12 set_value
    at markup-backend.c line 575
  • #13 gconf_source_set_value
    at gconf-sources.c line 169
  • #14 gconf_sources_set_value
    at gconf-sources.c line 728
  • #15 gconf_engine_set
    at gconf.c line 1226
  • #16 error_checked_set
    at gconf.c line 3321
  • #17 gconf_engine_set_schema
    at gconf.c line 3423
  • #18 hash_install_foreach
    at gconftool.c line 3507
  • #19 IA__g_hash_table_foreach
    at ghash.c line 614
  • #20 process_schema
    at gconftool.c line 3571
  • #21 process_list
    at gconftool.c line 3612
  • #22 do_load_file
    at gconftool.c line 3692
  • #23 do_makefile_install
    at gconftool.c line 3735

Comment 1 Kjartan Maraas 2007-10-02 15:45:25 UTC
It's doing this because the xml doesn't validate. Probably an error with the translation or something. Can we close this here?
Comment 2 Sebastien Bacher 2007-10-02 19:19:06 UTC
It should still not crash though
Comment 3 Kjartan Maraas 2007-10-02 22:55:24 UTC
Does it really crash or is this just an artifact of fatal critical warnings?
Comment 4 Sebastien Bacher 2007-10-03 10:43:52 UTC
not likely, the backtrace seems to indicate it's hitting an assertion
Comment 5 André Klapper 2018-08-17 13:57:06 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!