Description of problem: # cat /etc/dconf/profile/user user-db:user systemd-db:user # :> /etc/dconf/db/user # dconf dump / Segmentation fault (core dumped) "Don't do that, then"? Yes, you are right, I will stop doing that. But a low level and essential function like dconf should never segfault just because of invalid input. It should be more stable and reliable. Version-Release number of selected component: dconf-0.12.1-1.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: dconf dump / crash_function: gvdb_table_is_valid kernel: 3.5.1-1.fc17.i686.PAE truncated backtrace: :Thread no. 1 (8 frames) : #0 gvdb_table_is_valid at ../gvdb/gvdb-reader.c:572 : #1 dconf_engine_refresh_system at ../engine/dconf-engine.c:170 : #2 dconf_engine_refresh at ../engine/dconf-engine.c:206 : #3 dconf_engine_list at ../engine/dconf-engine.c:691 : #4 dconf_client_list at dconf-client.c:1153 : #5 add_to_keyfile at dconf-dump.c:195 : #6 dconf_dump at dconf-dump.c:308 : #7 _vala_main at dconf.c:1423
Created attachment 622122 [details] File: core_backtrace
Created attachment 622123 [details] File: environ
Created attachment 622124 [details] File: limits
Created attachment 622125 [details] File: backtrace
Created attachment 622126 [details] File: cgroup
Created attachment 622127 [details] File: maps
Created attachment 622128 [details] File: dso_list
Created attachment 622129 [details] File: build_ids
Created attachment 622130 [details] File: open_fds
Created attachment 622131 [details] File: var_log_messages
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.