Hide Forgot
abrt version: 2.0.0 comment: Alt-F2 then type 'dconf' followed by 'Enter' executable: /usr/bin/dconf cmdline: dconf component: dconf package: dconf-0.7.3-2 crash_function: _vala_main kernel: 2.6.38.2-9.fc15.x86_64 reason: Process /usr/bin/dconf was killed by signal 6 (SIGABRT) architecture: x86_64 username: aov uid: 500 rating: 4 time: 1303250753 os_release: Fedora release 15 (Lovelock) Text file: event_log, 3099 bytes Text file: smaps, 32342 bytes Binary file: coredump, 585728 bytes Text file: maps, 6498 bytes Text file: dsos, 4181 bytes Text file: backtrace, 5690 bytes build_ids ----- 9fd7f9c1f8b41211bd210e10f915ef69cea6a2ee 19cb415c2a79d817e5547e98be8c81d50add170e 4817e274bc7724ed10ed0c58f4d97188455309a3 2c35820baaea8571d8a8dc977f23cc7f629ddcb4 21ad5b8ca30ad4dbb2190cfd19b03c69958ad013 9ef41f9ca0eabaf3a03dd77eb180e202ab4fe956 1055ac8cb851ad0f25c1533682ed949a1d85c826 a7158bee1dfaecfbd81d16bc6b31b082b0d5244a 5d363f921f4545ef2e76fa9405d096745d4177fd d54647ce3fe0f70c8d886886d69b0fb5038371fa 2f709c0d80b7741b678d35892b3ffacecc03d50c e5f626726497a81807681ed0088dbce6d6a1f17b 5cc111ce758441128d08b5bc105a37addbc28a93 415dd94df0672c555dd4b2a4ef9dbf530694c82c b3900bee00b584ef0bfe2adc2f9b9aed93870bc0 8f67031b50aa96f0a6ae7c89efed129297831c5d
Created attachment 493300 [details] File: event_log
Created attachment 493301 [details] File: smaps
Created attachment 493302 [details] File: maps
Created attachment 493303 [details] File: dsos
Created attachment 493304 [details] File: backtrace
*** Bug 698895 has been marked as a duplicate of this bug. ***
The dconf commandline tool is not useful; just don't run it.
It may be that it's not useful, but being killed by SIGABRT which results in ABRT being opened seems very buggy for just a useless tool. Please reconsider fixing the bug. Thank you, ~ Philipp
Remove the dconf commandline tool or create an alias to dconf-editor?
As the dconf command line is considered an internal tool used by other programs and not by the end-user, it would make sense to just move dconf to a directory which is not in PATH, wouldn't it? IMHO this approach makes sense for internal tools in general. They'd be hidden from the end-user, but are still available unchanged for other programs, tools, whatever. In case this isn't feasible, I suggest just patching dconf to not exit with SIGABRT, but to emit a line "this tool is meant solely for internal use. Please don't call it directly, but via dconf-editor". Something like that. Please comment whether this would be feasible or if things look too easy to me. Cheers, ~ Philipp